Organization Schema sameAs: Give Google One Brand Identity
The sameAs property in your Organization schema is a list of URLs — your LinkedIn, Facebook, Instagram, Wikidata or Crunchbase pages — that tells Google and AI engines that all those profiles belong to the same business as your website. schema.org defines sameAs as the URL of a reference page that “unambiguously indicates the item’s identity,” and Google lists it among the Organization properties that help it identify your organization. Put it in the Organization block on your homepage or About page, point it only at profiles where your name, logo and details match, and you hand search engines one connected identity instead of a scattered one.
This matters more in 2026 than it did a year ago. Google’s AI Overviews and AI Mode increasingly cite brands they can resolve as a single, verified entity, and schema.org now reports sameAs in use on more than 10 million domains. If your own profiles disagree about your name or link to dead pages, you are competing against your own footprint — and an AI engine has no clean way to tell which “Northside Dental” you are.
What Organization schema sameAs actually does
Search engines don’t only index pages; they build a graph of entities — people, places and organizations — and try to decide which real-world thing each page is about. Your Organization markup is how you declare, in machine-readable form, that a specific business exists and what it is called. The sameAs array is the connective tissue: each URL is a signal that a separate profile belongs to that same entity. That is a different job from your page-level markup. If you are still deciding which types to run at all, start with our rundown of the best schema types for AI search, then come back to wire up the Organization block the right way.
Placement is simple but easy to get wrong. Google recommends putting Organization data on your homepage or a single About page — not duplicated on every URL — and using the most specific subtype that fits your business: OnlineStore for a shop, a LocalBusiness subtype for a physical location. If you serve a city or run a storefront, the identity work pays off twice; our LocalBusiness schema setup guide covers the address, hours and geo fields that sit next to sameAs in the same block.
Not sure whether your Organization block is even reaching Google — or whether a plugin is quietly emitting a second one? A Clariola audit ($9.99, one-time) reads your raw HTML the way a crawler does and lists every schema type it finds on each page, so you can see your real entity footprint before you touch a line of JSON-LD.
Which profiles actually count in sameAs
Not every link belongs in sameAs. The property is for authoritative references to the same organization — pages a crawler would accept as “officially this company.” Padding it with random directory listings or a founder’s personal accounts weakens the signal instead of strengthening it. Here is how the common options sort out:
| Profile | In sameAs? | Why |
|---|---|---|
| LinkedIn company page | Yes | Owned, verifiable, name-controlled |
| Facebook / Instagram business profile | Yes | Official brand channels you control |
| YouTube / TikTok brand channel | Yes | Same — if the handle is the business, not a person |
| Wikidata entry or Wikipedia article | Yes (strong) | Authoritative knowledge-graph anchors |
| Crunchbase / industry registry | Yes | Third-party corroboration of the entity |
| Founder’s personal LinkedIn | No | That is a Person, not the Organization |
| Google Business Profile URL | No | Google links it through other signals already |
| Random web directories | No | Low trust; dilutes the signal |
The highest-value targets are the ones Google’s Knowledge Graph already trusts: Wikidata and Wikipedia. schema.org specifically names a Wikipedia page or Wikidata entry as example sameAs values. You can’t manufacture a Wikipedia article, but many small businesses can create a legitimate Wikidata item, and linking it gives the graph a stable anchor to hang your other profiles on. Keep personal profiles out of the Organization block entirely: to associate a founder, model them as a separate Person and connect the two, rather than dropping a personal account into the company’s sameAs.
How to build your Organization sameAs block, step by step
- List your real, owned profiles. Open each one and copy the canonical URL from the address bar — not a share link or a redirect.
- Normalize your name. Decide on one exact business name and confirm it is identical on every profile and in your
nameproperty. “Northside Dental,” “Northside Dental Co.” and “Northside Dental Clinic” read as three different entities. - Add a stable
@id. Give the Organization an@idlikehttps://www.yoursite.com/#organizationso the rest of your schema can reference the same entity. - Write the block on your homepage or About page (example below).
- Validate in Google’s Rich Results Test and the Schema Markup Validator, and fix any critical errors.
- Confirm every
sameAsURL resolves with a 200 status and lands on the live profile — not a login wall or a 404.
A minimal, correct Organization block looks like this:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"@id": "https://www.yoursite.com/#organization",
"name": "Northside Dental",
"url": "https://www.yoursite.com",
"logo": "https://www.yoursite.com/logo.png",
"sameAs": [
"https://www.linkedin.com/company/northside-dental",
"https://www.facebook.com/northsidedental",
"https://www.instagram.com/northsidedental",
"https://www.wikidata.org/wiki/Q00000000"
]
}
</script>
Swap LocalBusiness for OnlineStore or plain Organization depending on your business, keep the logo at least 112×112 pixels and legible on a white background per Google’s image guidance, and only list profiles that genuinely exist.
The entity-consistency mistakes that break sameAs
Most sameAs problems aren’t syntax errors — the JSON validates fine — they are consistency errors that quietly confuse entity resolution:
- Name drift. Your schema says one name, LinkedIn says another, your footer a third. Pick one and make them match.
- Logo mismatch. Different logos across profiles make it harder for Google to confirm it is the same brand. Use the same mark everywhere.
- Dead or redirected links. A
sameAsURL that 404s or bounces through a shortener is a weak signal at best. - Personal accounts in the company block. Covered above — this actively confuses resolution.
- Duplicate Organization entities. Two SEO plugins, or a theme plus a plugin, can emit two Organization blocks with different
sameAsarrays. Keep exactly one.
Entity consistency reaches beyond your own site, too. The name, address and profiles in your markup should match what you publish on your Google Business Profile and anywhere else your brand appears. When every source agrees, you make it trivial for an AI engine to cite your business in AI Overviews as one confident answer. Prefer to read this in Spanish? Here is the Spanish version.
Not sure how connected your own entity looks right now? Score it below, then read the section that follows.
When you need an audit
Some sameAs and Organization problems are easy to spot yourself; others only surface when you look at your raw HTML the way a non-JavaScript crawler does. Consider a professional audit when:
- You can’t tell whether your Organization schema is even rendering in the raw HTML — common when markup is injected by JavaScript.
- Your Rich Results Test shows two Organization entities and you don’t know which plugin emits which.
- Your brand name, logo or profiles are inconsistent across pages and you need a prioritized list of what to fix first.
- You want to know which schema types each page exposes — and whether any of them are types Google has since retired.
A Clariola audit ($9.99, one-time) crawls your site’s raw HTML like a non-JavaScript bot, lists the schema types found on each page, flags any that Google has deprecated (with the date it happened), and reviews your content structure, competitors and AI-search visibility — then emails you a prioritized PDF action plan. It won’t test your page speed or run a WCAG conformance check; it tells you exactly what a crawler and an AI engine see when they try to resolve your brand.
Frequently asked questions
Does sameAs guarantee a Google Knowledge Panel?
No. Schema helps Google understand and connect your entity, but a panel also needs notability and corroboration from sources like Wikipedia, Wikidata and news coverage. Treat sameAs as necessary groundwork, not a trigger.
How many sameAs URLs should I add?
There is no official limit — Google says you can provide multiple. Quality beats quantity: three or four authoritative, consistent profiles outperform a dozen low-trust directory links.
Should sameAs point to my Google Business Profile?
No. Google already associates your Business Profile with your site through other signals. Reserve sameAs for external profiles like social networks, Wikidata and industry registries.
Keep reading
- Structured Data7 min read
Shopify Structured Data: Fix Your Product Schema for 2026 Rich Results
Shopify emits a thin Product block via the structured_data filter — and apps often add a conflicting one. Here's how to audit, consolidate and enrich it for 2026 rich results.
- ai website tools7 min read
How to Optimize Your Website for AI Agents in 2026
A new wave of AI browsers and agents now reads, clicks and completes tasks on websites. Optimizing your website for AI agents means making your structure, labels, forms, bot rules and schema machine-operable. Here's a practical 2026 playbook for small businesses.
- technical seo7 min read
Google's July 2026 Product.category update: fix your merchant listing schema
Google added Product.category and tightened sale-duration rules on July 7, 2026. Here is the exact JSON-LD, Shopify and WooCommerce fixes, and a 6-point readiness checklist so expired priceValidUntil values stop killing your rich results.
