What is sameAs?

Example

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example.com/#organization",
  "name": "Example Roasters",
  "url": "https://example.com/",
  "logo": "https://example.com/img/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/example-roasters",
    "https://www.instagram.com/exampleroasters",
    "https://www.youtube.com/@exampleroasters",
    "https://www.wikidata.org/wiki/Q00000000"
  ]
}

The value is a single URL or an array of URLs. Each should open a page that is about this one organization and nothing else.

What it is for

Search engines build knowledge bases of entities: companies, people, places, products. A recurring problem is reconciliation, deciding whether the "Example Roasters" on your site is the one on a business registry, the one with the Instagram account, or another company with the same name. sameAs gives a direct answer from the source.

Google's Organization structured data documentation lists it as a recommended property for exactly this purpose. Used well, it supports accurate brand information in results and consistent attribution of authors. It does not create a knowledge panel, raise rankings, or pass link value. It removes ambiguity, and what search engines do with that clarity is up to them.

Which URLs belong

Good candidates:

• official social profiles you control;
• an entry in a public reference source, such as Wikidata or Wikipedia, where one exists;
• a company's profile in an official business registry or a well-known industry database;
• for a person: an author profile on a publisher's site, a professional or academic profile.

Leave out:

• your own homepage or other pages on the same site, which belong in url;
• pages that merely mention you, such as press articles or reviews;
• category or search pages on another site;
• profiles of a parent company, founder or reseller. Those are different entities, expressed with parentOrganization, founder and similar properties;
• abandoned or unverified accounts that could be confused with someone else's.

A short list of accurate URLs is better than a long list of loose ones. Check them once a year: renamed handles and deleted profiles leave dead links in the markup.

sameAs for people and authors

For articles, the author's Person markup can carry its own sameAs. That ties a byline to a real, findable individual, which fits how Google's guidance on E-E-A-T talks about making it clear who is responsible for content. Put the property on the Person, and keep the organization's profiles on the Organization. Mixing the two tells search engines the author and the company are one entity.

Where it comes from in WordPress

You rarely write it by hand. Hydrogen SEO builds the Organization's sameAs list from two places: the social profile URLs entered under Hydrogen SEO → Social, and any extra URLs added on the Schema screen; see schema markup overview. To confirm what your site outputs, view the page source of the homepage, find the application/ld+json block, and look for the array, or paste the page into our JSON-LD validator.

Two checks are worth a minute: the URLs should be the exact canonical profile addresses, with https and no tracking parameters, and the same profiles should link back to your site where the platform allows it. A two-way connection is more convincing than a one-way claim.