What Organisation schema does

Organisation schema (schema.org uses the American spelling "Organization") represents the institutional entity behind your business — the legal person, so to speak. Where LocalBusiness schema tells AI systems where you are and what you do, Organisation schema tells them who you are as a registered, verifiable entity.

For AI visibility, this matters because AI knowledge graphs distinguish between a business's operational identity (LocalBusiness) and its legal/institutional identity (Organization). Businesses that declare both give AI systems far more to work with when constructing a confidence profile — and are significantly more likely to be treated as a well-understood, citable entity.

The structure of Organisation schema

Organisation schema can stand alone or be referenced from LocalBusiness schema. The most effective approach for a small business is to use it in a @graph alongside your LocalBusiness schema, connected by @id references:

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://www.yourbusiness.co.uk/#organization",
      "name": "Your Business Name Ltd",
      "legalName": "Your Business Name Limited",
      "url": "https://www.yourbusiness.co.uk/",
      "logo": "https://www.yourbusiness.co.uk/images/logo.png",
      "foundingDate": "2019",
      "vatID": "GB123456789",
      "sameAs": [
        "https://www.google.com/maps?cid=YOUR_CID",
        "https://find-and-update.company-information.service.gov.uk/company/YOUR_NUMBER",
        "https://www.trustpilot.com/review/yourbusiness.co.uk",
        "https://www.linkedin.com/company/your-business-name"
      ]
    }
  ]
}

The fields that matter most for AI

1
sameAs — links your schema entity to external authoritative profiles. This is the single most impactful field in Organisation schema for AI visibility. Include your Google Business Profile URL, Companies House entry, Trustpilot profile, LinkedIn, and any other authoritative directory entries.
2
legalName — the formal registered name of your business, exactly as it appears on Companies House. This resolves ambiguity between trading names and legal names, which is a common source of entity confusion for AI systems.
3
@id — a permanent, unique URI identifying this organisation entity. Use your canonical website URL plus a fragment identifier like #organization. This ID is referenced by other schema types on your site, linking all your structured data to a single entity.
4
foundingDate — the year or full date your business was founded. Established businesses benefit from declaring this — longevity is a trust signal for AI systems answering queries that favour reliable, experienced operators.
5
logo — a URL pointing to your business logo image. Used by Google for Knowledge Panel display and by AI systems as a visual entity identifier.

How sameAs strengthens AI entity recognition

AI knowledge graphs work by building confidence that multiple data sources refer to the same entity. Without sameAs, an AI system seeing your website, your Google Business Profile, your Trustpilot page, and your Companies House entry may treat these as four separate signals about four potentially different entities. With sameAs, you explicitly declare the connections.

The result is a stronger entity confidence score — meaning AI is more willing to cite you, more likely to include you in "best" or "top-rated" answers, and less likely to confuse you with similarly named businesses in the same area or sector.

Common mistakes to avoid

Missing sameAs entirely

The most common and most costly omission. Many businesses add Organisation schema but do not include sameAs. Without it, much of the entity-consolidation value is lost.

Mismatched legalName and name

If your trading name is "Smith Plumbing" but your Companies House registration is "Smith Plumbing Services Ltd", both fields should reflect this accurately. Inconsistency creates entity ambiguity.

Duplicate @id values

If LocalBusiness and Organisation schemas both claim the same @id URI, this creates a conflict. Use distinct identifiers: #organization for the Organisation type and #local-business for LocalBusiness, or use your domain root for Organisation and let LocalBusiness reference it via parentOrganization.

Questions about Organisation schema

What is the difference between Organisation and LocalBusiness schema?
+
LocalBusiness schema identifies where your business is and what it does locally. Organisation schema identifies the legal and institutional entity behind the business — its legal name, registration numbers, founding date, and relationships to other entities. For AI visibility, Organisation schema builds a layer of institutional credibility that LocalBusiness alone does not provide.
Do I need Organisation schema if I already have LocalBusiness schema?
+
For most small businesses, a well-completed LocalBusiness schema with the sameAs field achieves most of what Organisation schema adds. Organisation schema becomes most valuable when you want to explicitly declare legal registration details, founding information, or relationships between entities — and when your business operates across multiple locations or under a parent brand.
What is the sameAs field and why does it matter?
+
The sameAs field links your schema entity to external authoritative profiles — your Google Business Profile URL, Companies House entry, Trustpilot profile, LinkedIn page, and others. It tells AI systems that these separate profiles all refer to the same real-world entity. This is one of the highest-value fields for reducing entity ambiguity and strengthening AI knowledge graph confidence about your business.