Organization Schema: 2026 Guide for Businesses

Administrator in Search Engine Optimization Oct 19 / 1 week ago

Organization schema tells Google who runs a website, what the business is called, where it operates and which logo represents it. One easy mistake is pasting the markup on every page, which Google says is not needed. Another is listing a logo, phone number or address that does not match the visible site. This guide covers placement, types, properties, testing and fixes. The examples are fictional and come from Austin, Lyon, Manchester and Seoul.

What is organization schema and why does it matter?

Organization schema is structured data that describes your business, such as its name, logo, address and contact details. Google says it can help the search engine understand your organization's administrative details and tell your organization apart from others. Some properties work behind the scenes, while others can change what people see in search results.

Think of it as an ID card for your business. The visible site tells people who you are, and the markup tells a crawler the same facts in a standard form. Google splits the properties into two groups. Some are used behind the scenes to tell your organization from similar ones, such as iso6523Code and naics. Others can affect visual elements, such as which logo appears in Search results and in a knowledge panel. Google does not promise that any feature will show up, so we make no ranking claims here. Read the official Google Organization documentation first. For the format itself, see our JSON-LD schema markup guide, which this post does not repeat. Our entity SEO and knowledge graph guide covers the bigger picture.

Where should organization markup go on your site?

Put the markup on your home page, or on one page that describes your organization, such as the about us page. Google says you do not need it on every page of your site. Pick one home for the facts, and keep that page crawlable so Google can read it.

Our take: choose the home page when it already states your name, contact details and what you do, and choose the about page when those facts live there. Pick one and stay consistent. Other page types carry their own markup. An article page uses article markup, which we cover in our article schema guide, and a category page has its own job, covered in our ecommerce category page guide. A fictional online shop in Austin, Texas, puts its organization markup on the home page only. Its blog posts and category pages carry other types. The about page repeats the same facts, so a visitor and a crawler see one story.

Which type fits best: Organization, OnlineStore or LocalBusiness?

Use the most specific schema.org subtype that matches your organization. An ecommerce site should use OnlineStore, not OnlineBusiness. A business with a physical presence, like a restaurant or shop, should use the most specific LocalBusiness subtype and also follow the Google Local business guide for its required and recommended fields.

Plain Organization is the fallback when no subtype fits. Google recommends the most specific subtype so the markup describes what kind of business you run. Our local SEO and Business Profile guide covers the profile side of a physical location. If you use a LocalBusiness type, Google asks you to set a primary phone number and email at the business level before you use contactPoint for more ways to reach you. Consider a fictional bakery chain in Lyon, France. Each shop is a physical place, so the team gives every location a LocalBusiness subtype and keeps the company details on one page. A second fictional chain of cafes in Manchester does the same. The formal definitions live at schema.org Organization.

Which properties does Google recommend for organization schema?

No property is required. Google tells you to add as many recommended properties as apply to your organization. It suggests focusing on what helps users, such as your name or alternate name, signs of real-world presence like address and telephone, and signs of online presence like url and logo.

The table below shows eight of them, taken from the Google documentation.

The status column is copied from the Google organization documentation. Other recommended properties include contactPoint, description, email, foundingDate, legalName, numberOfEmployees and taxID. Skip any that do not apply to you. Because nothing is required, a clean test result says little about quality. Our take: a short, accurate set of organization schema properties beats a long set filled with guesses.

How do you add a logo that Google can use?

Your logo image must be at least 112 by 112 pixels, and its URL must be crawlable and indexable. The file format must be one that Google Images supports. Check how it looks on a plain white background, because a mostly white or gray logo may not appear the way you want.

The logo property helps Google understand which logo you want to show, for example in Search results and knowledge panels. It does not force that logo to appear. If you use the ImageObject type, give it a valid contentUrl or url that follows the same URL rules. A common slip is a pale logo that vanishes on a white page, so test it on white before you publish. Do not block the image folder with robots.txt, since a blocked file cannot be crawled. Use the full web address of the file, and keep it stable so the link does not break after a redesign.

What does sameAs tell Google about your brand?

The sameAs property holds the URL of a page on another website with more information about your organization, such as a profile on a social media or review site. You can list several. Google does not say that sameAs creates a knowledge panel, so treat it as a pointer to profiles you already control.

Use sameAs for real profiles that show the same name, logo and details as your site. Skip abandoned accounts and pages you do not manage. Our take: sameAs works best when the other profiles exist because people use them, not because a checklist said to create them. Outside mentions are a related topic, and our brand mentions and AI search guide explains how they work. The Google page does not describe how much weight sameAs gets, so we promise no result.

How should name and alternateName match your site name?

Google says to use the same name and alternateName in your organization markup that you use for your site name. Matching them keeps the facts on your site, in your markup and in your site name settings in agreement, which helps avoid confusion about what your brand is called.

The name property holds the name of your organization, and alternateName holds another common name for it. The legalName property is for the registered legal name, if it differs from name. A fictional company called Harbor Lane Goods LTD might use Harbor Lane as its name and keep the full registered name in legalName. Our site names and favicons guide shows how Google handles the name in results, so read it before you change either field. If your brand name changes, update the visible site, the markup and your profiles together.

Which identifiers and trust details can you add?

Google lists several identifier properties, including iso6523Code, duns, leiCode, globalLocationNumber, naics and taxID. It encourages iso6523Code over duns and leiCode, and lists common prefixes such as 0060 for DUNS, 0088 for GLN and 0199 for LEI. Add only those that apply, and make sure they match your real registrations.

Properties such as iso6523Code and naics work behind the scenes, so do not expect a visible change from them. The vatID property is different in spirit. Google calls it an important trust signal because users can look up a business in public VAT registries. A fictional online shop in Manchester shows its VAT number on the page and in its markup, so a shopper can check it. Make sure taxID matches the country in your address. Our take: trust is built from facts people can check, so one correct identifier beats a long list. For more on trust signals beyond markup, read our E-E-A-T and helpful content guide and our guide to building authority and AI trust.

What can online merchants add about returns and shipping?

Merchants can influence the merchant knowledge panel and brand profile with details such as return policy, address and contact information. Google offers hasMerchantReturnPolicy and hasShippingService on the Organization type for this, plus hasMemberProgram for loyalty programs. Each one links to its own Google guide with required and optional fields, so follow those guides for the full details.

Google's example for an online store uses the OnlineStore subtype with a contactPoint, a shipping service and a return policy. You can also set these policies for single products, which overrides the store-level policy for that item. Our product schema for ecommerce guide covers product-level markup, and our Merchant Center product feed guide covers the feed side. A fictional online shop in Austin, Texas, sets its return policy once at the organization level and overrides it on a few final-sale items. Keep the policy in the markup identical to the policy page that shoppers read.

How do you add organization markup step by step?

Gather your facts, add every recommended property that applies, and follow the guidelines. Validate with the Rich Results Test, then deploy a few pages and check them with URL Inspection. Make sure robots.txt, noindex and login walls do not block the page. Submit a sitemap so Google learns about later changes.

The Austin shop follows this order, and a short checklist keeps the rollout honest.

• Pick the most specific subtype for your business.
• Copy the name, address and phone from the visible site.
• Add a logo of at least 112 by 112 pixels that works on white.
• List only profiles you manage in sameAs.
• Put the markup on the home page or one about page.
• Validate in the Rich Results Test and inspect the live page.

If you use a CMS, a plugin may be easier than hand coding. If someone else runs your site, forward any Search Console message about the issue to them. If JavaScript builds your pages, Google has a guide on generating structured data with JavaScript. Allow time for recrawling and reindexing, since it may take several days after publishing for Google to find and crawl a page. Our technical SEO audit guide shows where this check fits in a wider routine.

How do you test and fix organization schema problems?

Test the page in the Rich Results Test and fix critical errors first. Non-critical issues are worth fixing too, but they are not needed for eligibility. Use URL Inspection to see how Google reads the live page. If a structured data manual action appears, the markup is ignored, although the page can still appear in results.

Google adds that a syntax test will not catch spammy content or spammy markup, so review the guidelines as well. If the markup breaks, check the list of structured data errors and the unparsable structured data report. Start with the Rich Results Test for a quick read. Our Search Console guide helps if the reports are new to you, and our structured data debugging guide helps when errors pile up. Violating the guidelines can lead to a manual action. Open the Manual Actions report, fix the issue and ask for a review. Our manual actions recovery guide walks through that path. Google does not guarantee that features will show up. Our take: when the test is clean but no feature appears, the cause can sit outside the markup, so check crawlability first.

How should a business in Seoul approach Naver?

A business in Seoul, South Korea should still add valid markup for Google, but Google is not the only audience. Our take: Naver is a major engine in Korea with its own tools and habits, so plan separate work for it and for Korean language fields.

A fictional cafe group in Seoul, South Korea, writes its name in Korean on the site and in the markup, and adds the English name as alternateName. The two stay in step. The team then reads our Naver SEO guide for Korea to decide what else matters on that engine. The Google documentation says nothing about Naver, so we make no claim about how it handles this markup. Test where your customers search.

Across Austin, Lyon, Manchester and Seoul, the lesson is the same. The costly mistake is markup that says one thing while the page says another. Keep the details true, keep them in one place, and review them whenever the business changes.

Frequently asked questions about organization schema

Does this markup improve my rankings?

Google's documentation does not say that this markup changes where a page ranks. It says the markup can help Google understand your organization and tell it apart from others, and some properties can influence visual elements such as the logo. Treat it as a clarity feature. Focus on a useful site, honest details and a page that matches what the markup says.

Is any organization property required?

No. Google lists no required properties. It tells you to add as many recommended properties as apply to your organization. That means a page can pass a test with only a few fields, so a clean result proves little about quality. Fill in the fields you can support with facts that visitors can also see on the page, and skip the ones that do not fit your business.

Do I need the markup on every page?

No. Google recommends placing it on your home page, or on a single page that describes your organization, for example the about us page. You do not need to include it on every page. Repeating it everywhere only gives you more places to keep in sync. Choose one page, keep it open to crawlers, and update it whenever your business details change.

Can I use a different logo from the one on my site?

Google asks for a logo that is representative of your organization, so it should match your brand. The file must be at least 112 by 112 pixels, crawlable, indexable and in a format that Google Images supports. It must also look right on a plain white background. Our take: use the same logo your visitors see, so the markup and the page agree.

Should a shop with a storefront use LocalBusiness?

Google recommends the most specific LocalBusiness subtype when your site is about a local business with a physical presence, such as a restaurant or a store. Follow the Google Local business guide as well, and set a primary phone number and email at the business level before you add contactPoint. A pure online retailer should use OnlineStore instead. Keep the chosen subtype in line with what the business is in the real world.

Does sameAs get me a knowledge panel?

Google does not say that. The documentation describes sameAs as the URL of a page on another website with more information about your organization, such as a social media or review profile. It also says the logo can affect what appears in a knowledge panel. Add sameAs for accurate profiles you control, and do not expect it to trigger a panel on its own.

What if my markup does not match my visible page?

Google warns that if a site violates the structured data guidelines, it may take manual action. A structured data manual action means the markup is ignored, although the page can still appear in results. Our take: a logo, phone number or address that the visitor cannot see on the site is the easiest guideline problem to avoid. Keep markup and page identical.

How do I list more than one location?

Google says you can provide multiple addresses if you have a location in several cities, states or countries. Each address uses the same subfields, such as street address, locality, region, postal code and a two-letter country code. If each location is a physical business, also look at the LocalBusiness subtypes. Keep every address identical to the one shown on your site.

How should I write the telephone number?

Include the country code and the area code, as Google asks for both. Use the business phone meant to be the main contact method for customers. If you use a LocalBusiness type, set the primary phone number at that level before you use contactPoint to list other ways to reach you. The number in the markup should match the number shown on the page.