The problem sameAs solves
When a machine sees your name, it asks: “Which one?” sameAs is one of the simplest ways to answer that question. It links your entity to other pages that unambiguously represent the same entity—your official profiles, and sometimes knowledge base entries.
Schema.org defines sameAs as a URL of a reference page that unambiguously indicates the item’s identity (for example, a Wikipedia page, Wikidata entry, or official website).
What an “entity ID” is (in practice)?
An entity ID is a stable identifier assigned by a system to a “thing.” Humans remember names. Machines prefer IDs.
- Your own canonical ID: a stable @id in your structured data (often a URL fragment like #organization).
- Platform IDs: identifiers within LinkedIn, Google Business Profile, app stores, review sites, and data providers.
- Knowledge base IDs: Wikidata QIDs (Q12345), and—when legitimate—Wikipedia pages.
Implementation principle: pick one canonical organization node
On your website, create one canonical organization identity and reference it everywhere in markup. Example: https://example.com/#organization. This becomes your “entity node” for structured data.
Minimum viable Organization JSON-LD (example)
{
“@context”: “https://schema.org”,
“@type”: “Organization”,
“@id”: “https://example.com/#organization”,
“name”: “Example Brand”,
“url”: “https://example.com/”,
“sameAs”: [“https://www.linkedin.com/company/examplebrand/”, “https://www.wikidata.org/wiki/Q123456”]
}
Google supports Organization structured data and documents properties like url and sameAs as ways to help them understand your organization. They also publish general structured data guidelines, including quality considerations (for example, structured data should not be misleading and should match page content).
See Also: Knowledge Graph Optimization and Entity Authority
The sameAs selection rules (use these or don’t use sameAs)
Rule 1: Only link to pages that are truly the same entity
- Official social profiles you control.
- Official marketplace/app store profiles you control.
- A Wikidata item that is clearly about your organization (with correct label/description).
- A Wikipedia page that is clearly about your organization (only if it exists legitimately).
Rule 2: Avoid “mention pages”
A blog post that mentions you is not an identity anchor. If the page does not clearly represent your entity, it does not belong in sameAs.
Rule 3: Keep the list short and high-confidence
More links aren’t better. Wrong links create new ambiguity. Start with the handful of pages that are unquestionably you.
Rule 4: If the external page is wrong, fix it before linking to it
sameAs links are endorsements. If a directory page has the wrong HQ or category, don’t enshrine it in your structured data. Correct it first.
See Also: Brand Facts Sheet: Canonical Data for Entity Consistency
Checklist: build your Entity ID Map
Track identity anchors the way you track brand assets. Here’s a recommended inventory table:
| Anchor | URL / ID | Status | Notes |
| Your canonical @id | https://example.com/#organization | Owned | Stable identifier used in schema markup |
| Website (canonical) | https://example.com/ | Owned | Primary URL (ensure redirects resolve to one canonical) |
| LinkedIn company page | https://www.linkedin.com/company/examplebrand/ | Claimed | Keep name/description consistent with facts sheet |
| Google Business Profile (if local) | GBP URL/ID | Claimed | Address/phone consistency is critical |
| Wikidata QID (if applicable) | https://www.wikidata.org/wiki/Q123456 | Verified | Ensure label/description are accurate and sourced |
| Wikipedia (if applicable) | https://en.wikipedia.org/wiki/Example_Brand | Verified | Only if article exists and is not promotional |
| Top directory 1 | Directory URL | Claimed | Correct category and HQ |
| Top directory 2 | Directory URL | Claimed | Remove duplicates |
Common mistakes (and what to do instead)
Mistake: Linking to every social network under the sun
Do instead: link only active, official, consistently branded profiles.
Mistake: Linking to profiles you don’t control
Do instead: claim them first or omit them until you can fix inaccuracies.
Mistake: Linking to Wikipedia because you want one
Do instead: earn it. Wikipedia requires notability and conflict-of-interest care. If you can’t meet the bar, focus on other anchors.
Mistake: Marking up facts that aren’t on the page
Do instead: keep structured data aligned with the visible content and your canonical facts sheet.
Operational tip: sameAs is a PR/Comms asset
Treat sameAs links as part of your reputation surface. When AI cites or “learns” from external pages, PR/Comms owns the narrative risk. Web/SEO implements, but PR/Comms should approve which anchors represent the brand.
References
Schema.org. “sameAs property.” . Accessed January 11, 2026.
Google Search Central. “Organization structured data.” Accessed January 11, 2026.
Google Search Central. “General structured data guidelines.” Accessed January 11, 2026.
Google Search Central. “Introduction to structured data markup in Google Search.” Accessed January 11, 2026.
About The Author
