The sameAs Property: How Search Engines and Assistants Confirm Who You Are

There are probably six places on the internet that describe your company right now: your homepage, LinkedIn, Crunchbase, G2, a directory listing nobody remembers submitting to. At least two are wrong or out of date. Search engines have to decide whether those six pages describe one company or several, and nobody on your team was ever assigned to make that decision easy for them.

What Does sameAs Actually Do?

sameAs tells search engines and assistants which other pages on the internet describe the exact same company as the one they are currently reading. Schema.org defines it as a URL that unambiguously indicates an item’s identity, such as a Wikidata entry or the company’s official website^[1]. Google lists it as a recommended field on Organization markup, not a required one^[2].

You can list more than one. A typical B2B SaaS company points sameAs at its LinkedIn company page, its Crunchbase profile, its G2 or Capterra listing, and its own homepage as the canonical anchor. Google’s documentation notes you can provide multiple sameAs URLs. The working assumption is that identity confirmation gets stronger with more independent corroboration, not weaker.

sameAs sits inside the same foundation as the site’s technical SEO baseline. Crawlability and indexing tell a search engine your pages exist. sameAs tells it those pages, and the ones sitting on other domains, describe one company rather than several unrelated ones that happen to share a name.

sameAs feeds the broader signal set a search engine already weighs when it decides how confidently to describe your company. It is not a switch you flip to get verified, and it is not the same thing as claiming a Knowledge Panel, which is its own separate process.

Why Does Identity Confusion Cost You Business?

Identity confusion is not hypothetical, it is a stated policy problem. Google’s own guidance on business profiles says plainly that “multiple profiles for the same business may mislead your customers and are against our policies”^[3]. Nobody signed up to own that consistency. It accumulates, one new listing, one rebrand, one acquired product name at a time, until six pages disagree.

Strip the schema vocabulary and the buyer-facing version is plain: a search engine or an assistant reading six descriptions of your company that do not quite match has to guess whether it is looking at one company or several. Machines that are not certain tend to hedge, and a hedge usually means your listing gets treated more cautiously, not more confidently, however good the underlying page is.

This is not a story about lost rankings with a number attached to it. Nobody has a clean, sourced figure for what six disagreeing profiles cost a company in trust, and a page that invents one is guessing. What is documented is Google’s own stated position that inconsistent or duplicated identity is a customer-facing problem it actively polices, not a cosmetic detail. That is reason enough to treat it as real, without dressing it up as something bigger than it is.

Where to Put It: Placement Without the Code Wall

sameAs goes inside your Organization schema, most often on the homepage, as a list of URLs pointing to profiles your company actually controls or is officially listed on. For most B2B SaaS companies, that means LinkedIn, Crunchbase, G2 and the official site itself, not Wikidata, which most companies this size do not clear the notability bar for^[4].

The list does not need to be exhaustive on day one. Two or three accurate, live URLs beat six where half are stale. Wikidata and Wikipedia can join the list later if the company ever clears that bar; most do not, and that is fine.

The Admin Half Nobody Does

Adding sameAs itself takes minutes. The larger job is unglamorous: going through every one of those profiles and making the name, category and description actually agree with each other. That admin pass carries more of the value than the markup does, and it needs no code at all.

Nobody owns this by default because it is not a job title anywhere. It is not analytics, it is not engineering, and it is rarely marketing’s first priority when a launch is due next week. So it drifts: a LinkedIn page still lists a product name the company retired two years ago, a Crunchbase entry has the wrong headquarters city, a G2 category is close but not quite right.

The checklist is short and does not need a specialist. List every profile you can find: Google Business Profile, LinkedIn company page, Crunchbase, G2 or Capterra, any industry directory, Wikipedia or Wikidata if one exists. For each, check the company name, the one-line description and the category against every other listing. Fix what disagrees. That is the whole job, and it is the larger share of what makes identity clarity real.

How Do You Know It Worked?

Three checks, none of which require a developer. First, view the page source or run the homepage through Google’s Rich Results Test and confirm the sameAs array is present with the right URLs. Second, open each linked profile and confirm the name and description still match. Third, re-check it after anyone else edits a profile.

What this will not tell you is whether an assistant now cites your company more often. A 2026 Ahrefs study that tracked 1,885 pages adding JSON-LD found the resulting change in AI citations was statistically indistinguishable from zero on ChatGPT and Google AI Mode, and slightly negative on Google AI Overviews^[5]. That is a separate question from the one this property answers, and it is worth understanding how AI-referred traffic actually shows up in your analytics before drawing conclusions from either number.

sameAs and the admin pass behind it are entity clarity and classic SEO, earned the same way they always have been: by making the facts about your company agree with themselves everywhere they appear. If your marketing site carries the other schema types that carry real weight, this one closes a gap those do not touch.

Sources

1. Schema.org, sameAs property definition – Continuously maintained reference documentation (accessed 2026-08-18); defines sameAs as a URL that unambiguously indicates an item’s identity, e.g. a Wikidata entry or official website ↩
2. Google Search Central, Organization structured data – Continuously maintained documentation (accessed 2026-08-18); lists sameAs as a recommended, not required, Organization property, describing it as a URL to a page with additional information about the organization (e.g. a social media or review site profile) ↩
3. Google Business Profile Help, duplicate profiles policy – Continuously maintained policy documentation (accessed 2026-08-18); states multiple profiles for the same business may mislead customers and are against Google’s policies ↩
4. Wikidata:Notability – Continuously maintained policy documentation (accessed 2026-08-18); an item qualifies only with a Wikipedia sitelink, clear identifiability via serious independent references, or a structural need, a bar most B2B SaaS companies do not clear ↩
5. Ahrefs, We Tracked 1,885 Pages Adding Schema. AI Citations Barely Moved. – Matched difference-in-differences study, 1,885 pages that added JSON-LD Aug 2025-Mar 2026 vs. roughly 4,000 control pages, published May 2026; found no statistically significant citation lift on ChatGPT or Google AI Mode, and a small significant decline on Google AI Overviews ↩

Written by Yasser Soliman

Fractional Head of WebOps

I've spent 5+ years embedded in marketing teams at B2B SaaS companies. I own the marketing website — performance, analytics, SEO, integrations — so your team ships without bottlenecks.