GEO / AI search

Schema.org sameAs

Q: What is the schema.org sameAs property?

sameAs is a schema.org property that links an entity to other references to the same concept — usually Wikipedia, Wikidata, LinkedIn, Facebook. It signals to search engines and LLMs: ”this is the same entity as the one over there.”

Q: Where is sameAs used?

In Organization and Person schemas. For companies: links to Wikipedia, Wikidata, the LinkedIn company page, Crunchbase. For authors: Wikipedia, Wikidata, LinkedIn profiles, ORCID (for researchers). Format: an array of URLs.

Q: Does sameAs influence rankings?

Indirectly, and strongly so. sameAs helps Google recognise entity connections. The consequence: better Knowledge Graph integration, more frequent appearances in the Knowledge Panel, a higher chance of being cited in AI answers. No direct ranking boost, but an important building block of trust.

Q: How do you check sameAs for errors?

With the schema.org validator. Common errors: an incorrect Wikidata URL (with special characters), a missing https prefix, a linked resource that does not exist. Rankmio checks sameAs links automatically when you publish from the Content Studio.

Also known as: sameAs, rdfa sameAs, Schema sameAs

Schema.org sameAs is the property used to link an entity on a web page to its unique external identity URL — usually on Wikidata, Wikipedia, LinkedIn, Twitter/X, Crunchbase or other authoritative data sources. sameAs states explicitly: ”this thing here is exactly the same as that one over there”. For GEO it is the most important bridge between your own website and knowledge graphs — AI engines can use sameAs to link entities and build trust.

Where sameAs is used

Organization — your own brand, with sameAs pointing to the Wikidata Q number, Wikipedia, LinkedIn, Crunchbase, Twitter.
Person — author byline with sameAs pointing to Wikidata, LinkedIn, ORCID, Twitter — an important E-E-A-T lever.
Product — your own products with sameAs pointing to the manufacturer entry and, where applicable, Wikipedia.
Place — location linked to a Wikidata geo entity.
DefinedTerm — glossary term with sameAs pointing to the Wikidata concept entity (e.g. SEO Q180711, AI Q11660).
About / mentions in Article — topic entities with sameAs pointing to Wikidata.

A concrete example of the markup

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Rankmio",
  "url": "https://rankmio.de",
  "sameAs": [
    "https://www.wikidata.org/wiki/Q...",
    "https://www.linkedin.com/company/rankmio",
    "https://twitter.com/rankmio"
  ]
}

This tells Google: ”the website rankmio.de is the official website of the Wikidata entity Q… — the same brand as the LinkedIn entry and the Twitter account.”

The most common mistake: sameAs on the article instead of the entity

An article about search engine optimisation is not the same thing as the concept of search engine optimisation. Even so, the Wikidata address of the topic often ends up directly in the Article object. The markup then claims the article is that concept.

Correctly, sameAs sits one level down, on the Thing inside about or mentions:

{
  "@type": "Article",
  "about": [{
    "@type": "Thing",
    "@id": "https://www.wikidata.org/wiki/Q180711",
    "name": "Search engine optimisation",
    "sameAs": ["https://en.wikipedia.org/wiki/Search_engine_optimization"]
  }]
}

On the Article itself, sameAs only belongs there when the same text also lives at a second address — a syndicated copy, for instance. Then the identity claim is true.

How to spot the mistake: the same entities appear twice in the object, once flat in sameAs and once as a Thing in about. When you see that, the flat list can go.

sameAs for glossary and guide content

For every glossary entry and every in-depth guide article: mark up the main entities in the Article schema as about with a sameAs link to Wikidata, and related terms as mentions. The effect: AI engines recognise the thematic depth not only from the full text, but from the explicit structured networking of entities. A domain whose content is fully linked via sameAs signals considerably more authority than one without — even if the backlink structure does not change.

Example from practice

Example: A magazine website had no sameAs markup at all for 80 main articles. Implementation per article: Article schema with an about list of the 3–5 central main entities, each with sameAs pointing to Wikidata and Wikipedia. Author byline with sameAs pointing to the author's LinkedIn. Organization schema in the site footer with all official brand profiles. After 12 weeks of citation tracking: the appearance rate in AI Overviews rose from 18 % to 47 %, and in ChatGPT answers from 8 % to 31 % — with an unchanged backlink structure. The GEO lever came solely from the structured entity linking.

Frequently asked questions

What is the schema.org sameAs property?

sameAs is a schema.org property that links an entity to other references to the same concept — usually Wikipedia, Wikidata, LinkedIn, Facebook. It signals to search engines and LLMs: ”this is the same entity as the one over there.”

Where is sameAs used?

In Organization and Person schemas. For companies: links to Wikipedia, Wikidata, the LinkedIn company page, Crunchbase. For authors: Wikipedia, Wikidata, LinkedIn profiles, ORCID (for researchers). Format: an array of URLs.

Does sameAs influence rankings?

Indirectly, and strongly so. sameAs helps Google recognise entity connections. The consequence: better Knowledge Graph integration, more frequent appearances in the Knowledge Panel, a higher chance of being cited in AI answers. No direct ranking boost, but an important building block of trust.

How do you check sameAs for errors?

With the schema.org validator. Common errors: an incorrect Wikidata URL (with special characters), a missing https prefix, a linked resource that does not exist. Rankmio checks sameAs links automatically when you publish from the Content Studio.

Used in Rankmio for

sameAs check in the GEO audit

Go to the feature →

Last updated: 2026-06-17 · Browse all glossary entries