The short version
sameAsmeans “this URL describes the same entity as this node” — not “here is a link I like”.- It only becomes corroboration when the profile links back. One-directional
sameAsis an unconfirmed claim. - Put the same list on the Person and on the Organization when the business is the person.
- Pair it with visible
rel="me"links in your footer — markup declares, links get followed. - Audit it. A 404 or an abandoned profile in the list is a failed verification, not a neutral entry.
What sameAs actually asserts
The schema.org definition is unglamorous and precise: “URL of a reference Web page that unambiguously indicates the item’s identity.”
Read that carefully. It is not “a related link” or “our social media”. It is a claim that the thing described at that URL and the thing described by this node are the same thing. Every URL you add is a specific, checkable assertion of identity.
That framing changes what belongs in the list. Your Instagram profile qualifies, because it is a page about you. Your latest Instagram post does not. Your Crunchbase company page qualifies. A news article that mentions you does not — that is a mentions or a citation, not an identity page.
The test: does this URL exist primarily to describe the entity? If yes, it is a sameAs. If it merely refers to the entity, it is not.
Why it has to go both ways
Here is the part that most guides skip, and it is the part that determines whether any of this works.
sameAs on your own site is a claim you make about yourself. Anyone can write anything in their own JSON-LD. On its own it carries roughly the weight of a business card: useful for disambiguation, worthless as proof.
It becomes evidence when the loop closes:
- Your site’s
sameAspoints at your LinkedIn profile. - Your LinkedIn profile links back to your site.
- Now two independently-controlled pages agree. That is corroboration.
This is the same reasoning behind domain verification anywhere else on the web: a claim you can make unilaterally proves nothing; a claim requiring access to both ends proves something. If you do one piece of work from this article, make it checking that every profile in your sameAs links back to your site.
Bidirectional beats long
- Four profiles that link back > twelve profiles that do not.
- Adding a platform you never use adds a weak, unconfirmed edge.
- Removing an abandoned profile is usually an upgrade, not a loss.
Which profiles are worth listing
Rank candidates by two things: how much Google trusts the platform, and how completely the profile describes you.
| Tier | Examples | Why |
|---|---|---|
| Strong | LinkedIn, a company page on an established platform, GitHub for developers, a university or employer staff page | High trust, structured profile fields, and the platform verifies something about you. |
| Useful | YouTube channel, Instagram, X, Facebook page, Pinterest, Threads | Real identity pages with a bio and a link field. Weight depends on whether the account is actually active. |
| Situational | Substack, Medium, a podcast host page, Behance, Dribbble, Speaker Deck | Worth listing if you genuinely publish there and the profile is filled in. |
| Skip | Empty accounts, link-in-bio pages, generic directory listings, anything you cannot log into | An unmaintained profile is a contradiction waiting to happen. |
A note on link-in-bio services: they are convenient for humans and unhelpful here. A page whose only content is other links does not “unambiguously indicate the item’s identity”. Link to it from your profiles if you like; do not put it in sameAs.
Free tool · See what a parser reads
Check that your sameAs list is present and parseable
The page checker reports the structured data blocks found in your rendered HTML, so you can confirm the sameAs array is actually there — and actually valid — rather than assuming it shipped.
sameAs and rel="me" do different jobs
These get conflated constantly, so:
sameAslives in your structured data. It is a machine-readable statement of identity that a parser reads.rel="me"lives on an actual anchor tag in your HTML. It marks a link as pointing at another profile of the same person, and it is a real link a crawler follows.
Use both. The markup states the claim formally; the link gives crawlers a path to walk. A footer block of profile links with rel="me", matching your sameAs list exactly, is the belt-and-braces version and costs nothing:
<a href="https://www.linkedin.com/in/yourname"
rel="me noopener noreferrer" target="_blank">LinkedIn</a>Keep the two lists in sync. If your footer has seven profiles and your sameAs has five, you have two slightly different claims on the same page, and the discrepancy is the sort of thing that stops a reviewer trusting either.
Person, Organization, or both
If you are a solo operator or the business is clearly built around you, put the same list on both nodes. Your Instagram is simultaneously your personal profile and the brand’s channel; asserting that for both entities is accurate, and it means the profiles corroborate the person—brand relationship as well as each entity individually.
If the organisation is genuinely bigger than you — multiple staff, its own channels, a separate voice — split them. The company’s sameAs gets the company channels; your Person node gets your personal profiles. Mixing them in that case creates the false impression that you and the company are one entity, which will eventually contradict something else.
Five ways the list goes wrong
1. Dead URLs
A profile you deleted, a platform that shut down, a username you changed. Each one is a verification attempt that fails. This is the most common problem and the easiest to fix.
2. Linking to posts instead of profiles
A specific tweet, video or article is not an identity page. Link to the channel, not the content.
3. Inconsistent identity across the listed profiles
If your LinkedIn says one job title, your X bio says another and your site says a third, you have listed three profiles that disagree. The list works against you. Make the profiles consistent before asserting they describe the same entity.
4. Padding with directories
Listing twenty low-quality directory profiles does not multiply your credibility; it dilutes a list that should read as a short set of real, maintained accounts. Quality is genuinely the metric here.
5. Claiming profiles you do not own
Someone else’s page, a namesake’s account, a company you left. Beyond being wrong, it actively introduces contradictory facts into your entity.
Auditing the list
Quarterly, or whenever you add or abandon a platform:
- Resolve every URL. Open each one. Confirm it loads, is yours, and is not a redirect to a login wall.
- Check the return link. Does the profile link to your site? If the platform only allows one link, point it at your profile or about page.
- Check the display name. Same name, same spelling, on every profile where a display name is separate from the handle.
- Check the bio. Each should state the same relationship — you, your role, your brand — in slightly different words. Identical boilerplate across seven platforms reads as automation.
- Check the photo. One face everywhere. Image similarity is a real resolution signal and the cheapest one available.
- Sync the footer. The
rel="me"links and thesameAsarray should contain the same URLs.
That is the whole job. It is unglamorous, takes an afternoon, and does more for how Google understands your identity than most of what gets sold as SEO.
FAQ
How many profiles should I list in sameAs?
As many as you genuinely own, maintain, and that link back — usually between three and eight. There is no benefit to padding the list, and an abandoned or empty profile is a liability rather than a neutral entry. If you would be embarrassed for a prospect to land on it, do not assert that it describes you.
Does sameAs help with rankings?
Not directly, and anyone claiming a ranking boost from it is overselling. What it does is help Google resolve your entity confidently, which affects whether you surface for your own name, how your snippet reads, and whether AI assistants describe you correctly. Those are worth having, but they are not a rankings lever for commercial keywords.
Should sameAs go on every page or only the about page?
Every page, as part of the shared Person and Organization nodes. Because those nodes carry a stable @id, repeating the array identically site-wide reinforces one node rather than creating many. What matters is that the list is byte-identical everywhere — differing lists on different pages is a soft contradiction.
Can I use sameAs for a Wikipedia or Wikidata entry?
Yes, and those are among the strongest entries possible — if they genuinely exist for you. What you must not do is create them for yourself to farm the signal. Wikipedia and Wikidata have notability standards, and a deleted entry is worse than no entry because it leaves a broken assertion behind.
What is the difference between sameAs and url?
url is the entity’s own canonical web address — your website. sameAs is a list of other pages, usually on platforms you do not control, that describe the same entity. Put your own domain in url and your profiles in sameAs; listing your own homepage in sameAs is harmless but pointless.
Thejas Acharya
Digital strategy consultant behind Digital with Thejas, based in Mangaluru, working with founders and marketing teams across India and the US. I build websites, landing pages, Meta Ads campaigns and AI automation that are judged on one thing: whether they generate leads. The free tools on this site are the checks I run on client work, opened up.