The sameAs Strategy: Connecting Your Entity

The schema.org sameAs property links your entity to its authoritative reference pages — Wikipedia, Wikidata, official profiles — so engines can confidently merge them into one identity. It won't directly lift citations, but it's a core disambiguation signal that strengthens recognition. Here's the markup and how to use it well.

What does sameAs actually do?

sameAs tells engines that the entity described on your page is the same thing as the entities at a list of reference URLs. When you point your Organization markup at your Wikipedia article, your Wikidata item, and your official profiles, you're giving engines an explicit, machine-readable bridge between your site and the authoritative records they already trust — exactly the entity disambiguation they need to link mentions confidently. It resolves "is this the same Acme as the one in Wikidata?" with a yes.

Does sameAs help with AI citations?

No — not directly, and it's important to be honest about that. Controlled testing found schema markup produces no measurable AI-citation lift, and sameAs is schema. Its value is entity clarity: it strengthens how reliably engines recognize and connect your entity, which is a precondition for the authority and credibility that do drive citations. Treat sameAs as plumbing that helps engines understand who you are — not as a lever that raises your citation rate on its own.

What's the JSON-LD?

Here's Organization markup with a sameAs array. Put it in a JSON-LD script on your homepage or about page, and replace the placeholders with your real entity details and authoritative URLs.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Acme Analytics",
  "url": "https://www.acme.example",
  "logo": "https://www.acme.example/logo.png",
  "description": "Acme Analytics builds AI visibility tracking for marketing teams.",
  "sameAs": [
    "https://en.wikipedia.org/wiki/Acme_Analytics",
    "https://www.wikidata.org/wiki/Q00000000",
    "https://www.linkedin.com/company/acme-analytics",
    "https://www.crunchbase.com/organization/acme-analytics",
    "https://x.com/acmeanalytics",
    "https://github.com/acme-analytics"
  ]
}

For a person (an author or executive), use Person with their own sameAs:

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Jordan Vega",
  "jobTitle": "Principal AEO Strategist",
  "worksFor": { "@type": "Organization", "name": "Acme Analytics" },
  "url": "https://www.acme.example/authors/jordan-vega",
  "sameAs": [
    "https://www.wikidata.org/wiki/Q00000001",
    "https://www.linkedin.com/in/jordan-vega",
    "https://x.com/jordanvega"
  ]
}

Which URLs belong in sameAs?

Include only URLs that unambiguously refer to the same entity, in rough order of authority:

1. 1

   Knowledge bases first

   Your Wikipedia article and Wikidata item — the references engines weight most for entity identity.

2. 2

   Official, verifiable profiles

   LinkedIn, Crunchbase, X, GitHub, YouTube, Facebook — accounts you control that clearly represent the entity.

3. 3

   Skip the padding

   Don't add marketing pages, partner links, or anything that doesn't represent the entity itself — noise weakens the signal.

4. 4

   Make links mutual where possible

   Ensure the linked profiles point back to your site, so the connections corroborate each other.

Where this fits in the Canon

sameAs is one declarative tool in building your entity — the disambiguation plumbing under entity AEO. It serves authority and credibility indirectly, by making the entity those pillars describe unmistakable to engines. Pair it with Wikidata and a Knowledge Panel, and see how to implement structured data for the wider markup picture.