Sub-grade spoke
Business Identity — does your site tell agents who you are?
Agents disambiguate companies the same way humans do: by name, address, phone, social profiles, and registered-entity records. The signal stack is Organization schema with sameAs links, consistent NAP across the web, and verified trust surfaces. Sites that publish identity legibly get cited as the primary source; sites that don't get cited as a derivative mention or not at all.
By Chris Mühlnickel · 2026-05-16
What is Business Identity?
Business Identity is whether your site emits a complete Organization schema block with sameAs links to authoritative profiles, maintains consistent name/address/phone (NAP) data across the web, and resolves cleanly to a single canonical entity for AI agents.
By the numbers
- 597K — Article→publisher→Organization relationships counted in 2024 Web Almanac structured-data corpus. (HTTP Archive Web Almanac 2024 — Structured Data)
- 40% — more likely to appear in Google's local pack when NAP data is consistent across major citation sources. (BrightLocal — What is NAP in Local SEO?)
- 745K — LocalBusiness→address→PostalAddress connections measured by Web Almanac — the canonical agent identity signal. (HTTP Archive Web Almanac 2024 — Structured Data)
Why it matters
Identity signals decide whether you're a primary source or a secondary mention. When ChatGPT, Claude, or Gemini cites a fact about your company, the citation goes to the canonical source — usually whoever has the strongest Organization schema with sameAs links to authoritative registries, the cleanest NAP consistency across the web, and the most stable identity-verification surface. Sites that publish their identity legibly get cited as the source; sites that don't get cited as a derivative mention or not at all. The Web Almanac's 597K Article-publisher-Organization relationships are the visible footprint of this disambiguation graph — every citation an agent emits walks through it.
NAP consistency is the foundation, not the optimization. BrightLocal's data puts the local-pack uplift at 40% for businesses with consistent name, address, and phone across major citation sources — and the agent-citation premium tracks the same shape, even for non-local businesses. The failure mode is unsexy: a rebrand that updates the website but not the LinkedIn page, an address change that propagates to Google but not the company's own footer, a phone number that's correct on the Contact page but wrong on the Support page. Each inconsistency forks the agent's entity graph, and the resolution defaults to unclear, don't cite.
sameAs is the bridge between your site and the rest of the web. An Organization schema block without sameAs links is a closed-loop claim — we're Acme Inc, source: us. Adding sameAs to LinkedIn, Crunchbase, Wikipedia, GitHub, and authoritative industry directories converts the claim to a verifiable cross-reference. The Web Almanac counted 745K LocalBusiness-address-PostalAddress connections in 2024; the disambiguation graph already exists, and Business Identity is whether your site connects to it.
Marketplace verification compounds the on-site signal. Salesforce AppExchange, Microsoft AppSource, HubSpot App Marketplace, Shopify App Store — each marketplace listing is a trust surface that compounds the basic identity stack. Agents routing B2B decisions weight verified-listing signals heavily because they encode third-party validation: someone with a stake (the marketplace operator) staked their gating on the company being who it claims to be. For SaaS in particular, marketplace presence is increasingly the cheap-to-acquire identity primitive that separates legibly established from might be real, can't tell.
Where it's heading
Identity verification gets capability-level. Today, business identity is binary — verified or not. The next layer is what is this entity verified to do? A Stripe-verified merchant has different credentials than a SOC2-verified SaaS than an AppExchange-verified Salesforce ISV. Agent-routing decisions will use these capability-level identity signals to decide which actions to delegate; sites with strong basic identity today are positioned to layer capability-verification cheaply.
Knowledge graph entries become a first-class identity surface. Google's Knowledge Graph and the analogous entity stores in OpenAI, Anthropic, and Perplexity's training pipelines are the canonical home for company identity at the agent layer. Sites with clean Organization schema today flow into these graphs cheaply; sites without it require external corroboration that's expensive to manufacture later.
Cross-vendor identity registries. A neutral entity registry — DUNS, IATA, or an emerging cross-vendor agent-identity standard — could become the canonical sameAs target for company identity, in the same way iss claims work for OIDC today. Companies that already invest in registered-entity verification are positioned for that transition; companies that don't will need to invest then.
Common mistakes
- Organization schema only on the homepage. The block should appear site-wide as a JSON-LD include — every page that represents the company benefits from the same identity declaration.
- Missing or thin `sameAs` arrays. A schema block with no external profile links is a closed-loop claim — adding LinkedIn, Crunchbase, and the relevant industry directories is the cheapest credibility upgrade available.
- NAP inconsistency across owned surfaces. Footer says one address, Contact page says another, About page says a third. Each fork costs identity weight without any team noticing until citations fragment.
- No `logo` URL in the schema block. Agents and search engines surface the logo as part of the entity card; missing it shows up as a generic placeholder and signals an incomplete identity declaration.
- Treating Google Business Profile as a substitute for Organization schema. GBP covers local search; Organization schema covers everything else agents read. Both matter, and they reinforce each other rather than substituting.
Frequently asked
What goes in an [Organization schema](/learn/glossary#term-organization-schema) block?
At minimum: name, url, logo, description, sameAs (array of links to your LinkedIn, Crunchbase, Wikipedia, and authoritative profiles), and contactPoint. For local businesses, add address as a PostalAddress and telephone. The block belongs in a site-wide template — homepage at minimum, every page ideally — emitted as JSON-LD.
Why are `sameAs` links so important?
They're the bridge between your site's claim about itself and external verification. An agent encountering an unfamiliar company name uses sameAs to traverse to LinkedIn, Crunchbase, Wikipedia — and treats the cross-referenced identity as substantially more reliable than a name on a page with no external corroboration. The 597K Article-publisher-Organization links the Web Almanac counted are exactly this disambiguation graph at scale.
How does Google Business Profile interact with Organization schema?
They're complementary signals. Google Business Profile is the canonical source for local-search identity (NAP, hours, photos); Organization schema is the on-site declaration that agents and search engines cross-reference against it. For service-local businesses, both should align — a mismatch costs the BrightLocal 40% local-pack premium that NAP consistency unlocks.
What's NAP consistency and how do I check it?
Name, Address, Phone — the three identity fields that must match across every directory, profile, and citation source your business appears in. Inconsistencies fragment the agent's entity graph: is this Acme Inc the same as Acme, Inc.? Tools like BrightLocal, Whitespark, and Moz Local audit consistency across major directories; a Spekto audit flags the on-site mismatches that downstream sources inherit.
Do I need a Wikipedia entry to be cited?
No, but having one materially helps agent disambiguation. Wikipedia is one of the highest-weighted entity sources in most LLM training corpora, and a clean Wikipedia entry with structured infobox data is functionally a Knowledge Graph entry. The threshold for inclusion is non-trivial, though — sameAs links to LinkedIn, Crunchbase, and authoritative industry directories cover most of the same ground for non-Wikipedia companies.
What about B2B SaaS — does this apply?
Yes, with different emphasis. B2B Organization schema should include sameAs to LinkedIn company page, Crunchbase, AngelList or similar, GitHub if applicable, and any platform marketplaces (AppExchange, AppSource, HubSpot App Marketplace). Marketplace verification status is increasingly load-bearing — agents routing enterprise decisions weight verified-listing signals heavily.
Does identity matter if my Schema.org coverage is otherwise complete?
Yes. Schema Coverage is the umbrella signal; Business Identity is the who is this company slice. An e-commerce site with valid Product schema but no Organization block forces agents to guess the seller's identity at every comparison step — costing the trust premium even when the product markup is otherwise perfect.