How to Fix Missing sameAs Links in Organization Schema
Your structured data has fewer than two sameAs URLs, so machines have little to confirm which LinkedIn page, Wikidata item or social account belongs to your brand. By the end of this guide you will have an Organization JSON-LD block with at least two verified, absolute sameAs URLs, live in the raw HTML of your site.

Why it matters
org states that this website and an external profile describe the same entity. Search engines use it to reconcile your brand into their knowledge graph, which feeds knowledge panels and correct entity attribution. AI assistants and answer engines lean on the same entity signals, especially Wikidata and LinkedIn, to decide which facts belong to you and to avoid mixing you up with a similarly named company.
Without sameAs, your brand is just a name string, and it is easier to confuse with others.
What you need
Step-by-step fix
Collect your official profile URLs
List every profile your organization actually controls or that is authoritative about it. Copy each URL from the browser address bar on the profile itself, not from a share link.
- LinkedIn company page: https://www.linkedin.com/company/your-slug
- Wikidata item: https://www.wikidata.org/wiki/Q…
- Crunchbase: https://www.crunchbase.com/organization/your-slug
- Social accounts: X, Facebook, Instagram, YouTube, TikTok, GitHub
You need at least two distinct URLs to pass this check.
Check whether you already output Organization schema
Open your homepage, choose View Source (Ctrl+U or Cmd+Option+U), and search for application/ld+json. If an SEO plugin or theme already prints an Organization or LocalBusiness block, add sameAs to that block instead of creating a second one. Two competing Organization entities with different names or logos send conflicting signals.
Add the sameAs array to your Organization JSON-LD
If you have no existing block, paste this into the <head> of your global template so it appears on every page. sameAs must be an array of absolute URLs as plain strings, not objects. Give the entity a stable @id so other schema, such as Article publisher, can reference it.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Example Co",
"url": "https://example.com/",
"logo": "https://example.com/logo.png",
"description": "Example Co makes scheduling software for small clinics.",
"sameAs": [
"https://www.linkedin.com/company/example-co",
"https://www.wikidata.org/wiki/Q00000000",
"https://www.crunchbase.com/organization/example-co",
"https://x.com/exampleco",
"https://www.youtube.com/@exampleco"
]
}
</script>Link back from the profiles to your website
sameAs is a claim, and it carries more weight when it is reciprocal. Set the website field on each profile to https://example.com/:
- LinkedIn: Admin tools → Edit page → Website URL
- Crunchbase: the website field
- Wikidata: the official website (P856) statement on your item
Check the social bios on your other accounts as well.
Make sure the JSON-LD is in the server-rendered HTML
Some crawlers, including many AI crawlers, do not run JavaScript. Insert the script through your template, plugin or server component, not through Google Tag Manager or a client-side script. Check that it renders on every page type, since some themes only print Organization schema on the homepage.
curl -s https://example.com/ | grep -o '"sameAs"[^]]*]'
Validate and re-run the audit
Paste your URL into validator.schema.org and confirm that the Organization node lists every sameAs URL with no errors. Then run Google's Rich Results Test to catch JSON syntax problems such as trailing commas. Finally, re-run the audit: it passes once two or more unique sameAs URLs are found across your crawled pages.
Platform-specific notes
WordPress (Yoast SEO / Rank Math)
In Yoast, go to Yoast SEO → Settings → Site representation. Pick Organization, then fill in the Facebook and X fields and use "Add another profile" for LinkedIn, Wikidata and Crunchbase. Yoast writes these into the Organization node's sameAs. In Rank Math, social URLs are entered under Rank Math SEO → Titles & Meta (Local SEO and Social Meta tabs). Don't also hand-code a second Organization block in header.php.
Shopify
Dawn and many other Online Store 2.0 themes build Organization JSON-LD from Online Store → Themes → Customize → Theme settings → Social media. Filling in two or more social links there may be enough. These themes often print the block on the homepage only, which still counts. Otherwise, add the script in Edit code → layout/theme.liquid inside <head>.
Wix
Wix generates some business schema automatically, but you can't reliably add sameAs to it. Add custom markup in Marketing & SEO → SEO → SEO Settings → Main Pages → Edit → Advanced SEO → Structured data markup. Or apply it to the homepage via Page settings → Advanced SEO → Structured data markup.
Webflow
Paste the script in Site settings → Custom code → Head code so it is global, then republish. Custom code requires a paid site plan.
Next.js
In app/layout.tsx, render <script type="application/ld+json" dangerouslySetInnerHTML={{ __html: JSON.stringify(orgSchema) }} /> inside a Server Component so it is in the initial HTML. Avoid next/script with strategy="afterInteractive" or "lazyOnload" for schema, because those load it client-side.
Check that it worked
✅ How to verify
- View the page source (not DevTools Elements) and confirm the sameAs array lists at least two different absolute URLs.
- Run the URL through validator.schema.org and confirm that the Organization entity shows sameAs with no errors or warnings.
- Fetch the page with curl or a crawler that has JavaScript disabled to confirm the JSON-LD is server-rendered.
- Re-run the audit and confirm the check shows pass and lists your sameAs URLs.
⚠️ Common mistakes
- Adding only one profile URL, which counts as a warning, or repeating the same URL with different tracking parameters.
- Pointing sameAs at share links, search results or a homepage like https://www.linkedin.com/ instead of the specific company profile.
- Injecting the schema through Google Tag Manager or client-side JavaScript, so non-rendering crawlers never see it.
- Creating a second Organization block alongside your SEO plugin's, with mismatched names or logos.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
What should I put in sameAs for an organization?
Use the URLs of authoritative profiles that describe the same organization: your LinkedIn company page, Wikidata item, Crunchbase profile, Wikipedia article if one exists, and your official social accounts (X, Facebook, Instagram, YouTube, GitHub). Leave out directories you don't control and pages that merely mention you.
Does sameAs help SEO or AI search?
It isn't a direct ranking factor. It helps search engines and AI systems resolve your brand to the correct entity, which supports knowledge panels and accurate brand facts. It also reduces confusion with similarly named companies in AI-generated answers.
Do I need a Wikidata entry to use sameAs?
No. LinkedIn plus one or more social profiles is enough to pass this check. Wikidata is a strong entity signal, but only create an item if your organization meets Wikidata's notability requirements and you can cite independent sources.
Should sameAs be on every page or only the homepage?
Placing the Organization block in your global template is simplest and keeps it consistent. Search engines mainly need it on the homepage, but a sitewide block with a stable @id lets other schema on inner pages reference the same entity.
How to Fix Missing FAQPage Schema on Your FAQ Pages
How to Make Your Brand Facts Consistent Across the Web
How to Fix Missing Step-by-Step Formatting for AI Answers
How to Fix Entity Clarity: State Who, What and Where
How to Add Comparison Tables That AI Search Can Extract
How to Add Concise Answer Blocks for AI Search Engines