Organization Schema for Brand Entities

Organization schema is JSON-LD on your homepage that states your brand's name, URL, logo, profiles and identifiers, helping Google "disambiguate your organization in search results". Google says there are no required properties and recommends adding every relevant one (Google). For AI visibility, it's a consistency signal, not a ranking switch: Google says no special markup is needed for its AI features (Google).

Facts are from Google and schema.org documentation, accessed 30 Oct 2026. Points marked "Our view" are interpretation.

On this page

• What does Organization markup actually do?
• Which properties should you include?
• What are the logo rules?
• How should you use sameAs?
• What does a good template look like?
• What rules must you follow?
• How do you test it?
• How does this help with AI answers?
• Exercise
• Checklist
• From MentionX data: how engines refer to brands
• Worked example: Ledgerline cleans up its entity facts
• Where should the markup live?
• Which type should you choose?
• How does the markup connect to the rest of your entity?
• What do people get wrong with Organization markup?
• How do you keep it current?
• How do you check what engines already believe?
• Common questions
• Related
• Sources

Checked on 31 October 2026. "Our view" marks MentionX opinion. Ledgerline is a fictional company used for illustration.

What does Organization markup actually do?

Google says adding it to your home page can help it understand your organization's administrative details and disambiguate it. Some properties work behind the scenes for disambiguation, such as iso6523Code and naicsCode, while others can influence visual elements such as which logo appears in results and your knowledge panel (Google). Merchants can also influence details in their merchant knowledge panel, such as return policy, address and contact information.

Our view: for AI systems, the value is consistency. When your markup, homepage, Wikidata entry and major profiles all state the same name, description and founding facts, there's less reason for an engine to confuse you with a similarly named company.

Which properties should you include?

Google lists properties including these (Google):

The full vocabulary is on schema.org/Organization; more specific types such as OnlineStore or Corporation exist as subtypes.

What are the logo rules?

Google's image guidelines say the logo must be at least 112×112 pixels, the URL must be crawlable and indexable, the format must be supported by Google Images, and it should look as intended on a pure white background (Google). Our view: use a square version of your logo, not a wide wordmark with lots of white space.

How should you use sameAs?

Google describes sameAs as the URL of a page on another website with additional information about your organization, such as a social or review profile, and allows several (Google; schema.org). Good candidates:

• Wikidata item, if one exists (Wikidata)
• Wikipedia article, if one exists
• LinkedIn company page
• Official X, YouTube, GitHub and Crunchbase profiles
• App store developer pages

Our view: only list profiles you control or that are clearly about you. A wrong sameAs link actively teaches engines the wrong entity. More detail is in sameAs links and the knowledge graph.

What does a good template look like?

A fictional example for a made-up company ("Acme Ledger"). Replace every value with real data.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.example.com/#organization",
  "name": "Acme Ledger",
  "legalName": "Acme Ledger Ltd",
  "url": "https://www.example.com/",
  "logo": "https://www.example.com/images/logo-512.png",
  "description": "Accounting software for UK sole traders that files Making Tax Digital VAT returns.",
  "foundingDate": "2019",
  "sameAs": [
    "https://www.wikidata.org/wiki/Q00000000",
    "https://www.linkedin.com/company/example",
    "https://github.com/example"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer support",
    "email": "support@example.com"
  }
}
</script>

The @id lets other markup, such as Article publisher or Product brand, refer to the same organization without repeating it. Our view: that's the simplest way to keep entity facts consistent across a large site.

What rules must you follow?

Google's general structured data guidelines say not to mark up content that isn't visible to readers and not to mark up misleading content (Google). For Organization, that means the facts in your markup should match what's on your homepage or about page. Google also states that it doesn't guarantee structured data will appear in results even if it's valid (Google).

How do you test it?

1. Run the homepage through the Rich Results Test and fix critical errors.
2. Check the vocabulary with the Schema Markup Validator.
3. Use URL Inspection in Search Console to confirm Google sees the rendered markup, especially if it's injected with JavaScript.
4. Compare every value with your about page, Wikidata and LinkedIn.

How does this help with AI answers?

Our view: AI answers that confuse two companies, or describe you with outdated facts, usually reflect inconsistent sources. Organization markup is one source you fully control. Use it to state the canonical version, then fix the others. Don't expect it alone to change whether you're recommended; content and third-party mentions matter more.

Exercise

Write Organization JSON-LD for your company with at least eight properties and four sameAs links, then validate it and list any facts that differ from your other profiles.

Checklist

• On the homepage, one block, with @id
• name, url, logo, description, sameAs at minimum
• Logo 112×112px or larger, crawlable
• Identifiers only where they apply
• Values match visible content and profiles
• Rich Results Test and Schema Markup Validator pass

From MentionX data: how engines refer to brands

Method. Read-only aggregate queries over MentionX scans from 22 August to 29 October 2026 (UTC): 2,217 engine runs (2,154 completed) across 18 anonymised projects and six engines.

Entity markup helps when engines need to tell which company a page or answer is about. In our sample, the type of question changes how often brands are named at all:

Brand and comparison questions name brands most often. Those are exactly the answers where confusing you with a similarly named company does the most harm, because the engine is describing you directly. Engines also differ in how often they show the sources behind those descriptions:

Our view: when an engine names you without citing sources, you can't trace where a wrong fact came from. Consistent markup and profiles narrow the set of places it could have come from.

Limits. A convenience sample of mostly B2B software projects, run through engine APIs, which can behave differently from the consumer apps. Perplexity, Copilot and DeepSeek figures come from a single day (26 October 2026), so treat them as a snapshot, not a trend.

Worked example: Ledgerline cleans up its entity facts

Ledgerline is a fictional accounts-payable tool. Figures are illustrative.

Ledgerline's homepage carries an Organization block written three years ago. It lists an old logo, a LinkedIn URL from before a rebrand and no @id. Its about page says the company was founded in 2018, while a business directory says 2017.

The team checks the registry record, confirms 2018 and updates the directory listing. It rewrites the markup with a single @id, a square logo at 512×512 pixels, a factual description and five sameAs links to profiles it controls. Article pages then refer to the organization with the @id as publisher rather than repeating the details.

The team validates the markup, inspects the rendered homepage in Search Console and records each value with its source in a shared facts sheet, so the next change happens in one place first.

Where should the markup live?

Google recommends placing Organization information on your home page or a single page that describes your organization, and says you don't need it on every page (Google). In practice, use one block on the homepage. Other templates can refer to it by @id instead of copying the whole object. That keeps one source of truth and avoids slightly different versions of your facts across thousands of pages.

If your site is built with a framework that injects JSON-LD with JavaScript, confirm that Google renders it. URL Inspection in Search Console shows the rendered HTML. Our view: if you can output the block in the initial HTML, do; other crawlers may not run JavaScript at all. See JavaScript rendering and AI crawlers.

Which type should you choose?

Organization works for most companies. Schema.org also offers more specific subtypes, and Google suggests using the most specific type that applies, for example OnlineStore for an ecommerce site (Google; schema.org). A software company can usually stay with Organization or Corporation. Don't choose a type for marketing reasons; choose the one that describes what you are.

How does the markup connect to the rest of your entity?

Markup is one of several places where your facts live. Others include your about page, a Wikidata item if you have one, LinkedIn, business registries, app stores and review profiles. Engines can draw on any of them. When they disagree, answers can mix facts from different sources or pick the wrong one.

Start with a list of every profile you control and the values each shows for name, description, founding date, location and website. Fix differences at the source, then list the profiles in sameAs. For a fuller treatment of profile links, see sameAs links and the knowledge graph, and for the visible page that should back up your markup, see building a brand facts page.

What do people get wrong with Organization markup?

• Copying a template without changing every value. Placeholder names or example URLs left in production markup describe a company that doesn't exist.
• Marking up facts that aren't on the page. Google's guidelines say not to mark up content that isn't visible to readers (Google).
• Several conflicting blocks. Plugins, themes and tag managers can each add their own. Check the rendered page and remove duplicates.
• Linking profiles that aren't yours. A fan account or a similarly named company in sameAs points engines at the wrong entity.
• Forgetting to update. A rebrand, move or new logo should trigger a markup change on the same day.

How do you keep it current?

Give one person ownership of the facts sheet and the markup. Review both whenever company facts change and at least twice a year otherwise. Add a check to your release process so site redesigns don't silently drop the block; template changes are a common reason markup disappears. After each change, re-run the Rich Results Test and the Schema Markup Validator and spot-check that your profiles still match.

How do you check what engines already believe?

Before and after you change the markup, ask a few AI assistants simple factual questions about your company: what it does, where it's based, when it was founded and who it serves. Note every fact that's wrong and where the answer says it came from, if it shows sources. Repeat the same questions after your fixes have had time to be crawled. Our view: treat this as a spot check, not a measurement, because answers vary between runs.

Common questions

Does Organization markup guarantee a knowledge panel? No. Google says valid structured data isn't guaranteed to appear in results (Google).

Should I add it to every page? No. Google says you don't need it on every page. Use one block and refer to it by @id.

Can I include several sameAs links? Yes. Google allows multiple, as long as each is clearly about your organization.

Related

• Schema markup for AI search
• Wikidata for brands

Sources

• Google, Organization structured data; structured data general guidelines; AI features and your website; Rich Results Test
• schema.org, Organization; sameAs; Schema Markup Validator
• Wikidata

All accessed 30 Oct 2026.