What Is the sameAs Property?
sameAs is a Schema.org property that points from an entity described on your page to other URLs identifying that same entity, such as a Wikipedia article.
sameAs is a Schema.org property that points from an entity described on your page to other URLs identifying that same entity, such as a Wikipedia article, a Wikidata item, or an official profile. It is not a link-building device and carries no endorsement. Search engines read it to decide whether two records describe one thing or two separate things.
Why sameAs matters
Search engines do not file your page under its title. They file it under an entity, and every entity has to be told apart from every other entity carrying a similar name. If your company shares a name with a band, a suburb, or a rival on another continent, something has to choose.
Without a declared reference, that choice falls back on inference from your copy, your links, and whatever third parties happen to have written. Inference is fine for a national bank. It fails for a four-person consultancy with a common trading name. The cost shows up as a knowledge panel blending two organisations, or an AI-generated summary crediting someone else’s history to you. None of that is fixed by markup alone, though. If the page never states plainly what the business is, no property rescues it, which is why it pays to tighten the copy around one entity before you touch the JSON-LD.
What search engines do with sameAs
Schema.org defines sameAs as the URL of a reference page that unambiguously indicates the item’s identity. The word doing the work in that definition is “unambiguously”. The property is a pointer, not a claim about quality.
- You declare an entity. A JSON-LD node typed Organization, Person, or LocalBusiness, ideally with a stable
@idso the same entity can be referenced from every template on the site. - You attach reference URLs. sameAs takes a single URL or an array. Each one should resolve to a page about the entity itself, not a page that merely mentions it.
- The engine fetches and compares. The target is crawled like any other URL. Name, location, and description are compared against what your page asserts.
- Corroboration decides the outcome. Your markup is a one-way claim. It becomes useful when the destination independently agrees, which is why a claimed, filled-out profile beats an empty placeholder.
- The strongest references win. A Wikidata item that already links back to your domain settles identity faster than a dozen thin directory listings pointing nowhere in particular.
| Reference URL you list | What it actually contributes |
|---|---|
| Wikidata item for the organisation | Machine-readable identity with existing cross-references |
| Wikipedia article about the organisation | Strong corroboration, if the article genuinely exists |
| Official company register or regulator listing | Verifiable legal identity, useful for local and finance |
| Claimed, active social profile | Weak confirmation that the name maps to this business |
| Fifth unclaimed directory listing | Nothing measurable |
Google’s Organization structured data documentation lists sameAs among the properties it reads, and does not publish what weight any individual value carries. Treat it as one input into entity resolution rather than a control you operate. Naming and describing an entity consistently across every template is what makes entity resolution work in your favour, and sameAs is one small part of that.
The blunt version
sameAs does not build authority. It cannot. A value inside a JSON-LD block is not a hyperlink a crawler follows for link equity; it is a field in a data structure, and the destination gets nothing from being listed. Adding fourteen social profiles to your homepage markup will not move a ranking, because that was never the mechanism.
What it does is disambiguate. Two profiles that genuinely confirm who you are will do the job that twenty scraped directory URLs cannot. Past the point where identity is settled, each extra entry adds nothing except maintenance, and dead profiles you stopped updating years ago are worse than absent ones.
Follow the incentive. “Entity SEO” packages that bundle thirty profile creations are selling volume, because volume is easy to invoice and easy to screenshot. Disambiguation is a yes-or-no outcome, so it makes a poor monthly deliverable. If you already have a claimed profile on the two platforms your sector actually uses, the remaining twenty-eight exist to justify the fee. The signals that genuinely shift how a business is assessed sit in the experience and trust signals Google weighs, not in the length of a URL array.
Example
Say a Manchester accountancy firm called Northgate Partners shares its name with a US software vendor and a Canadian property developer. Its knowledge panel keeps pulling the software vendor’s logo. The firm adds an Organization node with a stable @id, then a sameAs array holding three URLs: its Companies House record, its ICAEW listing, and its claimed LinkedIn page. Each of those pages names the firm, states Manchester, and describes accountancy. The claim now corroborates in three independent places. Nothing about the firm’s authority changed and no ranking moved directly. What changed is that a machine deciding between three organisations with one name has evidence pointing at the right one.
FAQ
Does sameAs pass link equity?
No. The value sits inside a structured data block, not in an anchor tag, so there is no link for a crawler to follow and nothing to pass. Listing a partner or a publication in sameAs does not help that destination and does not help you. Treat it as identity metadata only.
How many sameAs URLs should I include?
As many as genuinely identify the entity, which for most businesses is between two and five. Quality of corroboration beats quantity every time. A claimed profile that states your name, location, and sector is worth more than ten scraped directory pages that repeat a phone number and nothing else.
Can I use sameAs on a Person as well as an Organization?
Yes. Author and Person nodes take sameAs the same way, and it is often more useful there, because human names collide far more often than company names. Point it at profiles the person genuinely controls or is verifiably credited on, such as a professional register, a publisher bio, or an academic profile.
Related terms
- Entity SEO — the wider practice sameAs contributes one small signal to.
- Link Reclamation — recovering real links, which is the work sameAs is often mistaken for.
- Anchor Text Ratio — how the anchors on genuine links are distributed, a separate question entirely.
If someone is selling you sameAs as a way to build authority, they are selling a data field as a backlink. Ask them which specific ambiguity the extra profiles are meant to resolve, and listen for whether they can name one.