Dattva Blog · July 2026
Organisation Schema Explained: What AI Needs to Know About Your Brand
Organisation schema is a JSON-LD structured data format that explicitly declares what a brand is, its official name, its connection to verified external profiles like LinkedIn and Crunchbase, and other identifying details, giving AI models a clear, machine-readable reference point instead of having to infer the brand's identity from unstructured page content.
Why AI Models Need an Explicit Entity Reference
A model trying to describe a brand accurately needs to resolve a basic but surprisingly tricky question first: which specific entity is this website actually about, especially when a brand shares a name with an unrelated company, operates under multiple related legal entities, or has changed its name or focus at some point. Organisation schema answers this question explicitly rather than leaving the model to infer it from prose, declaring the brand's official name, its website, its logo, and its connections to other verified profiles in one structured, unambiguous format. Without this explicit declaration, a model cross-referencing a brand's website against other sources has to guess at these connections, a guess that becomes less reliable the more common or ambiguous a brand's name happens to be.
Running a free diagnostic often reveals exactly this kind of entity confusion in how a brand is described.
More detail is covered in Dattva's approach to entity consistency.
What Organisation Schema Should Actually Include
The schema should declare the brand's full, official legal or trading name exactly as it appears consistently elsewhere, since any mismatch between this name and the name used on other verified profiles undermines the consistency the schema is meant to establish. It should include the official website URL and logo, giving a model a clear visual and domain reference. It should link to the brand's verified profiles on external platforms, LinkedIn, Crunchbase, and any relevant industry directories, using the sameAs property, which explicitly tells a model that these separate profiles all describe the same entity. It can include a brief, factual description of what the company does, written plainly rather than promotionally, and contact information where relevant. Founding date and location details add further specificity that helps disambiguate a brand from any similarly named entity elsewhere.
A broader comparison of how different tools handle entity schema is covered in Dattva's research on GEO platforms built for mid-market B2B teams.
What the Data Shows About Entity Confusion Without It
Gemini in particular cross-references brand descriptions across a brand's own site, LinkedIn, Crunchbase, and directory listings, and tends to generate its own description from whichever source it finds first if those sources are inconsistent with each other, a pattern that becomes far less likely once Organisation schema explicitly ties these profiles together through the sameAs property. The most common hallucinations found in AI-generated brand descriptions involve wrong product categories or outdated information, errors that often trace back to exactly this kind of unresolved entity ambiguity rather than a factual mistake in any single source.
Identifying which specific hallucinations trace back to this gap is part of Dattva's citation gap intelligence work.
How to Implement Organisation Schema Correctly
Write the JSON-LD using the Organization type, with the name field matching the brand's official name exactly as used consistently across its own site and its external profiles. Include the url field pointing to the brand's primary domain and a logo field pointing to a stable, high-resolution logo image. Populate the sameAs array with the brand's verified LinkedIn, Crunchbase, and any other relevant profile URLs, since this array is what explicitly links these separate profiles together as describing one entity. Add a description field with a plain, factual summary of the business, avoiding promotional language for the same reasons any citation-native content avoids it, a discipline covered in why promotional content gets filtered out by AI models. Place this schema on the site's homepage at minimum, and ideally repeat it consistently across key pages so any page a crawler lands on carries the same clear entity signal.
Writing the plain, factual description this schema calls for is handled through Dattva's content intelligence work.
Implementing this schema consistently across key pages is the core of Dattva's GEO content engine approach.
How This Connects to the Rest of a Brand's Structured Data
Organisation schema works alongside Article schema, identifying a specific page as authoritative content from a named entity, and FAQPage schema, marking up specific question-and-answer content, together forming a layered structured data picture rather than three unrelated technical add-ons. A page with strong FAQPage schema but no Organisation schema still leaves a model uncertain about which entity the content actually belongs to, which is why Organisation schema functions as a kind of foundation the other schema types build on, a relationship explained further in FAQPage schema explained.
Checking whether this schema actually resolves entity confusion across platforms follows the same logic as Dattva's multi-model verification methodology.
Tracking whether AI-generated brand descriptions improve over time is exactly what Dattva's ongoing AI visibility monitoring is built to do.
Conclusion
Organisation schema gives AI models an explicit, unambiguous answer to a basic but important question: what entity is this website actually about, and how does it connect to the other profiles a model might already know about. Implementing it correctly, with a consistent name and a complete sameAs list, is a foundational technical fix that supports every other structured data and content effort built on top of it.
Frequently Asked Questions
Does Organisation schema need to be on every page of a website?
At minimum it should appear on the homepage, though repeating it consistently across key pages strengthens the entity signal for any page a crawler happens to land on first.
What is the sameAs property and why does it matter?
sameAs is a schema property listing a brand's verified external profiles, explicitly telling a model that these separate listings all describe the same entity rather than leaving that connection to inference.
Does Organisation schema help specifically with Gemini?
Yes, more than most platforms, since Gemini is known to cross-reference brand descriptions across multiple external sources and benefits particularly from an explicit, consistent entity declaration.
What happens if a brand's name in Organisation schema does not match its LinkedIn profile?
The mismatch can undermine the entity consistency the schema is meant to establish, so the name should match exactly across the schema and every linked external profile.
Should Organisation schema include a promotional description of the company?
No, a plain, factual description works better, since promotional language undermines the neutral, informational tone AI models weigh more heavily when assessing a source's credibility.
See where your brand stands in AI answers today
Run a free AI Visibility diagnostic across ChatGPT, Perplexity, Gemini, and Claude — with prioritised, copy-paste fixes at no cost.