SameAs schema is one of the simplest structured data additions you can make, yet it can be one of the most powerful for entity clarity, E-E-A-T, and trust. When implemented correctly, it helps search engines and AI systems connect your site’s Organisation or Person to the right real-world entity across authoritative profiles. If your goal is to publish content that machines can confidently reference, pair entity markup with strong credibility signals (see this guide on creating pages that AI can cite and users trust).
What SameAs actually signals (in plain English)
In Schema.org, sameAs is a property that indicates two URLs refer to the same thing (the same entity). In practice, you’re telling Google and other parsers: “This organisation/person on my website is the same organisation/person represented by these other authoritative URLs.”
That matters because entity resolution is hard: names are ambiguous, brands rebrand, and many people share the same name. SameAs is a way to reduce ambiguity by providing corroborating references.
For reference, you can review Schema.org’s documentation for the sameAs property to see how the property is defined and where it can be used.
Key takeaway: sameAs doesn’t “rank you” by itself. It helps systems connect your site to the correct entity, which supports trust and consistency across the knowledge graph ecosystem.
Why SameAs helps with entities, E-E-A-T, and trust signals
SameAs is most useful when it strengthens the consistency of who you are across the web. That consistency supports:
- Entity disambiguation: distinguishing your brand/person from others with similar names.
- Trust reinforcement: aligning your site with authoritative third-party profiles that confirm legitimacy.
- Knowledge graph cohesion: improving the likelihood that various systems (search, assistants, LLMs) connect your mentions, reviews, and citations to one entity.
- Reduced “identity fragmentation”: helping consolidate signals across multiple URLs (your site, Wikipedia/Wikidata, LinkedIn, Crunchbase, official registries, etc.).
This is especially relevant for brands investing in demand capture and brand credibility, where consistency across owned and earned channels is a compounding advantage (related: why branded SEO matters more than ever).
When SameAs is worth implementing (and when it isn’t)
SameAs helps most when you have an entity that is (or should be) consistently represented across reputable sources.
Use SameAs when
- You have a clearly defined Organisation (company, agency, non-profit) or Person (founder, spokesperson, author) with stable public profiles.
- Your business name is shared by other brands or could be interpreted in multiple ways.
- You operate across multiple markets or languages and want a single entity connection across regional profiles.
- You have a Knowledge Panel or are trying to reduce confusion between similar entities.
Be cautious or skip SameAs when
- You’re tempted to add references that are not truly the same entity (e.g., a “topic” page about your industry).
- You only have low-quality directory listings, scraped profiles, or user-generated pages that you don’t control and can’t verify.
- You’re unsure whether a profile is the canonical representation of the entity (better to omit than to mislead).
How to choose the right SameAs references
The best SameAs URLs are authoritative, stable, and unambiguous. Think of them as identity proofs, not link building targets.
Good SameAs sources (examples)
- Official social profiles you control (LinkedIn, YouTube, X/Twitter, Instagram, Facebook).
- Wikidata (if it exists and is accurate) and, where appropriate, Wikipedia.
- Official business registries or regulator listings (varies by country/industry).
- Major commercial databases where the entity has a clear profile (e.g., Crunchbase for companies, Google Scholar for researchers).
- App store developer pages (Apple App Store / Google Play) for software publishers.
Weak or risky SameAs sources
- Generic web directories with inconsistent data.
- Profile pages that can be claimed/edited by anyone without verification.
- Short-lived campaign URLs, tracking URLs, or redirect chains.
- Pages that mention you but are not “you” (news articles, guest posts, PR coverage).
A simple validation test before you add a SameAs URL
Ask: “If an auditor saw this URL, would they agree it is the canonical representation of the same entity?” If the answer is anything other than “yes,” don’t add it.
Where SameAs should live in your schema (Organisation vs Person)
SameAs is typically included inside your Organization or Person JSON-LD, usually on:
- Your homepage (for Organisation schema)
- About page (Organisation + key people)
- Author bio pages (Person schema for content authors)
In an E-E-A-T context, a clean pattern is:
- Organisation schema on the homepage (brand identity)
- Person schema on author pages (expert identity)
- Consistent publisher and author relationships (content accountability)
Implementation examples (JSON-LD) for Organisation and Person
Below are practical patterns you can adapt. Replace placeholders with your real URLs and identifiers. Keep lists tight: only include URLs you’re confident represent the same entity.
Example 1: Organisation schema with SameAs
This is a common pattern for a company site. Place it in the <head> or body via JSON-LD.
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Example Company",
"url": "https://example.com/",
"logo": "https://example.com/wp-content/uploads/logo.png",
"sameAs": [
"https://www.linkedin.com/company/example-company/",
"https://www.youtube.com/@examplecompany",
"https://www.wikidata.org/wiki/Q123456"
]
}Example 2: Person schema with SameAs (for a founder/author)
Use this on an author page or a leadership bio page. The goal is to connect the person on your site to reputable identity profiles.
{
"@context": "https://schema.org",
"@type": "Person",
"@id": "https://example.com/team/jane-doe/#person",
"name": "Jane Doe",
"jobTitle": "Founder",
"url": "https://example.com/team/jane-doe/",
"worksFor": {
"@id": "https://example.com/#organization"
},
"sameAs": [
"https://www.linkedin.com/in/janedoe/",
"https://www.instagram.com/jane.doe/"
]
}Example 3: Linking your content to verified entities
SameAs is one piece of the overall entity graph. Where possible, reinforce the entity relationships by connecting authors to the publisher and referencing the same @id values consistently across templates.
Common SameAs mistakes that weaken trust
- Using the wrong entity type: putting a person’s profiles in an Organisation
sameAslist (or vice versa). - Listing “mentions” instead of identities: news articles about you are not the same entity as you.
- Overstuffing the list: 20+ URLs of questionable quality creates noise and can introduce contradictions.
- Linking to redirects or tracked URLs: use clean, canonical URLs whenever possible.
- Inconsistent naming: different brand names, addresses, or logos across profiles reduce confidence.
How to validate and monitor your SameAs implementation
After adding SameAs, validate both technical correctness and entity consistency.
Technical validation
Use Google’s Rich Results Test to ensure your JSON-LD is parseable and there are no syntax errors. While SameAs itself isn’t a “rich result feature,” the tool is still useful for confirming structured data can be read.
Consistency validation
- Confirm the same brand/person details (name, logo, location, handle) appear on the linked profiles.
- Check that your key profiles link back to your website where appropriate (a two-way corroboration is ideal).
- Ensure your About, Contact, and author pages reflect the same identity information.
Practical checklist: SameAs done correctly
- Choose the right entity: Organisation on homepage; Person on author/bio pages.
- Use stable URLs: official profile links, not shorteners or redirects.
- Prioritise quality over quantity: a few authoritative references beat many weak ones.
- Keep entity data consistent: name, logo, and descriptors should match across sources.
- Validate markup: ensure JSON-LD is valid and deployed on the intended templates.
How SameAs fits into a broader on-page entity strategy
SameAs is a trust connector, but it’s most effective when your pages clearly communicate who you are, what you do, and why you’re credible. That includes clean site architecture, descriptive headings, strong author bios, and consistent internal linking. If you want help aligning structured data with content and on-site signals, explore our on-page SEO services in Dubai.
FAQs
Does SameAs schema improve rankings directly?
No. SameAs is best viewed as an entity clarity signal. It can indirectly support performance by reducing confusion, strengthening brand/entity understanding, and improving how systems interpret your site’s legitimacy.
How many SameAs links should I add?
There is no fixed number. Aim for a small set of high-confidence URLs (often 3–8). Only include profiles that clearly represent the same entity and are likely to remain stable.
Can I use SameAs to point to review pages or news coverage?
Usually, no. Those pages are about you, not you. SameAs should point to identity profiles where the page itself represents the entity (organisation or person).
Should I add SameAs for local business listings?
Sometimes. If you have a verified listing that unambiguously represents your business, it may be appropriate. The key is accuracy and stability. Avoid low-trust directories with inconsistent NAP data.
Where should I place SameAs on my website?
Add it in JSON-LD within your Organisation schema (typically on the homepage and/or About page) and in Person schema on author or team pages. Keep the @id consistent across templates so parsers can connect your entities reliably.