What is sameAs?
Also called Schema.org sameAs
Definition
sameAs is a Schema.org property that points to a reference page unambiguously identifying the same entity. It helps describe identity across pages or platforms and should not be used for partners, competitors, categories, or merely related organizations.
How does sameAs work?
A sameAs value is a URL representing the identity of the entity being described. In Organization markup, that might be an official company profile on another platform.
Schema.org defines the property around unambiguous identity rather than general subject similarity.
The property belongs inside structured data describing a particular entity. An organization and its software product may need separate descriptions.
Linking both to the same set of profiles without checking what each page represents can introduce ambiguity instead of resolving it.
Why does sameAs matter for B2B SaaS?
B2B SaaS companies often maintain profiles across social platforms, review sites, and business directories. Consistent identity references help connect those representations to the official business.
This is especially useful when the brand name resembles another company or the product has changed names.
Identity markup supports interpretation, not reputation transfer. Adding a famous partner to sameAs does not establish credibility and misstates the relationship.
Google documents sameAs for Organization data, but it does not promise a knowledge panel, higher ranking, or AI citation in return.
What is an example of sameAs?
A hypothetical software company publishes Organization JSON-LD on its About page. The markup includes its official website URL and uses sameAs for its verified company profile on LinkedIn. Both pages identify the same organization.
The company integrates with Microsoft Teams, but Microsoft is not another identity for that business. Its partner page therefore does not belong in the company’s sameAs list.
The integration should be explained as a relationship in appropriate content rather than encoded as identity equivalence.
How do you improve or measure sameAs?
- Choose reference pages that clearly identify the exact entity in the markup.
- Remove unrelated organizations, category listings, and pages with ambiguous ownership.
- Keep visible company details consistent with the structured data.
- Review identity references after rebrands, acquisitions, or profile URL changes.
Validate JSON-LD syntax and inspect whether every destination remains accessible and accurate. A valid schema document can still make a false statement, so automated validation is not enough.
Measure success through clearer identity and fewer mismatches rather than assuming each extra sameAs URL improves visibility.
Frequently asked questions about sameAs
Can sameAs point to a social profile?
Yes, when the profile clearly represents the same entity. A general social platform homepage or another organization’s account is not an appropriate identity reference.
Should sameAs include every page mentioning the company?
No. A passing mention is not necessarily an unambiguous identity page. Use selective references that genuinely identify the entity.
Does sameAs merge entities in Google?
It provides an identity statement, but Google controls how its systems interpret evidence. Publishers cannot force a merge or knowledge panel through this property.