# sameAs in Schema.org: what it is and how to use it

> What the Schema.org sameAs property is, which links it takes and which it does not, where Google uses it (Organization, authors) and how to review yours.

URL: https://clione.ai/glossary/sameas/
Lang: en

Where you most often see `sameAs` is in the [JSON-LD](/glossary/json-ld/) block on a store's home page, inside the node that describes the company: a list with the Instagram address, the Facebook one and sometimes a few more. That is why a lot of people treat it as the place to link social networks. It is a bit more precise than that: **it is how you tell a search engine which [entity](/glossary/entity/) your store is**, and that it isn't some other one with the same name. If your brand shares a name with a town, a band or a company in another country, this property is part of the answer.

## How it works

[Schema.org](/glossary/schema-org/) defines `sameAs` as the URL of a reference web page that unambiguously indicates the item's identity, and gives three examples: its Wikipedia page, its Wikidata entry or its official website. Its value is a URL and it is defined on Thing, the root type of the vocabulary, so **any type can carry it**: an organization, a person, a movie or a book. The documentation's own example describes a movie and links it to its Wikidata entry.[^schema-sameas]

In a store's [structured data](/glossary/structured-data/), Google documents two uses.

**On the organization.** The [Organization](/glossary/organization-schema/) type helps Google understand your company's administrative details and distinguish it in search results, and it can influence which logo is shown in Search and in the knowledge panel. It has no required properties: you add the ones that apply to your company. Google recommends putting it on the home page or on a single page that describes the organization, such as the about page. And among the recommended properties is `sameAs`: **the URL of a page on another website with more information about your organization**, for example your profile on a social network or a review site. You can give several.[^google-organization]

**On an article's author.** If your store has a blog, Google recommends marking up the author's type and their `url`, or `sameAs` as an alternative, with valid URLs: it understands both properties when it has to tell one author from another with the same name.[^google-article]

What Google doesn't do is ask for `sameAs` on the product. Its [merchant listings](/glossary/merchant-listings/) documentation doesn't mention it. The properties it describes for identifying a product are others: global identifiers such as the [GTIN](/glossary/gtin/), the manufacturer's [MPN](/glossary/mpn/), the brand and your store's [SKU](/glossary/sku/).[^google-merchant-listing] That the vocabulary allows `sameAs` on a [Product](/glossary/product-schema/) doesn't mean Google uses it for anything on a [product page](/glossary/product-page/).

## In a store

**Fictional example.** A ceramics store, Albar Ceramics, with made-up domains. This is the organization node its home page would carry:

```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://albar-ceramics.example/#organization",
  "name": "Albar Ceramics",
  "url": "https://albar-ceramics.example/",
  "logo": "https://albar-ceramics.example/logo.png",
  "sameAs": [
    "https://social-network.example/albarceramics",
    "https://another-network.example/albar.ceramics",
    "https://review-site.example/stores/albar-ceramics"
  ]
}
```

Its own site goes in `url` and the profiles on other sites in `sameAs`. Before writing the list it pays to put each candidate through the same question: does this page say, without doubt, that it is about this store?

| Candidate                                            | Goes in `sameAs`?    | Why                                                                                   |
| ---------------------------------------------------- | -------------------- | ------------------------------------------------------------------------------------- |
| The store's official social network profile          | Yes                  | It is Google's example[^google-organization]                                          |
| The store's listing on a review site                 | Yes                  | It is Google's other example[^google-organization]                                    |
| Its Wikidata entry, if there is one                  | Yes                  | Schema.org lists it as a reference page[^schema-sameas]                               |
| The store's own website                              | No, it goes in `url` | `sameAs` points to a page on another site[^google-organization]                       |
| A newspaper story about the store                    | No                   | It talks about the store, but isn't a reference page for its identity[^schema-sameas] |
| The website of a manufacturer whose product it sells | No                   | It identifies another company                                                         |


Putting your own website's address in `sameAs`. Google defines the property as the URL of a page **on another website** with more information about your organization; your address goes in `url`.[^google-organization] The reverse happens too: using `sameAs` as a list of links you'd like to show off. Schema.org asks that each one unambiguously indicate the item's identity, not that it talk about it.[^schema-sameas]


## How to check it

1. **Open your home page's source code** and look for `sameAs` inside a `<script type="application/ld+json">`.
2. **Check which node it is in**: it has to be the organization's, on the home page or the about page.[^google-organization]
3. **Open every URL on the list.** It has to load, belong to your store and still be active; a closed profile no longer identifies anyone.
4. **If you publish articles with an author**, check that the author carries `url` or `sameAs` pointing to a page that identifies them.[^google-article]
5. **Run the page through a [schema validator](/glossary/schema-markup-validator/)** to rule out syntax errors in the block.

## Related concept: the @id identifier

The two serve to identify, but they look in opposite directions. The [`@id` identifier](/glossary/id-json-ld/) belongs to JSON-LD, not Schema.org: the specification defines it as the keyword that uniquely identifies the nodes described in the document, with an IRI or an anonymous [node identifier](/glossary/id-json-ld/).[^w3c-json-ld11] It lets the product node, within your own markup, point to the organization's without repeating it. `sameAs` points outward, to pages on other sites that say who that entity is.[^schema-sameas] **`@id` is the name you give it yourself; `sameAs` is the outside pages that confirm it.**

To keep going, the [structured data reading path](/learn/structured-data/) puts the other terms in order, and the [MPN](/glossary/mpn/) entry explains how a product is identified, which is a different thing.
