Google SEO Update 2023 November 29
- Ata Aytug Acar
- 0 Comments
- 29 de novembro: Adicione nova documentação de Organização, que mescla a documentação de Logotipo e inclui mais informações organizacionais (como informações de contato, nome legal e identificadores de negócios).
Organização (Organization) dados estruturados
You can use organization structured data to let Google know about your organization’s administrative details, for example, logo, address, contact information, and business identifiers. Google can make use of this markup in knowledge panels and other visual elements (such as attribution), which helps users more easily find your organization’s details on Google Search.
How to add structured data
Structured data is a standardized format for providing information about a page and classifying the page content. If you’re new to structured data, you can learn more about how structured data works.
Here’s an overview of how to build, test, and release structured data. For a step-by-step guide on how to add structured data to a web page, check out the structured data codelab.
- Add as many recommended properties that apply to your web page. There are no required properties; instead, add the properties that apply to your content. Based on the format you’re using, learn where to insert structured data on the page.
- Follow the guidelines.
- Validate your code using the Rich Results Test and fix any critical errors. Consider also fixing any non-critical issues that may be flagged in the tool, as they can help improve the quality of your structured data (however, this isn’t necessary to be eligible for rich results).
- Deploy a few pages that include your structured data and use the URL Inspection tool to test how Google sees the page. Be sure that your page is accessible to Google and not blocked by a robots.txt file, the
noindex
tag, or login requirements. If the page looks okay, you can ask Google to recrawl your URLs.
- To keep Google informed of future changes, we recommend that you submit a sitemap. You can automate this with the Search Console Sitemap API.
Example
Here’s an example of organization information in JSON-LD code.
<html>
<head> <title>About Us</title> <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Organization", "image": "https://www.example.com/example_image.jpg", "url": "https://www.example.com", "sameAs": ["https://example.net/profile/example1234", "https://example.org/example1234"], "logo": "https://www.example.com/images/logo.png", "name": "Example Corporation", "description": "The example corporation is well-known for producing high-quality widgets", "email": "contact@example.com", "telephone": "+47-99-999-9999", "address": { "@type": "PostalAddress", "streetAddress": "Rue Improbable 99", "addressLocality": "Paris", "addressCountry": "FR", "addressRegion": "Ile-de-France", "postalCode": "75001" }, "vatID": "FR12345678901", "iso6523Code": "0199:724500PMK2A2M1SQQ228" } </script> </head> <body> </body> </html>
Diretrizes
Você deve seguir estas diretrizes para que os dados estruturados sejam elegíveis para inclusão nos resultados de pesquisa do Google.
Aviso: Se o seu site violar uma ou mais dessas diretrizes, o Google poderá tomar medidas manuais contra ele. Assim que você corrigir o problema, poderá enviar seu site para reconsideração.
Diretrizes Técnicas
- Fundamentos da Pesquisa
- Diretrizes Gerais de Dados Estruturados
- Diretrizes Técnicas
Recomendamos colocar essas informações na sua página inicial ou em uma única página que descreva sua organização, como a página “Sobre nós”. Não é necessário incluí-las em todas as páginas do seu site.
Recomendamos usar o subtipo mais específico de schema.org de Organization que corresponda à sua organização. Por exemplo, se você tiver um site de comércio eletrônico, recomendamos usar o subtipo OnlineStore em vez de OnlineBusiness. E se o seu site for sobre um negócio local, como um restaurante ou uma loja física, recomendamos fornecer seus detalhes administrativos usando o(s) subtipo(s) mais específicos de LocalBusiness e seguir os campos obrigatórios e recomendados para Local Business, além dos campos recomendados neste guia.
Definições de Tipos de Dados Estruturados
O Google reconhece as seguintes propriedades de uma Organization. Para ajudar o Google a entender melhor sua página, inclua quantas propriedades recomendadas se aplicarem à sua página da web. Não há propriedades obrigatórias; em vez disso, adicione as propriedades que se aplicam à sua organização.
Recomendamos focar em propriedades que sejam úteis para seus usuários, como name ou alternateName para o nome do seu negócio, bem como uma indicação da presença no mundo real (por exemplo, address ou telephone) e da presença online (por exemplo, url ou logo).
Recommended properties | |
---|---|
name |
Text The name of your organization. Use the same name and alternateName that you’re using for your site name. |
alternateName |
Text Another common name that your organization goes by, if applicable. |
legalName |
Text The registered, legal name of your Organization , if applicable and different from the name property. |
description |
Text A detailed description of your organization, if applicable. |
logo |
URL or ImageObject A logo that is representative of your organization. Adding this property can help Google better understand which logo you want to show, for example in Search results and knowledge panels.
Image guidelines:
If you use the |
url |
URL The URL of the website of your organization, if applicable. This helps Google uniquely identify your organization. |
sameAs |
URL The URL of a page on another website with additional information about your organization, if applicable. For example, a URL to your organization’s profile page on a social media or review site. You can provide multiple sameAs URLs. |
telephone |
Text A business phone number meant to be the primary contact method for customers. Be sure to include the country code and area code in the phone number. |
email |
Text The email address to contact your business, if applicable. |
address |
PostalAddress
The address (physical or mailing) of your organization, if you have one. Include all properties that apply to your country. The more properties you provide, the higher quality the result is for users. You can provide multiple addresses if you have a location in multiple cities, states, or countries. For example: "address": [{ "@type": "PostalAddress", "streetAddress": "999 W Example St Suite 99 Unit 9", "addressLocality": "New York", "addressRegion": "NY", "postalCode": "10019", "addressCountry": "US" },{ "streetAddress": "999 Rue due exemple", "addressLocality": "Paris", "postalCode": "75001", "addressCountry": "FR" }] |
address. |
Text The full street address of your postal address. |
address. |
Text The city of your postal address. |
address. |
Text The region of your postal address, if applicable. For example, a state. |
address. |
Text The postal code for your address. |
address. |
Text The country for your postal address, using the two-letter ISO 3166-1 alpha-2 country code. |
contactPoint |
ContactPoint The best way for a user to contact your business. Include all support methods available to your users following Google recommended best practices. For example:
"contactPoint": { "@type": "ContactPoint", "telephone": "+9-999-999-9999", "email": "contact@example.com" } |
contactPoint. |
Text The phone number to contact your business, if applicable. Be sure to include the country code and area code in the phone number. If you are using a LocalBusiness type, specify a primary phone number at the LocalBusiness level before using contactPoint to specify multiple ways to reach your organization. |
contactPoint. |
Text The email address to contact your business, if applicable. If you are using a LocalBusiness type, specify a primary email address at the LocalBusiness level before using contactPoint to specify multiple ways to reach your organization. |
numberOfEmployees |
QuantitativeValue The number of employees in your Organization , if applicable.
Example with a specific number of employees: "numberOfEmployees": { "@type": "QuantitativeValue", "value": 2056 } Example with the number of employees in a range: "numberOfEmployees": { "@type": "QuantitativeValue", "minValue": 100, "maxValue": 999 } |
foundingDate |
Date The date your Organization was founded in ISO 8601 date format, if applicable. |
iso6523Code |
Text The ISO 6523 identifier of your organization, if applicable. The first part of an ISO 6523 identifier is an ICD (International Code Designator) which defines which identification scheme is used. The second part is the actual identifier. We recommend separating the ICD and the identifier with a colon character (U+003A ). Common ICD values include:
|
duns |
Text The Dun & Bradstreet DUNS number for identifying your Organization , if applicable. We encourage using the iso6523Code field with prefix 0060: instead. |
leiCode |
Text The identifier for your Organization as defined in ISO 17442, if applicable. We encourage using the iso6523Code field with prefix 0199: instead. |
naics |
Text The North American Industry Classification System (NAICS) code for your Organization , if applicable. |
globalLocationNumber |
Text The GS1 Global Location Number identifying the location of your Organization , if applicable. |
vatID |
Text The VAT (Value Added Tax) code associated with your Organization , if applicable to your country and business. This is an important trust signal for users (for example, users can look up your business in public VAT registries). |
taxID |
Text The tax ID associated with your Organization , if applicable. Make sure taxID matches the country that you provided in the address field. |
Rešavanje problema
Ako imate problema sa implementacijom ili debagovanjem strukturiranih podataka, ovde su neki resursi koji vam mogu pomoći.
Ako koristite sistem za upravljanje sadržajem (CMS) ili se neko drugi brine o vašem sajtu, zamolite ih da vam pomognu. Uverite se da ste prosledili svaku poruku iz Search Console-a koja detaljno opisuje problem. Google ne garantuje da će funkcije koje koriste strukturirane podatke biti prikazane u rezultatima pretrage. Za listu uobičajenih razloga zbog kojih Google možda neće prikazati vaš sadržaj u bogatom rezultatu, pogledajte Opšte smernice za strukturirane podatke. Možda imate grešku u svojim strukturiranim podacima. Proverite listu grešaka u strukturiranim podacima. Ako ste primili ručnu akciju zbog strukturiranih podataka protiv vaše stranice, strukturirani podaci na stranici će biti ignorisani (iako se stranica može i dalje pojaviti u rezultatima Google pretrage). Da biste ispravili probleme sa strukturiranim podacima, koristite izveštaj o ručnim akcijama. Ponovo pregledajte smernice kako biste utvrdili da li vaš sadržaj nije usklađen sa smernicama. Problem može biti izazvan spam sadržajem ili upotrebom spam označavanja. Međutim, problem možda nije u sintaksi, tako da test za bogate rezultate možda neće moći da identifikuje te probleme. Rešavanje problema sa nedostajućim bogatim rezultatima / padom ukupnih bogatih rezultata. Ostavite vreme za ponovo indeksiranje. Zapamtite da može potrajati nekoliko dana nakon objavljivanja stranice da Google pronađe i indeksira. Za opšta pitanja o indeksiranju i pretraživanju, proverite FAQ o indeksiranju i pretraživanju Google-a. Postavite pitanje u Google Search Central forumu.
Recent Comments