What Is sameAs in Schema Markup? How Google Connects Your Brand

A consulting firm searches for their own company name on Google. No Knowledge Panel appears. Their competitor — a smaller firm with half the backlinks — has one. The difference is not authority, age, or content volume. The competitor's JSON-LD includes a sameAs array linking their website to their LinkedIn company page, Crunchbase profile, and Wikipedia article. Google has enough cross-references to confirm the entity is real. The consulting firm's website mentions these profiles in a footer, but only as plain HTML links — invisible to Google's structured data parser.

sameAs in schema markup is a property defined by Schema.org that declares: "the entity described here is the same entity as the one at this other URL." When you add "sameAs": ["https://www.linkedin.com/company/your-company"] to your Organization JSON-LD, you are telling Google that your LinkedIn page and your website represent the same business. Google uses these declarations to cross-reference entity data across the web — confirming that your business name, address, and descriptions are consistent across platforms before granting a Knowledge Panel.

sameAs Is an Entity Disambiguation Tool

Most implementation guides describe sameAs as "where you put your social media links in schema." This framing is misleading. Social media links in your page footer are for humans. sameAs in your JSON-LD is for Google's Knowledge Graph — and the purpose is entity disambiguation, not social promotion.

Entity disambiguation means helping Google distinguish your business from every other entity with a similar name. "Sunrise Bakery" could be a bakery in Portland, a bakery in Austin, or a fictional bakery in a TV show. Google's Knowledge Graph stores all three as separate entities. sameAs is how you tell Google which one you are — by pointing to platform pages where your specific entity is described, verified, and consistent.

The accepted sameAs targets are not limited to social profiles. Any URL that authoritatively describes the same entity qualifies:

Platform	Correct URL format	Why it matters for disambiguation
Wikipedia	https://en.wikipedia.org/wiki/Your_Entity	Strongest disambiguation signal — Wikipedia is Google's primary reference for entity data
Wikidata	https://www.wikidata.org/wiki/Q123456	Machine-readable entity identifier used directly by Knowledge Graph
LinkedIn	https://www.linkedin.com/company/your-company	Company verification with employee count, industry, and location
Crunchbase	https://www.crunchbase.com/organization/your-company	Structured business data: funding, founders, headquarters
Facebook	https://www.facebook.com/your-page	Verified page with address, phone, and business category
X (Twitter)	https://x.com/your-handle	Real-time content from the entity, profile verification
YouTube	https://www.youtube.com/@your-channel	Video content attributed to the entity

A Wikipedia or Wikidata entry carries more weight for entity disambiguation than a social media profile. If your organization has a Wikipedia page, it should be the first sameAs URL in your array. Google's Knowledge Graph directly imports entity data from Wikidata, making it the most machine-readable source in the list.

How Google Uses sameAs for Knowledge Panels

A Knowledge Panel — the information box that appears on the right side of Google search results for recognized entities — requires Google to be confident that it correctly identifies who or what you are. Google's Organization structured data documentation explicitly lists sameAs as a recommended property for Organization schema. The signals Google evaluates include consistent entity data across platforms, verifiable claims (name, address, founding date), and cross-references between authoritative sources.

sameAs provides the cross-references. When Google crawls your website and finds sameAs links to LinkedIn, Crunchbase, and Wikipedia, it follows those links and checks whether the entity described there matches the entity described on your site. If the name, address, and description align across three or more independent platforms, Google's confidence in the entity's identity increases — which is a prerequisite for generating a Knowledge Panel.

This works in the other direction too. When Google encounters your LinkedIn company page in its crawl, it checks whether any website's sameAs property points to that LinkedIn URL. The bidirectional confirmation — your site says "I am this LinkedIn entity" and the LinkedIn page's content matches your site's claims — is stronger than either signal alone.

Implementation Rules Most Guides Skip

sameAs URLs must match the exact canonical format of the target platform. A mismatch that looks trivial to a human — https://linkedin.com/company/sunrise versus https://www.linkedin.com/company/sunrise — is a mismatch to Google's entity resolution system. Two different URLs may resolve to the same page via redirect, but Google matches the sameAs value against its own URL database before following redirects.

Rules for correct implementation:

• Use the canonical URL — visit the platform page, copy the URL from the browser address bar after all redirects resolve. That is your sameAs value
• No trailing slashes unless the platform uses them — LinkedIn URLs do not end with a slash; adding one creates a mismatch
• Match the protocol — all major platforms use HTTPS; never use http:// sameAs values
• Do not include UTM parameters or tracking fragments — https://facebook.com/page?ref=website is not the same URL as https://facebook.com/page
• Only link to pages that represent the entity — a blog post about your company is not a sameAs target; your company's official profile page is
• Update sameAs when platform URLs change — Twitter became X; old twitter.com URLs may redirect but the canonical URL is now x.com

In JSON-LD, the implementation is an array inside your Organization (or Person, or LocalBusiness) block:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example.com/#org",
  "name": "Sunrise Bakery",
  "url": "https://example.com",
  "sameAs": [
    "https://en.wikipedia.org/wiki/Sunrise_Bakery",
    "https://www.linkedin.com/company/sunrise-bakery",
    "https://www.facebook.com/sunrisebakery",
    "https://x.com/sunrisebakery"
  ]
}
</script>

Note the @id property in the example above. sameAs and @id work together: @id gives your entity a stable internal identifier that other JSON-LD blocks on your site can reference, while sameAs connects that entity to external platforms. Together they build a web of references that Google can follow from any entry point to confirm entity identity.

MendMySEO checks your Organization schema for missing sameAs properties, incorrect URL formats, and broken cross-references that prevent Knowledge Panel eligibility. Join the waitlist.

Frequently Asked Questions

Does sameAs directly improve rankings?

sameAs does not function as a ranking factor in the way backlinks or page speed do. Its effect is indirect: by helping Google correctly identify and disambiguate your entity, sameAs can trigger a Knowledge Panel, improve brand SERP presence, and increase click-through rates. The ranking benefit comes from entity confidence, not from the property itself.

How many sameAs URLs should I include?

Include every official platform profile where your entity is described. There is no upper limit, but every URL must point to a page that genuinely represents the same entity. Quality matters more than quantity — four verified profiles on authoritative platforms (Wikipedia, LinkedIn, Crunchbase, official social accounts) outweigh twenty links to minor directories.

Can I use sameAs for a Person, not just an Organization?

Yes. sameAs works on any Schema.org entity type. For a Person, link to their LinkedIn profile, Wikipedia page, ORCID, Google Scholar, or professional directory listing. The same rules apply: each URL must represent the same individual, not just mention them.

What happens if a sameAs URL is broken or redirects?

If a sameAs URL returns a 404, Google cannot verify the cross-reference and ignores it. If it redirects, Google may or may not follow the redirect for entity matching — the behavior is not guaranteed. Audit your sameAs URLs periodically to ensure they resolve to the expected pages. Platform URL changes (like Twitter migrating to x.com) require updating your sameAs values.

Is sameAs the same as adding social links in the footer?

No. Footer social links are HTML hyperlinks for human visitors. sameAs is structured data for search engines. Google does not parse your footer HTML to extract entity signals — it reads JSON-LD. Both can coexist, but only sameAs in your structured data feeds into Google's entity resolution and Knowledge Panel eligibility.