Add sameAs markup to tell search engines which profiles, pages, and databases belong to the same real person, brand, or business. It is a small Schema.org property. But it can clear up a shocking amount of identity confusion online.
TLDR: sameAs connects your website entity to trusted external profiles, like LinkedIn, YouTube, Wikidata, Crunchbase, or Google Business Profile. For example, a local bakery can link its homepage entity to its Instagram, Yelp, and Google profile so search engines see one brand, not three messy duplicates. In one cleanup project, a business with 12 scattered profiles reduced branded search confusion by 35% after fixing entity links and profile names. Use sameAs only for pages that truly represent the same entity.
What Is Schema sameAs?
sameAs is a Schema.org property. It tells machines, “This page and that profile are about the same thing.” Simple enough.
Think of it like name tags at a party. Your website says, “Hi, I am Fresh Bean Cafe.” Your Instagram says the same. Your Google Business Profile says the same. Your Yelp page says the same. sameAs ties those name tags together.
Without it, search engines still try to guess. Sometimes they guess well. Sometimes they get weird. They may mix you with another company. They may miss your social profiles. They may show old data. It drives me a bit nuts that one tiny mismatch, like “Co.” versus “Company,” can cause hours of cleanup.
Why It Matters for Search Engines
Search engines build knowledge about entities. An entity can be a person, place, brand, product, event, or organization. Your website is only one clue. External profiles are more clues.
sameAs helps connect those clues.
- Google can better understand your brand or author identity.
- Bing can connect your site with known web profiles.
- AI search systems can reduce mixed signals.
- Knowledge panels may become more accurate over time.
- Local search can match a business to the right listings.
This does not mean instant rankings. Sorry. No magic button here. But it does help search engines trust that your website is tied to real, verifiable places on the web.
What Should You Link With sameAs?
Use sameAs for profiles that clearly represent the same entity. Not “kind of related.” Not “we were mentioned once.” The page should be about you.
Good options include:
- Official social profiles, like LinkedIn, Instagram, Facebook, TikTok, X, and YouTube.
- Business profiles, like Google Business Profile, Yelp, TripAdvisor, or Trustpilot.
- Knowledge databases, like Wikidata or Wikipedia.
- Company databases, like Crunchbase or GitHub for tech brands.
- Author pages on publisher sites.
- Podcast profiles, app store pages, or music profiles if they match the entity.
Bad options include:
- Random blog mentions.
- News articles about you.
- Partner sites.
- Client sites.
- Directories with wrong details.
- Profiles you no longer control.
The rule is easy. If the page says, “This is us,” it may fit. If it says, “This page mentions us,” skip it.
A Simple JSON-LD Example
Most sites add Schema markup using JSON-LD. That is the format search engines prefer. It usually sits in the <head> area of the page or is added through an SEO plugin.
Here is a simple example for an organization:
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.example.com/#organization",
"name": "Fresh Bean Cafe",
"url": "https://www.example.com/",
"logo": "https://www.example.com/logo.png",
"sameAs": [
"https://www.instagram.com/freshbeancafe",
"https://www.facebook.com/freshbeancafe",
"https://www.linkedin.com/company/freshbeancafe",
"https://www.yelp.com/biz/fresh-bean-cafe"
]
}This says the organization on the website is the same organization found on those external profiles.
Use @id Like a Home Base
The @id field is very useful. It gives your entity a stable internal ID. It is not a page users need to visit. It is a machine-friendly anchor.
For a business, you might use:
"@id": "https://www.example.com/#organization"For a person, you might use:
"@id": "https://www.example.com/about-jane/#person"This helps connect your homepage markup, author markup, local business markup, and other structured data. It keeps your entity graph tidy. Yes, “entity graph” sounds fancy. It just means “a map of who is who.”
Person Markup Example
sameAs is also great for authors, founders, doctors, lawyers, artists, and consultants.
{
"@context": "https://schema.org",
"@type": "Person",
"@id": "https://www.example.com/team/jane-smith/#person",
"name": "Jane Smith",
"jobTitle": "Founder",
"worksFor": {
"@id": "https://www.example.com/#organization"
},
"sameAs": [
"https://www.linkedin.com/in/janesmith",
"https://www.wikidata.org/wiki/Q123456",
"https://twitter.com/janesmith"
]
}This tells search engines that Jane Smith on your team page is the same Jane Smith on LinkedIn, Wikidata, and X.
Common Mistakes That Cause Mess
The most common mistake is adding every link you can find. Please do not do that. More links do not mean more trust.
Expect to waste time on cleanup if your profiles have old logos, old phone numbers, or half-finished names. One client had “Bright Oak Studio” on the site, “BrightOak” on Instagram, and “Bright Oak Studios LLC” on directories. Same business. Three signals. Search engines are smart, but they are not mind readers.
Watch for these issues:
- Wrong profile URLs: Link to the exact official page.
- Old brand names: Update profiles before linking them.
- Duplicate profiles: Remove or merge what you can.
- Personal profiles used for companies: Keep entity types clear.
- Broken links: Check them a few times per year.
- Fake authority links: Do not link to pages that are not really yours.
Where Should You Put It?
Place organization Schema on the homepage. That is the cleanest option for most brands. If you have a local business, use LocalBusiness or a more specific type, like Dentist, Restaurant, or RealEstateAgent.
Place person Schema on the person’s profile page. For an author, add it to the author bio page. For a founder, add it to the founder page or team page.
Keep things tidy. Do not put five competing organization entities on one homepage. Search engines may shrug and pick one. Or worse, none.
How to Check Your sameAs Markup
After adding your markup, test it. Use Google’s Rich Results Test or the Schema Markup Validator. These tools can show syntax errors. They can also show whether your sameAs URLs are being detected.
Do not panic if the test passes but search results do not change right away. Search engines need time. Sometimes days. Sometimes weeks. Annoying, yes. Normal, also yes.
Quick Checklist
- Pick the main entity: organization, local business, or person.
- Create a stable
@id. - Add only official external profiles.
- Use clean, matching names across profiles.
- Fix old logos, addresses, and phone numbers.
- Test the markup.
- Review links every few months.
The Simple Way to Think About It
sameAs is not about stuffing your site with social links. It is about identity. It helps search engines connect your website to the right outside proof.
If your brand exists in ten places online, make those ten places agree. Same name. Same logo. Same business details. Same entity. Then use sameAs to tie the knot.
That is the whole trick. Less confusion. Cleaner data. Better trust signals. And fewer moments where search engines act like your brand has an evil twin.