Hide and Seek

Profiles that resolve

Do the profiles the site claims as its own still exist, and do they name it?

Identity · 10 of 145 in Identity · yours to do · sameas-resolve

What we check

Your structured data’s sameAs list names your profiles elsewhere — LinkedIn, GitHub, Wikidata, and so on. We fetch up to five of them and check that each loads and mentions your name. The score is the fraction that do.

A profile is dead if it returns “not found” or its site no longer exists. Some sites turn away bots, with an error, a challenge page, or a page with no text; we can’t verify those, so we name them in the report and leave them out of the score. If we can’t verify any, or there’s no sameAs list, the check is skipped (the structured identity check already counts a missing one).

Why it matters

sameAs is you telling machines “these profiles are also me.” An AI assistant uses that claim to join what it knows from each place into one picture of you. A link to a deleted account, or to a page that doesn’t mention you, breaks that: at best it’s ignored, at worst it suggests the claim isn’t true. A one-way claim to a dead page is worse than none.

How to pass

  1. Open each profile in your sameAs list and make sure it still exists and shows your name.
  2. Remove the dead ones, and fix any that point to the wrong account:
    {
      "@context": "https://schema.org",
      "@type": "Organization",
      "name": "Example",
      "sameAs": [
        "https://www.linkedin.com/company/example/",
        "https://github.com/example"
      ]
    }
  3. While you’re there, add your website to each profile. The reciprocity check sees that they link back.

Last changed .

All the checks