Profiles that name you and link back

Do the profiles the site claims as its own exist, name it, and link back to it?

Identity · 10 of 100 in Identity · yours to do · profiles

What we look for

Your structured data’s sameAs list names your profiles elsewhere — LinkedIn, GitHub, X, Wikidata, and so on. We fetch up to five of them (your own site’s address, if it’s in the list, isn’t a profile) and ask two things of each.

  • Does it load and name you, by any of the names you give yourself: your structured data’s name and alternateName, og:site_name, or the name in your title, with or without a leading “The”, and for a person with or without initials? That’s half the profile.
  • Does it link back: does your domain appear on it, as a whole (wearefaculty.com isn’t faculty.com)? In its text, in the data the page carries for its scripts (Facebook and Instagram keep a profile’s website there), or behind the link a site sends you through (l.facebook.com, l.instagram.com, t.co). That’s the other half.

The score is the average across the profiles we could verify. A profile is dead if it returns “not found” or its site no longer exists. Some sites turn away bots, with an error, an error page served as a profile, a challenge page, a login wall, or a page with no text; and a profile larger than we read (a megabyte) that we didn’t find your domain in may have it further down. We can’t verify those, so we name them in the report, say we couldn’t check them, and leave them out of the score. We never read LinkedIn, which prohibits automated access: a LinkedIn profile is “couldn’t check”, and left out. If we can’t verify any, or there’s no sameAs list, the criterion is skipped (the structured identity criterion already counts a missing one).

A profile that answers our bot with an error page (“Page not found”, “Sorry, this page isn’t available”) is one we can’t verify, told by the page’s title, never by a word in a working profile’s code.

Why it matters

sameAs is you telling AI “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.

Anyone can claim a profile. A link in only one direction — your site saying “that’s us” — is a claim. A link in both directions — the profile saying “this is our site” — is confirmation, and it’s what systems that merge what they know about an entity look for.

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. Add your website address to each profile — most have a “website” field, or put it in the bio — using the same address you use everywhere else (https, the same www or no www):
    https://example.com

Last changed .

The whole rubric