Add Organization sameAs for AI & Knowledge Graph
Your homepage's Organization structured data exists but has no sameAs property. That property is the array of official profile URLs (LinkedIn, X, Wikipedia, Wikidata, Crunchbase, GitHub) that lets search engines and AI answer engines resolve your website to a single, known brand entity. Without it, engines see a name and a logo but cannot confirm which real-world organization you are. Fix it by adding a sameAs array to your Organization JSON-LD, leading with a Wikipedia or Wikidata link if one exists, then your authoritative social and business profiles.
What this means
sameAs is a schema.org property holding an array of URLs that point to other authoritative pages describing the same entity: your official LinkedIn company page, your X/Twitter profile, your Wikipedia or Wikidata entry, your Crunchbase, YouTube, or GitHub org. It tells engines that all those profiles and your website are the same organization.
This audit flagged missing_sameas because we read your actual Organization schema, not just whether it exists, and found the schema present but with no sameAs array (or an empty one). So the entity has a name and possibly a logo, but nothing linking it to its verified presence elsewhere on the web.
Think of sameAs as identity disambiguation. Many businesses may share your name. The sameAs links are the fingerprints that let an engine say "this is that company, the one with this LinkedIn page and this Wikidata ID" instead of treating your site as an unidentified brand.
Why it matters
For classic Google ranking, sameAs feeds the Knowledge Graph. It is one of the signals Google uses to connect your website to a Knowledge Panel and reconcile your brand across the web. It strengthens entity understanding, which supports E-E-A-T and brand SERP features. It will not move a keyword ranking on its own, but it hardens the identity layer that other trust signals sit on.
For AI answer engines the stakes are higher. ChatGPT, Perplexity, Google AI Overviews, and Gemini resolve a brand to a known entity before they decide what to say about it. When your Organization schema links out to LinkedIn, Wikipedia, and Crunchbase, you hand those engines a verified identity graph they can cross-reference. When it links to nothing, you are an unidentified brand, which is far easier to skip, misattribute, or confuse with a same-named competitor.
The strongest single anchor is a Wikipedia or Wikidata URL, because Wikidata is a primary input to Google's Knowledge Graph. If an entry exists for your brand and is not in your sameAs, adding it is the highest-leverage line in the array. If none exists, your authoritative social and business profiles still do real work.
How to fix it
- 1
Gather your authoritative profile URLs
List the canonical URLs for every official profile your organization controls: LinkedIn company page, X/Twitter, Facebook, Instagram, YouTube channel, GitHub org, Crunchbase, and your Google Business Profile. Use the full public profile URL, not a share link or vanity redirect. Only include accounts you actually own and that clearly represent the brand. A third-party mention or press article does not belong in sameAs.
- 2
Check for a Wikipedia or Wikidata entry
Search Wikidata (wikidata.org) and Wikipedia for your brand. If an entry exists, grab its URL (Wikidata IDs look like https://www.wikidata.org/wiki/Q12345) and make it the first item in your array. It is the strongest knowledge-graph anchor an AI engine can read. If no entry exists, skip this and rely on your social and business profiles. Do not fabricate or link an unrelated entity.
- 3
Add the sameAs array to your Organization schema
Locate the Organization (or LocalBusiness) JSON-LD block on your homepage. It usually sits in a <script type="application/ld+json"> tag in the <head>. Add a sameAs property whose value is an array of your profile URLs, and use absolute URLs (Google requires absolute URLs for sameAs). Keep it on the same entity that already carries your name, url, and logo. If your homepage has no Organization schema at all, add one first, then include sameAs inside it.
- 4
Publish once, on the homepage, and keep it consistent
Organization schema belongs on your homepage or a canonical /about page. You do not need to repeat the full sameAs array on every page. Make the brand name in your schema match your og:site_name and <title> so engines treat them as one entity. Avoid conflicting Organization blocks across pages, which can split your identity signals.
- 5
Validate and request a recrawl
Run your homepage through the Schema Markup Validator (validator.schema.org) to confirm the JSON-LD parses cleanly, and Google's Rich Results Test to confirm Google reads the block without errors (Organization markup does not produce a visual rich result, so expect it to validate rather than preview one). Confirm every sameAs URL resolves. Then re-run your audit and use URL Inspection in Google Search Console to request indexing so the updated entity data is picked up sooner.
Example
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Acme Analytics",
"url": "https://www.acmeanalytics.com",
"logo": "https://www.acmeanalytics.com/logo.png",
"description": "Web analytics software for product teams.",
"sameAs": [
"https://www.wikidata.org/wiki/Q112233",
"https://en.wikipedia.org/wiki/Acme_Analytics",
"https://www.linkedin.com/company/acme-analytics",
"https://x.com/acmeanalytics",
"https://www.youtube.com/@acmeanalytics",
"https://github.com/acme-analytics",
"https://www.crunchbase.com/organization/acme-analytics"
]
}
</script>A complete Organization JSON-LD block with a sameAs array. Put this in a <script type="application/ld+json"> tag in your homepage <head>. Lead with Wikidata/Wikipedia if you have one, then your owned profiles. Use absolute URLs.
Platform-specific steps
Yoast auto-generates Organization schema from your Knowledge Graph settings. Go to Yoast SEO > Settings > Site basics and set the site to represent an Organization, then add your social profile URLs (Facebook, X, Instagram, LinkedIn, YouTube). Yoast writes those into the sameAs array automatically. Wikidata and Wikipedia are not default fields, so add them via the wpseo_schema_organization filter or a custom JSON-LD block if you have an entry.
Open Rank Math > Titles & Meta > Local SEO (or the Schema settings) and set the Knowledge Graph type to Organization. Fill in the social profile URLs under the organization settings; Rank Math outputs them as sameAs. To add Wikidata, Wikipedia, or other profiles the UI does not expose, use the Custom Schema builder on the homepage and add them to the sameAs array.
Shopify's default themes emit basic Organization schema but rarely a full sameAs array. Edit theme.liquid (or your theme's schema snippet) and add a <script type="application/ld+json"> Organization block with your sameAs array in the <head>. Alternatively use a JSON-LD SEO app that exposes an organization or social-profiles field, then confirm it renders in view-source.
Wix generates limited schema automatically. Use Settings > SEO to add business info and social links where available. For a full sameAs array, add a Custom Code element (Settings > Custom Code) that injects your Organization JSON-LD into the <head> on the homepage, since the built-in fields do not cover profiles like Wikidata or Crunchbase.
Squarespace does not expose Organization sameAs through the UI. Add it via Settings > Advanced > Code Injection > Header, pasting your full Organization JSON-LD script including the sameAs array. Connecting social accounts under Settings > Social Links affects display but does not populate schema sameAs, so code injection is required.
Render the Organization JSON-LD server-side so crawlers get it in the initial HTML. In Next.js, inject it with a <script type="application/ld+json"> using dangerouslySetInnerHTML in your root layout or homepage. Keep one source of truth for the sameAs array so the same identity ships on every render, and verify it appears in view-source, not only after hydration.
Frequently asked
It is an Organization (or Person) property holding an array of URLs to other authoritative pages about the same entity: your official LinkedIn, X, Wikipedia, Wikidata, Crunchbase, YouTube, or GitHub. It tells search engines and AI engines that all those profiles and your website are the same real-world organization.
Only profiles you own or that authoritatively represent your brand. Prioritize a Wikipedia or Wikidata URL if one exists, then your LinkedIn company page, X/Twitter, YouTube, GitHub, Crunchbase, and major social accounts. Do not add press articles, affiliate pages, or unrelated mentions. sameAs is for identity, not backlinks.
Yes. These engines resolve your brand to a known entity before deciding what to say about it. A sameAs array that links to a knowledge-graph entry and verified profiles gives them a cross-referenceable identity, which reduces the chance they skip you or confuse you with a same-named competitor. A Wikipedia or Wikidata link is the strongest single signal because Wikidata feeds Google's Knowledge Graph.
No. If one exists for your brand, add it first, since it is the strongest anchor. If none exists, your official social and business profiles still resolve the entity and clear the warning. Do not invent or link an unrelated Wikidata entity to fill the slot. A wrong anchor is worse than none.
On your homepage, or a canonical /about page, as one authoritative Organization block. You do not need to repeat the full sameAs array on every page. Keep the brand name consistent across your title tag, og:site_name, and schema so engines treat them as one entity.
Does your site have this issue?
Run a free, AI-powered audit and we’ll flag this and 150+ other checks in about a minute. No signup.