Session 1.7: The sameAs Signal

Course → Module 1: Entity Relationships

Session 7 of 9

The sameAs property in structured data tells search engines that your entity on one platform is the same entity on another platform. Your website, your LinkedIn, your Twitter, your Wikidata entry: these are all fragments of one entity. Without explicit sameAs connections, the system may treat them as separate entities or fail to consolidate signals.

This is low-hanging fruit that most entities neglect. It takes 15 minutes to implement correctly and immediately improves entity signal consolidation.

Why sameAs Matters for Recognition

Search engines encounter your entity name across dozens of platforms. Each platform has its own URL structure, its own way of displaying your information, and potentially slightly different versions of your name or description. Without explicit signals that these are all the same entity, the system must infer identity through statistical matching.

Statistical matching works, but it is imperfect. The sameAs property removes the guessing. It is a direct, machine-readable declaration: "This entity on my website is the same entity as this LinkedIn profile, this Twitter account, and this Wikidata item."

How to Implement sameAs

The sameAs property is added to your Person or Organization schema on your website. It takes an array of URLs pointing to your profiles on other platforms.

A properly implemented sameAs array looks like this in JSON-LD:

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Jane Smith",
  "url": "https://janesmith.com",
  "sameAs": [
    "https://www.linkedin.com/in/janesmith",
    "https://twitter.com/janesmith",
    "https://www.wikidata.org/wiki/Q12345678",
    "https://www.youtube.com/@janesmith",
    "https://www.crunchbase.com/person/jane-smith",
    "https://github.com/janesmith"
  ]
}

Which URLs to Include

Not every URL belongs in sameAs. The property should point to canonical profile pages that represent your entity on major platforms.

Include	Why	Exclude	Why
LinkedIn profile	Major platform, frequently crawled	Random forum profile	Low authority, not a canonical identity source
Twitter/X profile	Major platform, used by Knowledge Graph	Guest post author page	Not your profile, it is a third-party page about you
Wikidata item	Directly feeds Knowledge Graph	Google search results URL	Not a profile, it is a search page
YouTube channel	Major platform, Google-owned	Review site page	Not a profile you control
Crunchbase	Business entity database, trusted by Google	Duplicate or old profiles	Conflicting signals from outdated information
GitHub profile	Professional identity (for tech entities)	Defunct social media platforms	Dead links create errors in schema validation

Every URL in your sameAs array must be a live, current profile that you control or have claimed. Dead links and profiles with outdated information create negative signals.

Bidirectional Linking

sameAs works best when the connection goes both ways. Your website points to your LinkedIn via sameAs. Your LinkedIn should link back to your website. This bidirectional connection gives the system high confidence that the entities are the same.

One-directional sameAs (website points to LinkedIn, but LinkedIn does not link back) is weaker but still useful. Bidirectional is stronger because it provides corroboration. The system sees: "Entity A claims to be on LinkedIn. LinkedIn entity links back to Entity A. Confirmed."

Common Mistakes

Including too many URLs. Stick to major platforms (5-10 URLs). Including 50 random profiles dilutes the signal and increases the chance of broken links.
Including URLs you do not control. A press mention or a Wikipedia page about you is not a sameAs target. sameAs is for pages where you are the subject and ideally where you control the content.
Not maintaining the list. If you delete a social media account or change your username, update your sameAs array. Broken URLs in schema are validation errors.
Forgetting Wikidata. If your entity has a Wikidata item, its URL should always be in sameAs. Wikidata items feed directly into Google's Knowledge Graph.

Verification

After implementing sameAs, validate it. Use Google's Rich Results Test or the Schema Markup Validator to check that your JSON-LD is syntactically correct and all URLs resolve. Then verify bidirectional linking: visit each profile URL and confirm it links back to your website.

Assignment

List every official profile URL your entity has across all platforms (aim for at least 8).
Implement or audit the sameAs property in your website's Person or Organization schema with all official profile URLs.
For each profile in your sameAs array, verify that the profile links back to your website. Fix any that do not.
Check if your entity has a Wikidata item. If yes, confirm the URL is in your sameAs and that the Wikidata item has your website URL in its "official website" property.
Validate your schema using the Rich Results Test.

The sameAs Signal