Organisation schema should answer a deceptively simple question:
Which organisation does this website actually represent?
Many sites stop after adding a business name and logo.
That is a start, but Schema.org provides considerably more information that can help describe an organisation, including its web address, registered legal name, contact details and external pages referring to the same entity.
One of the most useful fields to audit is sameAs.
Schema.org defines sameAs as a URL to another page that unambiguously indicates the identity of the same thing. Google also recognises sameAs in Organisation structured data and says multiple URLs can be supplied, including organisation profiles on social or review sites. Schema.org
That makes it useful for connecting:
Your website
to:
other authoritative pages representing the same business.
But it does not mean adding ten social profiles suddenly makes ChatGPT recommend you.
The job here is entity clarity, not schema quantity.
Table of Contents
- What Organisation schema actually declares
- Why entity ambiguity matters
- The sameAs property explained
- What should go inside sameAs?
- Should you include Companies House?
- Legal name versus trading name
- name, legalName and alternateName
- Organisation or LocalBusiness?
- The role of @id
- A copy-and-adapt JSON-LD example
- Common Organisation schema mistakes
- How to validate the implementation
- The limit of Organisation schema for AI search
- Frequently Asked Questions
What Organisation schema actually declares
Google describes Organisation structured data as a way to provide administrative details about a business and help Google disambiguate the organisation in search results. Google recommends placing it on the homepage or a single page describing the organisation, such as the About page. It does not need to be repeated independently across every page. Google for Developers
The markup can include information such as:
- name
- alternateName
- legalName
- url
- logo
- sameAs
- address
- telephone
- contact points
- business identifiers where applicable
Google says there are no universally required Organisation properties. Instead, businesses should add relevant properties that genuinely apply. Google for Developers
That is an important principle.
The objective is not:
How many properties can we add?
It is:
How clearly can we describe the real organisation behind this site?
For the wider schema hierarchy, see which schema types actually matter for AI search
Why entity ambiguity matters
Imagine the website uses:
Northstar Facilities
LinkedIn says:
Northstar FM
Companies House records:
Northstar Facilities Management Limited
An industry directory says:
North Star Facilities
and one old business profile still links to a previous domain.
A person can often work out that these probably refer to the same business.
A machine has to resolve that relationship from the evidence available.
Organisation structured data gives the website owner an opportunity to declare the business identity more explicitly.
Google itself says Organisation markup can help it disambiguate organisations. Google for Developers
That does not mean schema overrides contradictory external information.
It means you are giving search systems a cleaner declaration to compare with the rest of the web.
For the broader concept, internally link to your entity SEO explained for UK businesses article
The sameAs property explained
This is the field that deserves more attention.
Schema.org describes sameAs as a URL for a reference page that unambiguously indicates the item’s identity. Its examples include an official site, Wikidata or Wikipedia. Schema.org
Google’s Organisation documentation says sameAs can point to pages on other websites containing additional information about the organisation, including social-media or review profiles, and allows multiple URLs. Google for Developers
In practical terms, you are saying:
The organisation described here is the same organisation represented by these URLs.
That is much more precise than simply placing social icons in your footer.
But there is one important rule:
Do not use sameAs as a backlink list
A page mentioning your company is not automatically the same entity.
For example:
Good candidate: your official LinkedIn company profile.
Potential good candidate: an accurate Companies House company profile for the same registered business.
Poor candidate: an article that merely mentions your company.
Poor candidate: a generic directory category page containing hundreds of companies.
Poor candidate: somebody else’s LinkedIn post mentioning you.
The referenced page should identify your organisation, not simply contain your name
What should go inside sameAs?
There is no published ideal number.
Quality matters more than volume.
For a typical UK B2B company, I would inspect these first:
Official company social profiles
For example:
- LinkedIn company page
- Facebook business page
- Instagram business profile
- YouTube channel
Only include accounts that genuinely represent the organisation.
Relevant authoritative business profiles
A credible trade body, professional association or industry directory can make sense when the profile uniquely represents your organisation.
Do not add every directory listing you have ever created.
Companies House
For an incorporated UK company, the correct Companies House profile can provide a particularly clear external identity reference.
Companies House is the UK’s official register of companies, and its public service contains information including registered company name, registered address, company type, status and incorporation information. GOV.UK
However, this is a practical entity-matching use of sameAs, not a Google-documented ranking factor.
Should you include Companies House?
For a registered UK limited company, it is worth considering.
The logic is simple.
A Companies House profile contains identifiers and administrative details relating to the registered company. Companies House makes this public company data available through its official register. GOV.UK
If the page clearly represents the same legal organisation described by your website, it can fit the Schema.org definition of a reference URL identifying the same entity.
But check the details first.
Do not blindly connect:
Brand A
to:
Limited Company B
unless they really are the same organisation and your markup explains that relationship accurately.
Companies House also notes that information submitted to the register is public, and its search service carries a disclaimer that Companies House does not itself check the accuracy of all filed information. Company Information
So use the correct profile, but do not treat its existence as proof of every commercial claim on your website.
Legal name versus trading name
This is another common source of confusion.
Suppose your customers know the business as:
Northstar Facilities
but the registered company is:
Northstar Facilities Management Limited
Do not force one field to do both jobs.
Schema.org provides legalName specifically for the registered legal name of an organisation. Google describes legalName as the registered legal name when it differs from the main name property. Google for Developers
That gives us:
name: Northstar Facilities
legalName: Northstar Facilities Management Limited
If the company is commonly known by another legitimate variation, alternateName can represent that too. Google defines alternateName as another common name the organisation goes by. Google for Developers
For example:
alternateName: Northstar FM
Now the schema is describing the real
name, legalName and alternateName
| Property | Use It For |
|---|---|
| name | The main business name customers see |
| legalName | The registered legal organisation name |
| alternateName | Another genuine common name or abbreviation |
Do not create keyword-heavy variations such as:
Northstar Facilities London Facilities Management Company Best FM Provider UK
That is not an alternate business name.
It is keyword stuffing inside structured data.
Keep these fields factual.
Organisation or LocalBusiness?
They are related.
Schema.org’s LocalBusiness is a subtype of Organization.
Google specifically recommends using the most precise LocalBusiness subtype for businesses such as physical stores or restaurants, and following both its LocalBusiness and Organisation guidance. Google for Developers
A practical distinction:
Use Organisation when
You are describing the company at corporate level.
This is common for:
- B2B firms
- national businesses
- consultancies
- software businesses
- companies without a customer-facing physical location
Consider LocalBusiness when
A real physical business location is central to how customers interact with the organisation.
Examples include:
- dental clinics
- restaurants
- salons
- retail stores
- physical service locations
Do not create fake LocalBusiness entities for every town you serve.
A service area is not automatically a physical business location.
The overlooked role of @id
There is another useful field that makes a schema graph cleaner:
@id
This creates a stable identifier for the organisation inside your own structured-data graph.
For example:
“@id”: “https://example.co.uk/#organization”
Other entities can then refer back to that same organisation.
A Service could say its provider is:
“provider”: {
“@id”: “https://example.co.uk/#organization”
}
Instead of independently recreating the business entity on every page.
This is especially useful when multiple schema types connect:
Organization
→ Service
→ Article
→ WebPage
The objective is one coherent graph, not several contradictory versions of the same business.
Copy-and-adapt Organisation schema
Here is a simple UK example:
<script type=”application/ld+json”>
{
“@context”: “https://schema.org”,
“@type”: “Organization”,
“@id”: “https://www.example.co.uk/#organization”,
“name”: “Northstar Facilities”,
“legalName”: “Northstar Facilities Management Limited”,
“alternateName”: “Northstar FM”,
“url”: “https://www.example.co.uk/”,
“logo”: “https://www.example.co.uk/images/logo.png”,
“description”: “Facilities management services for commercial organisations across the UK.”,
“telephone”: “+44 20 1234 5678”,
“email”: “hello@example.co.uk”,
“sameAs”: [
“https://www.linkedin.com/company/example/”,
“https://find-and-update.company-information.service.gov.uk/company/00000000”
]
}
</script>
Replace every example with real information.
Do not copy:
- fake telephone numbers
- invented social profiles
- somebody else’s Companies House URL
- descriptions that are not supported by the website
Also check whether your SEO plugin already outputs Organisation schema before inserting another block manually.
Common Organisation schema mistakes
Adding every external URL to sameAs
Only use URLs that genuinely represent the same entity.
Using the registered name everywhere
Your name does not need to become the long registered legal company name if customers genuinely know you by the trading name.
Use legalName for that distinction.
Creating several competing Organisation entities
Check WordPress plugins, themes and custom code.
You may already have:
- Yoast schema
- AIOSEO schema
- theme-generated schema
- manually inserted JSON-LD
before adding another block.
Leaving old profiles connected
If an external page contains an old name, previous domain or incorrect company details, investigate whether it is still an appropriate identity reference.
Treating sameAs as an AI optimisation hack
It is an entity relationship.
That is valuable enough.
You do not need to invent an unsupported ranking claim around it.
How to validate the implementation
Start by inspecting the live page.
Then validate the structured data.
Google recommends using its structured-data testing workflow and URL Inspection to confirm how Google sees the implementation. Google for Developers
Also manually check every sameAs URL.
Ask:
Does the page resolve?
Does it describe this exact company?
Is the name accurate?
Is the location accurate where relevant?
Is the company still active on that profile?
Does the URL belong to another business with a similar name?
Syntax validation cannot answer those questions.
A technically valid link to the wrong company is still wrong.
The honest limit of Organisation schema for AI search
Organisation markup is useful because structured data gives machines explicit information about the page and entity.
Google confirms that Organisation markup can help it understand administrative information and disambiguate an organisation. Google for Developers
But we should stop there.
There is no published formula saying:
Five sameAs URLs = better AI rankings.
There is no documented threshold for the number of profiles.
And adding a Companies House URL does not guarantee a citation, AI Overview or recommendation.
Good entity optimisation extends beyond schema.
You also need consistency between:
- the website
- company profiles
- service descriptions
- business directories
- reviews where relevant
- industry memberships
- external coverage
The schema is your declaration.
The wider web is the evidence systems can compare it against.
For the broader strategy, link naturally to Generative Engine Optimisation
Frequently Asked Questions About Organisation Schema
How many sameAs URLs should I add?
There is no official ideal number.
Google allows multiple sameAs URLs. Add the external pages
that genuinely represent the same organisation rather than trying to reach
an arbitrary count.
Five strong identity references are more useful than twenty irrelevant directory URLs.
Should I include social profiles?
Yes, where they are official organisation profiles.
Google specifically gives social-media profile pages as an example of URLs
that can be used with sameAs.
Use the company profile rather than an employee’s personal account unless you are marking up that individual separately as a Person.
Should I use Organisation or LocalBusiness?
Use the type that accurately describes the business.
For a business with a genuine physical customer-facing location, Google recommends using the most specific LocalBusiness subtype and following LocalBusiness guidance as well as Organisation properties.
Google: Organisation structured dataA national B2B consultancy without a customer-facing location may be better represented at company level as an Organisation.
Does Companies House help?
A correct Companies House profile can provide a useful external reference for a UK incorporated company because the public register contains the company’s registered identity information.
GOV.UK: Companies House register That makes it potentially appropriate for sameAs where it
clearly represents the same entity.
But there is no Google documentation saying a Companies House sameAs link directly improves rankings or AI recommendations.
What if my trading name is different from my company name?
Use separate properties.
Your visible trading name can be the name, while the registered
company name can use legalName.
If you genuinely use another recognised variation or abbreviation, alternateName may also apply.
Does sameAs make ChatGPT understand my company?
There is no published OpenAI rule saying that adding sameAs causes ChatGPT to identify or recommend a business.
Use it because it creates a standardised identity relationship in Schema.org and because Google recognises it within Organisation structured data.
Do not turn that into a guaranteed AI visibility claim.
Entity clarity starts with getting your own declaration right
Organisation schema will not build your reputation for you.
It can, however, make the identity you are declaring much clearer.
For most businesses, check these first:
name
Is this the actual name customers know?
legalName
Is your registered company name represented correctly if it differs?
alternateName
Do you have a genuine commonly used alternative?
url
Does it point to your canonical website?
sameAs
Do the external URLs genuinely represent this same organisation?
Contact and location details
Do they agree with the rest of your public information?
That is more valuable than stuffing the graph with every property your SEO plugin provides.
The principle is simple:
One organisation. Clear identity. Consistent supporting references.
Then let the wider content, reputation and third-party evidence do their jobs.
Get your free AI visibility audit
For broader GEO strategy:
For the schema priority guide:
https://lobodigital.co.uk/schema-types-that-matter-ai-search
