Skip to content

sameAs schema: link your Organization and Person to their profiles

How to use sameAs in Organization and Person markup: what schema.org and Google document, which profiles to list, and keeping name, logo and URL consistent.

By Crawlito · 6 min read

In short

  • schema.org defines sameAs as the URL of a reference web page that unambiguously indicates the item's identity.
  • Google's Organization documentation describes sameAs as a page on another website with more information about your organization, such as a social or review site profile.
  • Google recommends url or sameAs on article authors, using valid URLs, to help it understand who the author is.
  • List only profiles the entity controls or that are clearly about it, and use the same name, logo and home page URL across the markup and those profiles.
  • sameAs is a hint that helps systems connect records about one entity; no search engine documents it as a ranking or citation factor.
On this page

sameAs is a schema.org property that lists URLs of other pages that identify the same thing: your company's LinkedIn page, its Wikipedia article, a founder's profile on another site. You add it to Organization or Person markup so that search engines and other systems can connect the entity on your site with the same entity elsewhere. It does not make anything rank, but it removes ambiguity, which matters when your name is shared with other companies or people.

This guide covers what schema.org and Google document, which URLs belong in the list, complete examples, and how to keep the details consistent.

What sameAs means

schema.org defines sameAs as the URL of a reference web page that unambiguously indicates the item's identity. It is a property of Thing, so every type can use it, and its value is a URL or a list of URLs.

The key word is unambiguously. A sameAs URL should be a page about that exact entity, not a page that mentions it. For a company, that is its own profile on a platform. For a person, it is their own profile or a reference page about them.

Google uses the property in several structured data features:

  • Organization. Google's Organization documentation lists sameAs as a recommended property: the URL of a page on another website with additional information about your organization, for example a profile on a social media or review site.
  • Article authors. Google's Article documentation says it strongly recommends the type and url (or sameAs) properties on authors to help it understand who the author is, and that the URLs must be valid.
  • Profile pages. Google's ProfilePage documentation describes sameAs on the Person or Organization as the URL to other external profiles or home pages, if applicable.

None of these pages says sameAs affects ranking. Google's Organization page says the markup helps it understand your organization and tell it apart from others, and that some properties can influence visual elements such as the logo shown in results.

Which profiles to list

Include a URL when the page is clearly about the same entity and you would be happy for someone to treat it as an official reference.

Usually includeUsually leave out
Official social profiles: LinkedIn company page, X, Instagram, Facebook, YouTube, GitHubPages that only mention you, such as news articles or blog posts
A Wikipedia article about the organization or personA Wikipedia article about a topic or product category
A Wikidata item for the entitySearch result pages or hashtag pages
Business listings you manage, such as a marketplace or app store developer pageDirectories you have never claimed, with outdated details
Review site profiles for the businessProfiles of a different company with a similar name
For people: their own site, professional profiles, an author page on a publication they write forPersonal accounts the person has not chosen to connect publicly

A few practical rules:

  • Use the canonical profile URL, without tracking parameters, and the https form the platform itself uses.
  • One entity per list. A company's sameAs should not include the founder's personal profile; that belongs in the founder's Person markup.
  • Prune dead links. A profile you deleted or that redirects elsewhere no longer identifies you.
  • Fewer, correct links beat many weak ones. There is no documented benefit to length.

Organization example

Put this on the home page or an about page. Google says you do not need Organization markup on every page.

json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.example.com/#organization",
  "name": "Example Analytics",
  "alternateName": "ExampleA",
  "url": "https://www.example.com/",
  "logo": "https://www.example.com/images/logo-512.png",
  "sameAs": [
    "https://www.linkedin.com/company/example-analytics",
    "https://github.com/example-analytics",
    "https://www.youtube.com/@exampleanalytics",
    "https://en.wikipedia.org/wiki/Example_Analytics",
    "https://www.wikidata.org/wiki/Q00000000"
  ]
}

The @id gives the organization a stable identifier you can reference from other markup on the site, such as publisher on an article, instead of repeating the details. The Organization schema guide covers the other properties and which subtype to use.

Person example for authors

For an author page, describe the person once and link out to their profiles:

json
{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "mainEntity": {
    "@type": "Person",
    "@id": "https://www.example.com/authors/maria-lopez#person",
    "name": "Maria Lopez",
    "jobTitle": "Head of Research",
    "url": "https://www.example.com/authors/maria-lopez",
    "worksFor": { "@id": "https://www.example.com/#organization" },
    "sameAs": [
      "https://www.linkedin.com/in/maria-lopez-example",
      "https://github.com/mlopez-example",
      "https://scholar.example.org/profiles/maria-lopez"
    ]
  }
}

Then, in each article, point the author at that page:

json
"author": {
  "@type": "Person",
  "name": "Maria Lopez",
  "url": "https://www.example.com/authors/maria-lopez"
}

Google's Article documentation asks you to put only the person's name in author.name, to list each author in their own author entry, and to use Person for people and Organization for organizations. Our guides to author pages and Article schema go further on both.

Keep name, logo and URL consistent

Linking profiles helps only when the profiles agree with your site. Any system trying to match records about one entity has little more to go on than names, addresses, logos and home page links. Inconsistency makes that harder.

Check these against each profile in your sameAs list:

  1. Name. The same legal or trading name. If you use a short form, put it in alternateName rather than mixing forms in name.
  2. Website link. Each profile should link back to the same home page URL you use in url, including www or not, and https.
  3. Logo. The same logo file or at least the same design. Google asks for a logo at least 112 by 112 pixels at a crawlable, indexable URL.
  4. Description and location. Same country, city and category across profiles where they appear.
  5. Site name. The name in your Organization markup should match the site name you want shown in Google. The post on Google showing the wrong site name covers the separate WebSite markup for that.

A short audit routine: list every URL in sameAs, open each one, and note the name, the website link and the logo. Fix the profiles first, then the markup.

Common sameAs mistakes

MistakeWhy it is a problemFix
Listing your own home page or blog URLssameAs points to other pages that identify the entity; your own URL belongs in urlMove it to url
A share link or a profile URL with tracking parametersIt is not the profile's stable addressUse the clean profile URL
A single string with several URLs separated by commasIt is one invalid URL, not a listUse a JSON array of strings
The founder's profiles in the company's listIt mixes two entitiesPut them in the founder's Person markup
Profiles of a different company with a similar nameIt links you to the wrong entityRemove them and check each URL by hand

How to check your sameAs markup

  1. Confirm it is in the server HTML, not added only by a tag manager or script:

    bash
    curl -s https://www.example.com/ | grep -o '"sameAs"[^]]*]'
  2. Validate the JSON-LD with the Schema Markup Validator. It flags syntax errors and unknown properties. Our JSON-LD errors guide covers the usual ones.

  3. Check every URL returns 200 and is the profile you meant:

    bash
    for u in https://www.linkedin.com/company/example-analytics https://github.com/example-analytics; do
      curl -s -o /dev/null -w "%{http_code} $u\n" -L "$u"
    done

    Some platforms block automated requests, so a 403 or 999 from a social site does not always mean the profile is gone. Open those in a browser.

  4. Check for one Organization per site. Two Organization blocks with different names or sameAs lists, often from a theme plus an SEO plugin, contradict each other. Keep one and reference it by @id.

Frequently asked questions

What should I put in sameAs?

URLs of pages that unambiguously identify the same entity: official social profiles, a Wikipedia or Wikidata entry about it, and business listings you manage. Leave out pages that merely mention it.

Does sameAs help SEO?

Google describes it as a way to point to other pages with information about your organization or author, and says Organization markup helps it understand and disambiguate your organization. It does not document sameAs as a ranking factor.

Do AI assistants use sameAs?

No AI operator documents how it uses sameAs. It is plain schema.org data in your HTML, so any system that reads structured data can see it, and consistent profiles help anyone matching records about you.

Should I add sameAs to every page?

No. Google says Organization markup belongs on the home page or a page about the organization, not every page. Reference that entity by @id from other markup.

Can sameAs point to a Wikipedia page I do not control?

Yes, if the article is about your organization or the person. The property is about identity, not ownership.

Check what your markup says about you

The free check shows what a crawler receives from one page without JavaScript, including its structured data, with no account needed. It is a quick way to confirm your Organization markup and its sameAs list are where crawlers can read them.

Filed under Structure and schema. Topics: structured-data, json-ld, google, metadata