What is sameAs (Schema.org)?

What is sameAs (Schema.org)?

sameAs is a property defined in the Schema.org vocabulary that declares "this entity is the same as the entity described at this other URL." It accepts one or more URIs—typically Wikipedia pages, Wikidata entries, social media profiles, and official directory listings—and tells search engines that all those URLs refer to the same real-world thing. Google's Knowledge Graph relies heavily on sameAs to disambiguate entities: a business named "Mercury" could be a planet, a car brand, or a fintech startup, and sameAs URLs resolve that ambiguity. The property was part of the original Schema.org 1.0 release in June 2011 and applies to any Thing type, meaning it works on Person, Organization, LocalBusiness, Product, and more. We use sameAs on virtually every Organization and Person schema block we ship because it's one of the cheapest ways to strengthen entity signals for AEO and Knowledge Panel eligibility.

How it works

sameAs takes an array of URLs as its value. Each URL should be a canonical, publicly accessible page that describes the same entity. Under the hood, search engines treat these as co-reference signals—evidence that entity A on your site is the same as entity A on Wikipedia, LinkedIn, Crunchbase, etc.

Here's a typical JSON-LD implementation for an organization:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Social Animal",
  "url": "https://socialanimal.dev",
  "sameAs": [
    "https://www.wikidata.org/wiki/Q-EXAMPLE",
    "https://www.linkedin.com/company/socialanimaldev",
    "https://twitter.com/socialanimaldev",
    "https://github.com/socialanimaldev"
  ]
}

Key technical details:

• Order doesn't matter, but we always put Wikidata and Wikipedia first because Google's Knowledge Graph ingests those with the highest confidence.
• Only link to pages you control or that genuinely describe you. Google's structured data guidelines warn against spammy sameAs usage, and we've seen manual actions on sites that pointed sameAs to unrelated high-authority pages.
• The URLs must resolve. A 404'd sameAs link is worse than no link—it signals a stale or untrustworthy entity reference.
• sameAs is not owl:sameAs. Schema.org's sameAs is looser than the OWL strict logical equivalence. It means "substantially the same entity," not "logically identical in all properties."

Google processes sameAs in both JSON-LD and Microdata, but JSON-LD is our default—it's what Google explicitly recommends as of their 2024 structured data docs.

When to use it

sameAs is most valuable when you're trying to establish or reinforce an entity's identity in Google's Knowledge Graph, AI answer engines like Perplexity or ChatGPT with browsing, and Bing's entity understanding.

Use sameAs when:

• You want a Google Knowledge Panel for a person, brand, or organization
• You're implementing entity SEO and need to disambiguate a common name
• You're building AEO content and want AI engines to confidently attribute facts to the right entity
• Your brand has verified social profiles, a Wikidata entry, or a Wikipedia page
• You're marking up local businesses with multiple directory listings (Yelp, BBB, etc.)

Skip sameAs when:

• You don't have real, authoritative external profiles yet—pointing to a Twitter account with 3 followers won't help
• The entity is a generic product without a distinct public identity
• You're tempted to link to pages that mention your entity but aren't about your entity

sameAs vs alternatives

sameAs and url are complementary, not interchangeable. url is "where to find this entity's page," while sameAs is "where else this entity is described." We always include both. The identifier property is useful for machine-readable IDs (like a DUNS number), but it doesn't carry the same entity-resolution weight with Google as sameAs pointing to Wikidata.

Real-world example

On a recent project for a SaaS founder looking to earn a Google Knowledge Panel, we added Person schema with sameAs pointing to their Wikidata entry (which we helped create with verifiable references), LinkedIn profile, Twitter/X account, and a Forbes contributor page. Within six weeks of the Wikidata entry going live and the structured data being indexed, the Knowledge Panel appeared for branded searches. Before this, Google was confusing the founder with two other people sharing the same name. The sameAs array—especially the Wikidata URI—was the disambiguation signal that tipped it. We've repeated this pattern on 50+ projects, and the Wikidata + sameAs combo remains the single most reliable path to Knowledge Panel generation we've found.