By the iSuggest.ai Team · Updated for 2026
This is another entry in our running series of single, concrete things you can add to your site today for better GEO readiness. Today's fix takes about fifteen minutes: a complete sameAs array on your Organization schema.
What sameAs is actually for
sameAs is a schema.org property that lists other URLs which represent the exact same real-world entity as the page it's attached to. On an Organization node, that means your Wikipedia page (if you have one), your Wikidata entry, your LinkedIn company page, your Crunchbase profile, and your official social accounts. It is not a list of "related links" or partners — every URL in the array should point to a page that is unambiguously you, not a page about you written by someone else.
Why AI engines care about this more than a search ranking does
A traditional search index mostly needs to match keywords and rank pages. A generative engine trying to answer "who is this company" or "is this a real business" has a harder problem: entity resolution. It needs to decide whether the "Acme Inc." on your homepage is the same Acme Inc. that has a Wikidata entry, a Crunchbase page, and a LinkedIn presence — or a coincidence of naming. A complete sameAs array removes the guesswork. It's a direct, machine-readable statement: these profiles and this website are one entity. That's the same underlying idea we cover in Entity Clarity: Why AI Engines Need to Know Who You Are — sameAs is one of the more mechanical, checkbox-able ways to act on it.
What a complete array actually looks like
A minimal, honest sameAs array for a small business or SaaS company typically includes whichever of these actually exist and are actually yours:
- Your Wikipedia page, if one exists (do not create one just for this — that's a separate, higher-bar project)
- Your Wikidata item, if one exists
- Your official LinkedIn company page
- Your Crunchbase profile, if you have funding or are commonly looked up there
- Official X/Twitter, Instagram, YouTube, or Facebook accounts you actually maintain
- Your GitHub organization page, if you're a technical company with public repos
A common mistake is listing only one or two of these when three or four exist, or including a personal profile of a founder instead of the company's own account. The array should represent the organization, not any one person inside it (a founder's personal sameAs is a separate, valid thing to add to a Person node elsewhere, but don't mix the two).
Where the JSON-LD actually goes
You don't need a schema plugin for this. A small, hand-written block in your homepage's <head> is enough:
A basic pattern is a script type="application/ld+json" block containing an @type: Organization object with your name, url, and a sameAs array of the profile URLs above. Keep it on the homepage (or wherever your site already declares its Organization entity — some sites put it in a shared header template instead), and keep the array current: a stale link to a deactivated social account is worse than no link at all, because it points the entity resolution the wrong direction instead of just leaving a gap.
One honest caveat, from us
We'll say this plainly rather than let a claim slide by unchecked: iSuggest.ai's own audit does not currently score whether your sameAs array is complete. Our audit engine reports which structured-data types a page uses — that a page declares an Organization node at all — but not the specific properties inside it, so we can't honestly measure completeness of sameAs the way we measure, say, whether a meta description exists. We'd rather tell you that directly than pretend to check something we can't observe. That doesn't make the fix less worth doing — it's still one of the more overlooked, low-effort entity signals available, and you can see everything our audit does check in Inside an iSuggest.ai Audit: What We Measure.
Where this fits with the rest of your structured data
sameAs is one property on one node type. It pairs naturally with the broader structured-data work covered in Structured Data for AI Search Engines and with the FAQ markup covered in FAQ Schema and AI Citations: The Fastest Way — none of these fixes work in isolation, but each one is small enough to ship in an afternoon. If you want to see where your page actually stands before or after adding it, run a free audit from the homepage or read how the audit works. Once a page scores well enough, publishing it to an AI directory takes one more step, covered in your account.