What is the sameAs property in Schema.org, and how do you use it?

What is the sameAs property in Schema.org?

The sameAs property in Schema.org defines the URL of a reference web page that unambiguously indicates an item's identity. It connects a specific entity, such as an organization or a person, to recognized external web pages. Common examples of reference pages include an item's Wikipedia page, Wikidata entry, or official website. By pointing to these canonical sources, sameAs relates a thing to a page that indirectly identifies it.

Google Search works hard to understand the content of a web page. Structured data offers a standardized format for providing explicit information about a page and classifying its main content. For example, structured data on a recipe page might detail ingredients, cooking time, temperature, and calorie counts. Beyond topic-specific properties, Google can make general use of the sameAs property and other Schema.org structured data to recognize entities accurately.

When applied to a person or entity type in Schema.org, sameAs serves as a clear pointer to identity pages across the web. Whether pointing to an authoritative Wikipedia article or an official organizational domain, the property reduces ambiguity about who or what is being described. This explicit identity link helps systems ground page topics in established public reference pages.

How does sameAs differ from url, mainEntityOfPage, and identifier?

The sameAs property, the url property, and the mainEntityOfPage property in Schema.org are all similar, but each serves a distinct role in structured data. Schema.org documentation specifies that the url property should be reserved to refer to more official or authoritative web pages, such as the item's official website. In contrast, sameAs emphasizes well known external pages that identify the entity indirectly or directly across different domains.

The mainEntityOfPage property serves to clarify which of several entities described on a web page is the primary subject of that page. It indicates a page or CreativeWork for which the item is the main entity being described. Whereas sameAs emphasizes well known pages across the web, mainEntityOfPage clarifies which entity is the primary focus of a given page. For example, for a product, sameAs might refer to a page on the manufacturer's official site with specs for the product, while mainEntityOfPage might be used on pages within various retailers' sites giving details for that same product.

The identifier property serves a different technical purpose by representing code-based values. Schema.org defines identifier to represent any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, or UUIDs. While sameAs relies on reference web page URLs to indicate identity, identifier handles alphanumeric identification codes.

How do search engines use sameAs markup?

Search engines use sameAs markup to aggregate entity data from across the web and clarify relationships between entities. Schema.org notes that identity matching can rely on monthly aggregations from Google's web index. By reading sameAs attributes, search engine systems map connections between web pages and external references.

Google documents that adding organization structured data to your home page helps Google better understand your organization's administrative details and disambiguate your organization in search results. For organizations, sameAs provides the URL of a page on another website with additional information, such as a profile page on a social media or review site. You can provide multiple sameAs URLs to list all relevant profiles.

Similarly, Google uses profile page markup to understand creators who post in an online community. Adding this markup helps show better content from that community in search results, including the Discussions and Forums feature. For creator profile pages, sameAs provides the URL to other external profiles or home pages associated with that user.

How should you implement sameAs in structured data?

You implement the sameAs property by adding reference URLs into structured data code placed within HTML script tags on your page. Google recommends using JSON-LD for structured data if your site's setup allows it. JSON-LD is encoded inside an HTML script tag, making it the easiest solution for website owners to implement and maintain at scale with lower risk of user errors.

When defining an organization or profile in JSON-LD format, include sameAs as a string or an array of URL strings. For example, an organization block on example.com can include sameAs URLs pointing to its profile page on a review site or social media network. Providing clean reference URLs ensures search engines can resolve administrative details without parsing ambiguous text.

How do you diagnose and fix sameAs structured data issues?

To ensure your sameAs implementation works properly, follow a step-by-step diagnostic process to validate code syntax and verify that search engine crawlers can access your pages. Google guidelines emphasize testing code syntax and clearing access blocks before relying on structured data in search features.

1. 01Validate your structured data code using the Rich Results Test tool.
2. 02Fix any critical errors identified during validation.
3. 03Verify that your page is accessible to Google and not blocked by a robots.txt file, a noindex tag, or login requirements.

Common questions