sameAs Schema: What It Is and How to Add It Correctly
Published by The Branded Agency · · 12 min read

sameAs is a Schema.org property that lists URLs of other pages on the web that describe the same entity as your markup. On a business site, you add it to your Organization structured data and point it at your official profiles, such as LinkedIn, Google Business Profile or a Wikidata item. It helps search engines and AI systems reconcile who you are across sources. It is an identity signal, not a ranking lever.
This guide covers the definition, the pages to include and exclude, a working JSON-LD example, the relationship between sameAs and your entity home page, and a method for checking the markup on any site.
TL;DR
- sameAs holds URLs of pages that unambiguously indicate the identity of the item you describe. The URL must be about the same entity, not a related one.
- Put it in Organization (or Person) JSON-LD on your entity home page, usually the About page or home page, as an array of canonical URLs.
- Keep the list short, verified and stable: official profiles, listings you control, and knowledge base entries such as Wikidata where they exist.
- Do not add competitors, press articles, directories you do not control, or internal pages.
- Google does not promise a display or ranking effect from structured data, so treat sameAs as entity clarity work and audit it regularly.
Table of Contents
- What sameAs schema means
- sameAs links versus your entity home page
- Which URLs to include in sameAs
- How to add sameAs to Organization schema with JSON-LD
- What sameAs does and does not do
- How to find and check sameAs on a website
- Common mistakes
- Our perspective
- Check your entity signals with a Brand Health Audit
- FAQ
- Sources
What sameAs schema means
Schema.org defines sameAs as the URL of a reference web page that unambiguously indicates the item's identity, with the examples of a Wikipedia page, a Wikidata entry or the official website. The property is defined on Thing, so it is available on every type that inherits from it, including Organization, Person, Brand, Product and Place.
Google's documentation describes it for organizations in practical terms: a URL of a page on another website with additional information about your organization, for example your profile on a social media or review site. You can provide more than one.
The W3C WebSchemas wiki explains why the property exists. It was added to indicate that a single real-world entity is described across multiple pages. The url property covers the stronger case, a page that is in some sense the entity's own page, while sameAs can be used wherever a useful identifier for the entity exists.
In plain terms, sameAs says: the thing described here is the same thing described there. Every decision about which URLs to include follows from that sentence.
sameAs links versus your entity home page
Searchers often ask about the entity home page next to sameAs, because the two work as a pair.
The entity home is the single page you treat as the definitive source of facts about your brand, organization or person. Jason Barnard, writing in Search Engine Land in March 2026, describes it as the page that anchors how algorithms, bots and people understand your brand, and notes it is usually the About page.
The division of labor looks like this:
| Element | What it does | Where it lives |
|---|---|---|
| Entity home | Makes the claim: this is who we are, what we do, who runs us | One page on your own site |
| sameAs markup | Lists the other pages that describe the same entity | Structured data on the entity home |
| Corroborating profiles | Confirm the same facts independently | LinkedIn, listings, knowledge bases |
The working pattern is two-directional. The entity home links out to the profiles through sameAs, and the profiles link back to the entity home through their website field. Each source then confirms the other. When the name, description and details on all of them match, a system reconciling identity has little to guess at. When they conflict, sameAs cannot repair it, which is why consistency comes first. Our brand consistency audit checks name, claims and details across channels for exactly this reason.
Which URLs to include in sameAs
The test is equivalence. Ask of each URL: does this page describe exactly the same entity as the node I am marking up, and can an outside system verify it? If the answer is anything but yes, leave it out.
Strong candidates
- Wikidata item. If your organization has one, its URL is among the clearest identifiers because knowledge graphs read it directly. Google's own Schema.org-based guidance on sameAs names Wikidata and Wikipedia as typical reference pages.
- Wikipedia article, where one exists and the entity meets notability standards.
- Official social profiles. LinkedIn company page, X, Facebook, Instagram, YouTube, whichever you actually operate and keep current.
- Business listings you control. Google Business Profile, Bing Places, Apple Maps listing for the correct location.
- App store or marketplace profiles that belong to your company or product.
- Industry directory listings you have claimed and verified.
Leave these out
- Competitors. A competitor's URL tells a parser that you and they are one entity.
- Mention pages. A press article, podcast page or partner blog that talks about you is a citation, not an identity anchor.
- Internal pages. Your own pricing or contact page is not an external reference for the entity.
- Related but different entities. A parent company, a founder's personal site or a sister brand needs its own node, not a place in this list.
- Unverified or stale profiles. If an old profile shows the wrong address or a former name, fix it before linking to it. A sameAs link works as an endorsement.
- Redirects and variants. Use the final canonical URL, not a shortened link, a mobile URL or a tracking-parameter version.
Short and high-confidence beats long. Ten verified URLs do more for clarity than forty that include weak ones, because each questionable link adds ambiguity instead of removing it.
How to add sameAs to Organization schema with JSON-LD
Google's own example places sameAs as an array of URLs inside Organization markup, and the documentation recommends putting the structured data on the home page or a single page that describes the organization. Here is a working pattern with placeholder values:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.example.com/#organization",
"name": "Example Co",
"url": "https://www.example.com/",
"logo": "https://www.example.com/logo.png",
"sameAs": [
"https://www.wikidata.org/wiki/Q00000000",
"https://www.linkedin.com/company/example-co",
"https://www.youtube.com/@exampleco",
"https://www.facebook.com/exampleco"
]
}
</script>
A few implementation notes:
- Give the node an
@id. A stable identifier lets you reference the same organization from other markup on your site, such as Article publisher or Product brand, so the sameAs list is defined once and reused. - Use full absolute URLs including the protocol.
- Use an array even for one URL if you expect to add more later. Google confirms multiple values are allowed.
- Place it on the entity home, and keep the visible content on that page consistent with the markup. Markup should describe what a visitor can see.
- Plugins work too. Most SEO plugins have a social profiles field that outputs sameAs. Check the rendered output rather than assuming the field maps correctly.
For a fuller walkthrough of the surrounding properties, see our guide to marking up your brand with Organization schema, and this Organization schema implementation guide for the wider context on eligibility and rich result expectations. If you run multiple markup types, our overview of schema markup for B2B brands shows how they fit together.
Person and local variants
The same property works on a Person node for a founder or author, pointing at their LinkedIn profile or a Wikidata item. For a business with locations, each location can carry its own node with its own Google Business Profile URL, while the parent organization lists the corporate profiles. Keep each node's list limited to pages about that node.
What sameAs does and does not do
Be precise about expectations. Google states that it may make general use of sameAs and other Schema.org markup, and that some elements may be used to enable future Search features if deemed useful. That is a statement about possible use, not a guarantee.
Google's general guidelines add two relevant points. A structured data issue can lead to a manual action, which means the page loses eligibility for rich results but its web search ranking is unaffected. And Google does not guarantee that correctly marked-up data will appear in results.
Practically, that means:
- sameAs is not a backlink and passes no ranking boost. Nothing in Google's documentation says otherwise.
- It does not by itself create a knowledge panel or an AI citation.
- Its value is disambiguation: it gives search engines and AI systems an explicit, machine-readable map of where your entity lives, so they can connect scattered mentions to one brand rather than treat them as separate or similarly named businesses.
That last point matters more as AI answers draw on multiple sources. Systems that cross-check claims look for agreement across independent pages, a theme we cover in third-party corroboration in GEO and in entity SEO for marketing teams.
How to find and check sameAs on a website
You can audit your own markup, or a competitor's reference pattern, in a few minutes without special tools.
- View the page source. Open the entity home in your browser, view source, and search for
sameAs. If nothing appears, the markup may be injected by JavaScript, so also inspect the rendered DOM in your browser's developer tools. - Read the structured data. Paste the URL or the code into a structured data testing tool such as Google's Rich Results Test or the Schema Markup Validator. Look for errors and for the Organization node with its sameAs array.
- Confirm each URL resolves. Every link should return a normal page, not an error or a redirect chain. A deleted or moved profile silently removes the signal.
- Check equivalence. Open each URL and ask whether it describes the same entity, with the same name, description and website.
- Check the return link. Does each profile point back to your entity home? A mismatch in website URL (http versus https, www versus bare domain) weakens the pairing.
- Look for duplicates. Plugins, themes and manual snippets often output two Organization nodes with different sameAs lists. Merge them into one.
Repeat this review quarterly and after any rebrand, handle change, address change or profile migration. Stale links are the most common way a clean setup decays.
Common mistakes
- Treating sameAs as a place to list every URL that mentions you. Mentions belong in your PR archive, not in identity markup.
- Linking profiles with conflicting facts. A listing with an old name and phone number contradicts the entity home. Correct the source first.
- Mixing entities. Putting the founder's personal profile in the Organization's list blurs two distinct entities.
- Setting and forgetting. Social handles change and platforms retire pages.
- Marking up content that is not visible or true. Structured data should reflect the page content and the real-world facts.
Our perspective
We approach sameAs as one line item inside a larger question: can a machine tell, with confidence, which brand it is looking at, and do the sources agree with each other?
In the audits we run, the markup itself is rarely the main problem. The more common finding is a mismatch between what the entity home says and what the profiles say: a different descriptor on LinkedIn, an outdated address on a listing, a founder profile that describes another company. Adding sameAs on top of those conflicts only points machines at the inconsistency.
That is why we score entity clarity from observable public data against a fixed checklist, and separate the score from data coverage and confidence. The sameAs array becomes one checkable item: present or absent, complete or padded, every URL live and equivalent. Fixing it takes an afternoon. Fixing the underlying inconsistency across channels is where the visibility gains come from, in classic search and in AI answers alike.
Our advice is to inventory first, correct the sources second, and mark up third.
Quincy
Check your entity signals with a Brand Health Audit
If you want to see how your sameAs setup, entity home and profiles read from the outside, our Brand Health Audit starts with a free scan of your public presence. No sales call or credit card is required for the initial scan.
The full twelve-category audit is $99 one-off and covers messaging, SEO, AEO, GEO, reputation, website experience and more, with recommendations tied to observable data. Subscription plans start at $79 per month on the pricing page. If your priority is AI answer visibility, the GEO audit and AEO audit focus on exactly that.
FAQ
What is sameAs in schema?
sameAs is a Schema.org property that gives the URL of a reference page that unambiguously indicates an item's identity, such as a Wikipedia page, a Wikidata entry or an official profile. It is defined on Thing, so Organization, Person, Brand, Product and Place can all use it. It tells machines that the entity described in your markup is the same one described at those URLs.
Does sameAs schema help SEO?
It helps search engines understand which entity your site represents, but Google's documentation does not describe it as a ranking factor. Structured data issues affect rich result eligibility, not web search ranking, and display is never guaranteed. Treat sameAs as entity clarity work that supports search and AI systems, and expect no direct ranking boost.
How many sameAs links should I add?
Add as many as there are verified, official pages for the same entity, and no more. Google allows multiple URLs, but a short list of high-confidence profiles is stronger than a long one with weak entries. Remove any link that is broken, outdated or not strictly about your organization.
What is the difference between sameAs and an entity home page?
The entity home is the page on your site that makes the definitive claim about who you are, usually the About page. sameAs is the property in that page's structured data that lists the other pages describing the same entity. The entity home links out through sameAs, and the profiles link back to it.
Sources
- sameAs - Schema.org Property
- Thing - Schema.org Type
- Organization Schema Markup | Google Search Central
- WebSchemas/sameAs - W3C Wiki
- The entity home: The page that shapes how search, AI, and users see your brand | Search Engine Land
- Intro to How Structured Data Markup Works | Google Search Central
- General Structured Data Guidelines | Google Search Central
Recommended
Where this shows up in your audit
These scored categories cover what this article talks about.
Industry brand audits
Accounting & bookkeeping firms brand audit · Architecture & design studios brand audit · Automotive brand audit
Want this handled for you?
Aligning how your brand shows up across every channel and listing.
Growth Strategy at The Branded AgencyGoing deeper on the strategy behind it: The framework the audit's brand strategy checks are drawn from. The Golden Spiral™ methodology.
Measured against real data
Every figure we publish comes from completed audits, reported as anonymised averages.
Related articles
- Schema Markup for B2B Brands: What Actually Matters
Discover the essential B2B schema markup types needed to define your corporate entity, services, and leadership for search engines and AI answer engines.
- Unsubstantiated Claims in Your Audit: Meaning and Fixes
Learn what an unsubstantiated claims audit finding means, why proof deficits hurt B2B conversions and AI citations, and how to verify landing page copy.
- Review Schema Markup: How to Add It and Earn Stars
Review Schema Markup: How to Add It and Earn Stars! Geometric cards represent review markup and ratings Review schema markup is structured data, usually JSON-LD, that tells search engines a page conta
Stay sharp
Get the next brand breakdown in your inbox
Practical brand strategy, messaging and AI-search insights. No fluff, no daily sends — just the work that moves brands.
Written by
Quincy Samycia
Founder & Brand Strategist, The Branded Agency
Quincy leads brand strategy at The Branded Agency, where he has spent over a decade helping founders and B2B teams sharpen their positioning, messaging and creative systems so growth stops depending on guesswork.
More from Quincy Samycia →See where your brand actually stands
Run the Brand Health Audit and get a scored diagnostic of your messaging, positioning and visibility.
