Schema field: sameAs
What this field is: sameAs is an array of URLs to other authoritative profiles that represent the same entity as this Organization or Person. It is the single most important, and most misunderstood, field for AI entity recognition.
Why it matters
Section titled “Why it matters”Engines use sameAs to disambiguate you: to confirm that your homepage, your Wikidata item, your LinkedIn, and your Crunchbase all describe one entity, not several. That is how the model reconciles scattered mentions into a confident, citable brand rather than a fuzzy one. A brand with a rich sameAs mesh resolves cleanly; a brand without one fragments across the labs’ memory.
How to fill it
Section titled “How to fill it”Provide an array (even for one link), in priority order, strongest surfaces first:
"sameAs": [ "https://www.wikidata.org/entity/Q12345678", "https://en.wikipedia.org/wiki/Example_Inc", "https://www.linkedin.com/company/example", "https://www.crunchbase.com/organization/example", "https://www.g2.com/products/example"]- Order: Wikidata first (it feeds the Knowledge Graph and training data), then Wikipedia, then high-authority directories (Crunchbase, G2, LinkedIn), then socials and industry directories.
- For a Person (an author), use their professional identities: LinkedIn, Google Scholar, GitHub, ORCID, personal site.
- Only real, live profiles. Do not pad the array with URLs that do not exist or do not point back at you.
- Use the canonical URL form. For Wikidata that is
wikidata.org/entity/Q..., not the/wiki/page.
Keep the array consistent everywhere it appears; the homepage Organization schema is the canonical copy. Aim for five or more entries. See E5 and E3 for the fuller playbook.