Implementing sameAs Links Correctly

A sameAs property in schema markup is one line of code and a genuinely common source of confusion: which URLs actually belong in it, how many is too many, and whether it does anything measurable at all. It's worth being precise about all three.

What sameAs actually is

sameAs is a schema.org property that lets a page declare "this entity described here is the same entity as the one described at these other URLs." For a local business, that typically means linking the Organization or LocalBusiness schema on the website to the business's Wikipedia page (if one exists), Wikidata entry (if one exists), Google Business Profile, LinkedIn company page, and other verified official profiles. It's a machine-readable disambiguation signal, not a backlink and not a citation in the SEO sense — it's closer to a business saying "here's proof these are all me" in a format a parser can read. Generative engine optimization explained covers where this kind of entity-facing markup fits in the wider AEO picture.

Why it matters for entity recognition, described honestly

Google's Knowledge Graph and other entity systems work by resolving mentions of a name to a specific real-world entity. A business named "Sunrise Diagnostics" is ambiguous on its own — there could be a dozen clinics with that name across India. sameAs helps disambiguate by pointing to the same identifiers across multiple platforms, which is one input among several that entity-resolution systems can use to link mentions together.

That's the honest version. What sameAs does not do is guarantee a Knowledge Panel, guarantee AI citation, or function as a ranking signal on its own. Google has never published sameAs as a confirmed ranking factor, and there's no controlled study showing it moves rank independently. Treat it as infrastructure that supports entity clarity, not a lever that moves numbers by itself.

Which URLs actually belong there

The general principle is: only link profiles the business actually controls and that are verifiably about the same entity, not every mention of the business name anywhere online. A reasonable list for an Indian local business: the official website itself (if linking from a subpage), Wikipedia and Wikidata (only if entries genuinely exist — never create thin, promotional entries just to have something to link), Google Business Profile, LinkedIn company page, verified Facebook and Instagram business pages, and major directory profiles where the business has claimed and verified the listing — Practo for healthcare, JustDial, IndiaMART for B2B, Sulekha, depending on category.

Leave out unclaimed directory mentions, review aggregator pages the business doesn't control, and anything where the name match is coincidental rather than confirmed. Business listing sites in India covers which directories are worth claiming in the first place, which is the prerequisite before any of them belong in a sameAs list.

Implementation, concretely

On the Organization or LocalBusiness JSON-LD block, sameAs takes an array of URL strings:

"sameAs": [
  "https://en.wikipedia.org/wiki/Example",
  "https://www.google.com/maps/place/...",
  "https://www.linkedin.com/company/example",
  "https://www.practo.com/example-clinic"
]

Each URL should be the canonical live URL for that profile, not a shortened or tracking-parameter version. Keep the list current — a stale sameAs pointing to a deleted or renamed profile is worse than a shorter, accurate list. Local business schema covers where this property sits inside the broader schema block, and schema markup for AI search covers how AI-facing extraction tends to use structured entity data like this alongside plain page content.

A common mistake: sameAs as a link-building substitute

Some sites pad the sameAs array with every social profile and mention they can find, treating it as a quasi-backlink list. This misreads what the property is for. A sameAs array with twenty loosely related URLs dilutes the disambiguation signal rather than strengthening it, because it makes the "same entity" claim less precise, not more thorough. Five to eight well-chosen, verifiably-controlled profiles do more than twenty scraped mentions. This is the same discipline NAP consistency at scale asks for with address data — precision over volume.

Multi-location businesses and sameAs

Each location with its own LocalBusiness schema needs its own sameAs pointing to that specific location's GBP listing and any location-specific directory profiles, not the parent brand's URLs repeated across every location page. A 20-branch chain that copies the head-office sameAs array onto every branch page is telling entity-resolution systems all 20 branches are the same entity, which they aren't. Multi-location local SEO guide and location pages SEO cover the broader location-differentiation problem this is one piece of.

Where this fits with entity authority more broadly

sameAs is one input into a much larger entity-authority picture that also includes consistent NAP data, GBP completeness, and mentions across authoritative third-party sources. Entity authority and SEO and entity SEO and the knowledge graph cover that fuller picture — sameAs supports it without being the whole thing.

Does adding sameAs schema improve my Google ranking? There's no published or confirmed mechanism where sameAs alone moves ranking. It supports entity disambiguation, which is one input among many into broader entity-authority signals, not a direct ranking factor on its own.

Should I include every social media profile in my sameAs array? No. Include only profiles the business genuinely controls and that are verifiably the same entity. A shorter, accurate list works better than a long, padded one.

Can I add a Wikipedia link to sameAs if my business doesn't have a Wikipedia page yet? No — never link to a page that doesn't exist, and never create a thin or promotional Wikipedia entry just to have one to link. Only include entries that genuinely exist and meet Wikipedia's own notability standards.

Does each location of a multi-location business need its own sameAs array? Yes. Each location's schema should point to that specific location's GBP listing and directory profiles, not a copy of the parent brand's array repeated across every page.

Related: structured data for AI answers and review schema markup cover adjacent schema implementation that typically sits alongside sameAs on the same page.

Angryturtle's entity infrastructure work covers schema and sameAs implementation as part of managed AEO services →