AI Search

sameAs (schema property)

Also known as: sameAs, schema sameAs

The `sameAs` property in schema.org links an entity declared on your site to its representations elsewhere, Wikidata, Wikipedia, LinkedIn, GitHub, Crunchbase, Bloomberg profiles, social media profiles. It's the bridge that connects your brand's on-site entity declaration to the broader web entity graph. AI search engines use sameAs heavily for entity disambiguation, making it one of the highest-leverage single schema properties to populate.

How sameAs works in JSON-LD

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://yourdomain.com/#organization",
  "name": "Your Brand",
  "sameAs": [
    "https://www.wikidata.org/wiki/Q12345",
    "https://en.wikipedia.org/wiki/Your_Brand",
    "https://www.linkedin.com/company/your-brand/",
    "https://twitter.com/yourbrand",
    "https://github.com/yourbrand",
    "https://www.crunchbase.com/organization/your-brand"
  ]
}

sameAs takes an array of URLs. Each URL should resolve to an authoritative profile / page representing the same entity.

When ChatGPT, Claude, Perplexity, or Gemini need to disambiguate which “X” the user is asking about, the entity graph (Organization + sameAs links) provides the answer:

  • Without sameAs: the model guesses based on context, might conflate your brand with a similarly-named one
  • With sameAs: the model has a graph of authoritative identifiers and can confidently attribute facts

The sameAs property is the cheapest, highest-impact AI-search infrastructure investment for most brands.

Required sameAs targets

For B2B brands, prioritize in this order:

  1. Wikidata Q-entity (if you have one, see Wikidata)
  2. Wikipedia (if eligible, long-term, but worth pursuing)
  3. LinkedIn company page
  4. Twitter / X profile (if active)
  5. GitHub organization (for developer-focused brands)
  6. Crunchbase profile
  7. Bloomberg profile (for public or PR-active brands)

For local businesses, add:

  • Google Business Profile URL
  • Yelp profile
  • Industry-specific directory profiles

Common mistakes

  • Linking to your own site’s pages, sameAs is for EXTERNAL representations, not internal pages
  • Linking to outdated profiles, if your Twitter handle changed, update the sameAs
  • Inconsistent profile names, the LinkedIn profile should match the Organization name in your schema
  • Linking to vanity / personal profiles instead of organization profiles, link to the brand’s, not the founder’s, unless the founder IS the brand

The reciprocity question

Some brands ask: do external profiles need to link BACK to my site (reciprocal sameAs)?

The answer: not technically required, but helpful. When Wikipedia/Wikidata reference your website as the official URL, you’ve created a verifiable round-trip that increases AI confidence in the entity. Most sameAs targets (LinkedIn, GitHub, Crunchbase) have a website field, make sure your website is listed there.

Resocial perspective

Most schema implementations we audit have weak or empty sameAs arrays. Building a complete sameAs graph is one of the first things our Schema Markup service does. The work is straightforward; the AI citation rate impact is measurable within 3-6 months.

Looking for hands-on help with this?

Not sure where to start?

Describe your problem and our AI maps it to the closest Resocial service.

Describe my problem

Free SEO audit

60+ dimensions, 48-hour turnaround.

Get a Free SEO Audit

Enterprise RFP

Tailored proposal in 5 business days.

Submit an Enterprise RFP