Organization Schema: How Does Your Logo Show Up in Google Search?

At Talha Aslan and team, we see this as one of the most overlooked items in technical SEO audits. In practice, many sites have no organization markup at all. Others still carry a block that a plugin generated years ago, and it no longer matches the business. In this guide we follow Google Search Central's official documentation step by step. You will learn which properties to fill, which rules the logo has to meet, how it relates to your site name and how to validate everything. If structured data is new to you, start with our guide to schema markup first.

Is the small icon next to a result the favicon or the organization logo?

Specifically, this is the distinction people mix up most often. The small square icon beside your site name in an organic result follows Google's favicon rules. For a favicon, you add a link tag with rel="icon" to the head of your home page. Also, the image has to be square, and Google's favicon documentation recommends a size larger than 48x48 pixels.

The organization logo, however, is a separate signal. According to Google, the logo property can affect visual elements such as the logo in search results and the knowledge panel. So there are two jobs, and one does not replace the other. For example, if your favicon file is broken, no amount of logo markup will fix the icon in your result snippet.

• Favicon: the small icon in the result line. You declare it with a link tag on the home page.
• Organization logo: your brand logo. You declare it in the logo property of your markup.
• Common ground: Googlebot has to be able to crawl both images.

If the favicon is your actual problem, our post on a favicon not showing in Google walks through the fix.

Which page should carry your organization schema?

Google recommends adding organization markup to your home page or to a single page that describes the organization, such as an About page. You do not need it on every page. Therefore a block that repeats on every template is optional. It does no harm either, as long as it carries the same accurate data everywhere.

In practice we prefer the home page for organization schema. The WebSite markup for your site name also lives only on the home page, and keeping both blocks together makes maintenance easier. On the other hand, multilingual sites may have a home page per language. In that case, consistency across languages matters as much as picking the right page.

Above all, the markup needs to match visible content. Google's general structured data guidelines ask that markup describe content users can see on the page. In other words, an address or phone number that appears only in code and nowhere on your About page is not a healthy setup.

Which organization subtype should you choose?

Google recommends the most specific schema.org subtype that fits your organization. For example, OnlineStore is a better choice than the generic OnlineBusiness for an ecommerce site. A business with a physical location that serves customers should pick the right LocalBusiness subtype and also follow that type's own guidelines.

Why does the subtype matter? Because the right classification decides which set of properties makes sense. For instance, giving a software company a local business type, or describing a dental clinic only as a generic Organization, blurs the signal.

• Organization: general organizations that fit no specific subtype.
• OnlineStore: stores that sell products online.
• OnlineBusiness: businesses that operate online but are not stores.
• LocalBusiness subtypes: businesses with a physical location that customers visit.

In short, you choose the type that reflects your real business. Picking a type that does not fit, just in the hope of more rich results, can conflict with the ban on misleading markup.

Does organization schema have required properties?

According to Google's documentation, organization markup has no required properties. Instead, Google asks you to add every recommended property that applies to you. That flexibility sounds convenient. However, every empty field makes it harder for Google to distinguish your organization. The table below sums up the properties we use most often in client work and what each one does.

For merchants, the documentation also lists return policy, shipping service and member program properties. Each comes with its own documentation. So read those pages separately if you need them.

What requirements does the logo image have to meet?

Google's organization structured data documentation sets a few clear rules for the logo. First, the image has to be at least 112x112 pixels. Second, the image URL must be crawlable and indexable. Finally, the file format has to be one that Google Images supports.

1. Prepare the logo at 112x112 pixels or larger, ideally square or close to square.
2. Host the file at a URL that robots.txt does not block and that needs no login.
3. Pick a common format that Google Images supports.
4. Keep the logo URL stable. A fixed address makes crawling easier.
5. If you use ImageObject, make sure its url or contentUrl meets the same rules.

The mistake we see most often is a logo moved by an image optimization plugin or CDN to an address that blocks Googlebot. The logo looks fine in your browser, yet Google cannot reach the file. That is why we recommend testing the logo URL itself in the URL Inspection tool.

Why should you test your logo on a white background?

Google's documentation asks you to check how your logo looks on a pure white background. Logos that are mostly white or gray may not display as intended. So a white, transparent logo designed for a dark header can almost vanish in search results.

Example scenario: example.com, an architecture studio, uses a white logo with a transparent background in its dark top menu. It points the organization markup to the same file. If Google shows that logo on a white surface, almost nothing remains visible. The fix, however, is simple. You prepare a separate version of the logo in a dark color or with its own background for the markup.

In practice, asking your design team for one extra file solves this. Also check the logo at small sizes. Thin, highly detailed emblems lose legibility when they shrink. As a result, your brand stays recognizable in both search results and the knowledge panel.

Which URLs belong in the sameAs property?

The sameAs property holds URLs of other pages with more information about your organization. Google's documentation names social media profiles and review site profiles as examples, and you can list several URLs. This property helps Google connect your website with your other identities on the web.

Above all, list only active profiles that you own. An account nobody has updated in years, one whose password nobody remembers or one that someone else created weakens the signal. Moreover, the guidelines explicitly forbid markup that impersonates an organization or misrepresents ownership or affiliation.

• Your official social media accounts, only the ones you manage.
• Your company video channel.
• Review or directory profiles that truly belong to you.
• A page about your organization on an independent reference source, if one exists.

To see how this ties into brand identity more broadly, read our posts on what a knowledge graph is and how entity SEO helps Google recognize your brand.

How do you define contactPoint and contact details?

The contactPoint property describes the support channels people can use to reach you. Google's documentation recommends email and telephone inside it and asks you to include every support method available to users. For instance, if your sales line and your technical support email are separate, you define them as two contact points.

For LocalBusiness markup, the documentation suggests a specific order. First, you set the primary email and phone directly at the business level. Then, if you offer several contact methods, you add contactPoint. This order helps Google separate your main contact details from additional channels.

In addition, we recommend writing phone numbers in international format with the country code. A number on the contact page that differs from the one in the markup is an inconsistency we find often. Put simply, every contact detail in your markup should match what users see on the page.

What do address, VAT and identifier properties do?

According to Google, some properties such as iso6523Code and naics work behind the scenes. They do not appear in search results. Still, they help identify your organization correctly. In the address property, you fill every address part that applies in your country and use the two letter ISO 3166-1 alpha-2 code for the country. If you have several addresses, you can list all of them.

The documentation calls vatID an important trust signal, because users can look up businesses in public VAT registries. The iso6523Code property combines an identifier with its code list number, separated by a colon. For that reason, Google recommends iso6523Code instead of the separate DUNS and LEI properties.

Note: every number in these fields has to match your official records exactly. If you are unsure about an identifier, leaving the field empty is safer than guessing. Please confirm tax and registration details with your accountant. This section is not tax or legal advice.

How does your site name relate to organization schema?

The site name is the name Google shows above your URL in search results, and people often confuse it with organization markup. According to Google's site names documentation, WebSite structured data is the most important signal for your preferred name. That markup belongs only on the home page. The name and url properties are mandatory, while alternateName is optional.

In addition, Google looks at og:site_name, the title tag and headings on the home page. Therefore the name inside your organization markup and the name inside your WebSite markup should describe the same brand. If one is an acronym and the other a full name, put the acronym in alternateName.

One more difference matters here for organization schema. The Rich Results Test does not support site names. So you validate WebSite markup with a schema testing tool such as the Schema Markup Validator. If your site name looks wrong, our post on a wrong site name in Google covers the causes in detail.

How do you set up organization markup step by step?

You can plan the setup without writing code. First you collect the facts, then you generate the markup and finally you test it. Google supports JSON-LD, Microdata and RDFa, but it recommends JSON-LD. We also use JSON-LD because it is easier to maintain.

1. Collect your name, legal name, main URL and any acronyms in one document.
2. Prepare a logo file of at least 112x112 pixels that looks good on white.
3. List the active profile URLs you own for sameAs.
4. Match support email, phone and address with your contact page.
5. Choose the most specific type that fits your organization.
6. Add the JSON-LD block to your home page or About page.
7. If the page already has WebSite markup, add the site name properties to that existing node instead of creating a second block.

If you would rather generate a draft than write JSON-LD by hand, try our schema generator tool. Then check every generated field against your real data. If you want us to implement and monitor this setup on your site, you can request a quote on our SEO consulting page.

How do you validate with the Rich Results Test and URL Inspection?

Google's recommended validation flow is clear. First, you check the markup with the Rich Results Test and fix any critical errors. Non critical issues do not block rich result eligibility. Still, the documentation notes that fixing them can improve the quality of your structured data.

Next, you deploy a few pages and use the URL Inspection tool in Search Console to see how Google views them. Here you confirm that robots.txt, a noindex tag or a login requirement does not block the page. If everything looks fine, you can request a recrawl from the same tool.

• Rich Results Test: does the markup contain critical errors?
• URL Inspection: can Google crawl the page and the logo?
• Sitemap: does it keep Google informed of changes?

If Search Console still feels unfamiliar, our guide on what Google Search Console is and how to use it explains the main screens. Also, if you see syntax errors, read our post on the unparsable structured data error.

What if your organization schema is valid but the logo still does not show?

Start by accepting one fact. Google does not guarantee that features that consume structured data will show up in search results. A markup that passes every test does not mean the logo appears right away. That said, there are concrete points you can check, and most problems turn up in one of them.

1. Open the logo URL through URL Inspection, through Googlebot's eyes rather than your browser.
2. Confirm that robots.txt does not block the image folder.
3. Check that the logo is not smaller than 112x112 pixels.
4. Make sure the logo stays visible on a white background.
5. Look for several conflicting organization blocks on the same page.
6. Wait a few days for recrawling and reindexing.

In practice, conflicting blocks appear most often on plugin heavy sites. For example, the theme may print one organization block while the SEO plugin prints another, each pointing to a different logo URL. In that case you settle on one source and switch the other off.

How can you influence the logo in your knowledge panel?

A knowledge panel is the box where Google shows information it has gathered about an entity next to the results. Your organization logo can influence the image in that panel, but markup alone does not create a panel. According to Google Help, if a panel exists for your organization, you can claim and verify it.

Based on Google's knowledge panel help page, the process works like this. You search for your organization, click the option to claim the panel and sign in to one of the official sites or profiles Google lists, such as Search Console or YouTube. After verification, you can suggest changes through the feedback option under the panel and add web pages that confirm the correct information.

On the other hand, the same page recommends a Google Business Profile for businesses that serve customers at a location or within a service area. So if you run a local business, your Business Profile is usually the main place to manage the panel image.

Which mistakes can lead to a manual action?

Google may apply a manual action to sites that violate its structured data guidelines. According to the general guidelines, a structured data manual action removes rich result eligibility but does not affect how the page ranks in web search. You monitor this in the Manual Actions report in Search Console.

Specifically, these behaviors usually carry risk in organization schema:

• Using a name or logo that impersonates another organization.
• Adding profiles you do not own to sameAs.
• Marking up facts that never appear on the page and that nobody can verify.
• Implying an affiliation with an organization you have no tie to.

After fixing the issue, you can request reconsideration. The best approach, however, is to mark up only verifiable facts from the start. That way you never have to deal with manual action risk.

Example scenario: how would organization schema look for example.com?

Example scenario: example.com is a furniture brand with a showroom in Istanbul that also sells online. Meanwhile, the showroom receives customers in person, and the website sells products. The first question in this setup is which type the home page should describe.

For a structure like this, we would describe the online store on the home page with the OnlineStore type. For the showroom, we would use the right LocalBusiness subtype on a separate location page. The home page block includes name, legalName, url, logo, sameAs, contactPoint and address. The WebSite block on the same page carries the site name and its acronym.

For the logo, you prepare a dark, square version and keep it at a stable URL. Then you confirm with the Rich Results Test that there are no critical errors and check with URL Inspection that Googlebot can reach the logo. This is not a worked calculation but an example scenario that shows the setup logic. Timing and appearance remain Google's decision.

What should you watch for with WordPress and tag managers?

On WordPress sites, you usually enter organization details in your SEO plugin settings. That is practical for organization schema. However, if the theme also prints its own markup, you end up with duplicate blocks. So after setup, we recommend viewing the source code and counting how many organization blocks exist.

Alternatively, you can also add structured data through a tag manager. Still, this method relies on JavaScript adding the content later. You need to confirm with URL Inspection that Google sees the block when it renders the page. For details, read our post on adding schema with Google Tag Manager.

• Pick a single source: plugin, theme or tag manager.
• Keep the logo URL fixed in your media library.
• Test the markup again after every redesign.

This way you prevent your organization data from breaking silently whenever the site changes.

How do you keep organization schema consistent on a multilingual site?

In practice, the most common problem on multilingual sites is that each language version describes the organization differently. For example, the English home page may show the legal name, the German version an acronym and another version an old logo URL. Google may read these differences as conflicting signals rather than as versions of one organization.

That is why we recommend managing organization data from one master source. Name, legal name, logo URL, sameAs list and identifiers stay identical in every language. You translate only text fields such as description. As a result, Google sees the same organization no matter which language it crawls.

• name and legalName: the same spelling in all languages.
• logo: the same stable file URL in all languages.
• sameAs: the same official profile list in all languages.
• description: a short description translated for each language.

Also, if each language home page sits on its own subdomain, mind the site name rule. Google supports one site name per domain or subdomain and does not support separate site names for subdirectories.

Can you combine organization schema with LocalBusiness?

Yes, on the right page and in the right role. In the schema.org hierarchy, LocalBusiness is a subtype of Organization. Therefore a LocalBusiness subtype for a business with a physical location already counts as an organization description. Placing a generic organization block and a separate LocalBusiness block on the same page, with no link between them, usually just duplicates information.

For brands with several branches, however, the picture changes. The home page carries an organization block for the brand itself, and each branch page carries a LocalBusiness block for that branch. In this way, you describe the brand and its locations separately and without contradictions.

Example scenario: example.com runs a chain of three dental clinics. The home page carries the brand, the logo and the official profiles. Each branch page describes its own address, phone and opening hours. For how branches appear on maps, Google Business Profile remains the main place to manage them.

When do changes show up and how do you track them?

According to Google, recrawling and reindexing can take several days. The site names documentation adds that it can take anywhere from a few days to several weeks. That is why, instead of expecting results the next day, we recommend a tracking plan after any change to your markup.

In practice, you track three things. First, you check the last crawl date and the rendered version of your home page in URL Inspection. Next, you make sure your sitemap is current, because Google's documentation recommends submitting a sitemap to keep it informed of changes. Finally, you search for your brand name at regular intervals and note how the logo and site name appear.

One caveat, though. A visible logo or a knowledge panel is not a ranking guarantee, and no method can promise one. Organization markup is a foundational layer that helps Google understand your organization correctly.

Who should own organization schema in your team?

Organization markup looks like a one time coding task, but in reality it is brand data maintenance. Over time your address changes, you open a new social account, you refresh the logo or your legal name gets an update. If these changes never reach the markup, Google keeps receiving outdated or conflicting information.

That is why we treat organization markup as a permanent item on our technical SEO checklist. With every major project, such as a redesign, a domain migration or a rebrand, we review the markup again. We also evaluate favicon, site name and organization data together, because all three shape how your brand looks in search results.

If your logo, site name or organization details look wrong in Google, we diagnose and fix the issue and then keep monitoring it. For scope and a quote, see our SEO consulting service. We do not promise rankings. Instead, we deliver a measurable, monitored setup that follows Google's official documentation.

Core guide: What Is Digital Marketing? Its types, examples and how it is done, on one page with an interactive film that travels through the brain.