There are probably six places on the internet that describe your company right now: your homepage, LinkedIn, Crunchbase, G2, and a directory listing nobody remembers submitting to. At least two are wrong or out of date. The sameAs property helps search engines connect these profiles and understand that they describe one company. Yet nobody on your team may have been assigned to make that decision easy for them.
What Does the sameAs Property 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 clearly identifies an item. Examples include 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 can point the sameAs property to its LinkedIn company page, Crunchbase profile, G2 or Capterra listing, and official homepage. The homepage acts as the canonical anchor. Google’s documentation notes you can provide multiple sameAs URLs. The working assumption is simple. More independent corroboration strengthens identity confirmation.
sameAs sits inside the same foundation as the site’s technical SEO baseline. Crawlability and indexing tell search engines that your pages exist. The sameAs property connects those pages to profiles on other domains. It helps clarify that they describe one company, not several unrelated businesses with similar names.
How sameAs Fits Into Your Company’s Search Identity
sameAs feeds the broader signal set a search engine already weighs when it decides how confidently to describe your company. It does not automatically verify your company. It also does not give you a Knowledge Panel, which follows a separate process.
Why Company Identity Confusion Matters
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 lack confidence tend to hedge. Your listing may then be treated more cautiously, even when the underlying page is excellent.
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. Google has clearly stated that inconsistent or duplicated identity creates a customer-facing problem. Its policies actively address this issue, so it is not just a cosmetic detail. That is reason enough to treat it as real, without dressing it up as something bigger than it is.
Where to Add the sameAs Property in Your Schema
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 website. Wikidata is usually not an option because most companies at this stage do not meet its notability requirements[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 Work Behind the sameAs Property
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.
Find and Compare Your Company’s Online Profiles
Nobody owns this task by default because it does not belong to one specific job title. It is not analytics or engineering. It is also rarely marketing’s first priority when a launch is due next week. As a result, inconsistencies build up. A LinkedIn page may still list a product name the company retired two years ago. A Crunchbase entry may show the wrong headquarters city. A G2 category may be close, but still inaccurate.
Create a Consistent Company Profile Checklist
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 to Check Whether Your sameAs Property Works
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.
These checks will not tell you 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 the sameAs property answers. Before drawing conclusions, understand how AI-referred traffic appears in your analytics.
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
- 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 ↩
- 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) ↩
- 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 ↩
- 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 ↩
- 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 ↩
Seeing these patterns at your company?
Book a free WebOps Diagnostic. I'll review your site before the call and share specific observations.
Book a Free Call →Frequently Asked Questions
No good evidence says so. A 2026 Ahrefs study tracking 1,885 pages that added JSON-LD found the change in AI citations was statistically indistinguishable from zero on ChatGPT and Google AI Mode, and slightly negative on Google AI Overviews. sameAs earns entity clarity and classic SEO value, not a citation shortcut.
As many as you have accurate, actively maintained profiles. There is no fixed minimum or maximum. Schema.org's own example shows a single URL; Google's documentation shows several in an array. Three to six is typical for a B2B SaaS company: LinkedIn, Crunchbase, G2 or Capterra, and the official site itself.
No. A Google Business Profile is a separate listing product Google hosts directly, built mainly for local and service businesses. sameAs is a schema.org property inside your own site's code that can reference a Google Business Profile among other URLs, but the two are unrelated systems solving different problems.
No. Wikidata requires a notability bar, typically a Wikipedia sitelink or serious independent coverage, that most B2B SaaS companies at seed-to-Series-D stage do not clear. Realistic sameAs targets for most companies are LinkedIn, Crunchbase, G2 and the official homepage, not Wikidata or Wikipedia.
In practice, nobody by default, which is why it drifts. It is not a specialist skill, just an unglamorous checklist: pull up each profile, compare name, category and description against the others, and fix what disagrees. It pairs naturally with whoever already owns the site's technical SEO baseline.