mail@crispycontent.de
Last updated on September 8, 2026 at 12:08 PM.
A sameAs array in JSON-LD unambiguously connects a website entity to its official profiles on Wikipedia, Wikidata, LinkedIn and other authoritative sources. Search engines and AI systems use this linkage to recognise brands as verified entities in the Knowledge Graph—rather than treating them as isolated web pages. Structured data is a technical instrument, not an end in itself. It only delivers value once it is clear which brand values, products and services need to be communicated to which audience. Visibility starts not with technology but with the question of what information creates value for which audience. How positioning, USPs and relevant contexts translate into a robust content architecture—from entity level down to individual articles—is outlined by Crispy Content in the area of content strategy. This article explains core concepts, JSON-LD syntax, implementation steps, common mistakes and the implications for AI visibility.
Why entity linking via sameAs matters for B2B brands
Search engines operate on an entity-based model. That means Google, Bing and the AI systems built on top of them no longer simply match keywords to pages—they attempt to understand which real-world entity stands behind a website: which company, which person, which product. Without explicit linking, a brand remains ambiguous to these algorithms. And ambiguity is the opposite of visibility.
Search engines are no longer the only place where a brand is discovered. Anyone who wants to understand how visibility for Google and for the answers generated by ChatGPT, Perplexity and similar systems can be managed in a data-driven, automated way will find a methodical approach at Crispy Content on Agentic SEO and Generative Engine Optimization—where structured data and sameAs links become a measurable signal for AI systems.
The 2025 BrightEdge report shows a positive correlation between structured data implementation and the likelihood of being cited in AI-generated search results. This is no coincidence: when you explicitly tell a machine who you are and where the evidence resides, you are favoured whenever that machine needs to verify sources. Implementation is a one-time effort; the impact on visibility is long-term—a cost-to-benefit ratio that makes clear business sense.
Core concepts – What sameAs, JSON-LD and entity mean in the Schema.org context
Before implementation begins, three terms must be defined precisely. Confusing them leads to structured data that is technically valid yet semantically worthless.
What is an entity in the Schema.org context?
An entity is a uniquely identifiable thing—an organisation, a person, a product, a concept. In the Knowledge Graph, an entity exists independently of individual web pages. It has properties (name, founding date, location) and relationships to other entities. The difference from a keyword: a keyword is a character string; an entity is a concept with identity. "Apple" as a keyword is ambiguous. "Apple Inc." as an entity with Wikidata ID Q312 is unambiguous.
What does sameAs mean in JSON-LD?
The official definition according to schema.org reads: "URL of a reference Web page that unambiguously indicates the item's identity." The sameAs property links a local entity on your own website to external authoritative sources—it tells the machine: "The company we describe here is the same company described on this Wikipedia page." The distinction from @id is critical: @id is an internal URI for referencing within your own schema blocks; sameAs points outward to independent third-party sources.
JSON-LD as the preferred format for structured data
JSON-LD stands for JavaScript Object Notation for Linked Data. Google explicitly recommends this format over Microdata or RDFa. The advantage: JSON-LD blocks sit in the <head> or <body> as a standalone <script> element, completely separated from the visible HTML content. This separation makes implementation, maintenance and debugging significantly easier than formats embedded directly in HTML tags.
The core principle – How sameAs arrays disambiguate entities
The underlying mechanism is straightforward: a sameAs array provides search engines with a reference point between your own website and known databases. When the Organization schema on the homepage states "We are Company X" and the sameAs array points to the Wikipedia article, the Wikidata entry and the LinkedIn page of Company X, Google can triangulate this information. The entity is validated.
The analogy: sameAs works like a digital identity document. An ID card does not prove that someone exists—the person is standing right there. It proves that the person standing there is the same one registered in the government database. That is exactly what sameAs does for machines: it confirms that "Organisation X on this website" and "Organisation X on Wikipedia" are the same entity.
Google uses this linkage specifically to populate Knowledge Panels and to validate entity information. Without sameAs, Google must infer this mapping on its own—with sameAs, it is explicitly declared. Explicit beats implicit when machines decide.
| Property | Function | Target |
|---|---|---|
| sameAs | External identity linking | Wikipedia, Wikidata, LinkedIn, Crunchbase |
| @id | Internal unique URI | Referencing within your own schema blocks |
| url | Official website URL | Main page of the entity |
Getting started – Implementing a sameAs array in the Organization schema
Implementation follows four steps. None of them is technically complex—but each requires diligence. A sameAs array with incorrect or dead URLs is worse than none at all.
Step 1 – Identify and prioritise authoritative profiles
Not every profile belongs in the sameAs array. The tier model prioritises by impact on entity validation:
| Tier | Sources | Impact on Knowledge Graph |
|---|---|---|
| 1 | Wikipedia, Wikidata, official social profiles (X/Twitter) | Highest impact on entity validation |
| 2 | LinkedIn Company Page, Crunchbase, Google Business Profile | Strong impact |
| 3 | YouTube channel, GitHub, Facebook page | Supporting |
The rule: only include verified, active profiles. A LinkedIn profile that has not been updated since 2019 weakens the signal rather than strengthening it.
Step 2 – Create the JSON-LD block with a sameAs array
A concrete example for a B2B company:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.beispiel-unternehmen.de/#organization",
"name": "Beispiel GmbH",
"url": "https://www.beispiel-unternehmen.de",
"logo": "https://www.beispiel-unternehmen.de/logo.png",
"sameAs": [
"https://de.wikipedia.org/wiki/Beispiel_GmbH",
"https://www.wikidata.org/wiki/Q123456789",
"https://www.linkedin.com/company/beispiel-gmbh",
"https://www.crunchbase.com/organization/beispiel-gmbh",
"https://twitter.com/beispielgmbh"
]
}
</script>
This block belongs in the <head> of the homepage. Subpages reference the organisation via @id without repeating the full schema.
Step 3 – Ensure consistency across all linked profiles
NAP data (Name, Address, Phone) must be identical across all sameAs targets. If the website reads "Beispiel GmbH", the Wikipedia article says "Beispiel Gesellschaft mit beschränkter Haftung" and LinkedIn shows "BEISPIEL"—the machine sees three different entities instead of one. Inconsistencies measurably weaken the entity signal. The spelling in the schema block is the reference; all external profiles are aligned to it.
Step 4 – Validation and monitoring
Three tools for verification: Google Rich Results Test for technical validity, Schema.org Validator for semantic correctness, Search Console Structured Data Report for ongoing monitoring in the index. Additionally: regular checks for dead links in the sameAs array. A 404 in sameAs is like an expired identity document—it proves nothing.
A consistent entity strategy built on structured data makes brand communication equally readable for search engines and AI systems. Organisations that cannot handle implementation in-house may find a suitable partner for technical execution in specialised B2B communications agencies such as Crispy Content®.
Common mistakes with Schema sameAs – and how to avoid them
Implementation is not hard. Maintenance is. Five errors appear repeatedly in practice:
- Dead URLs in the sameAs array: Linked profiles no longer exist or return a 404. The solution is a quarterly audit of all sameAs URLs—easily automated with any crawling tool.
- Inconsistent entity data: The company name on Wikipedia differs from the schema entry. Uniform spelling across all platforms is mandatory, not optional.
- Linking irrelevant profiles: Personal social media accounts instead of official company profiles. Only controlled, official presences belong in the array.
- Confusing sameAs with @id: @id is an internal reference; sameAs points outward. Both properties work complementarily—@id for internal architecture, sameAs for external validation.
- Over-marking: Equipping every subpage with the full Organization schema instead of referencing via @id. The Organization schema belongs on the homepage; subpages reference via @id.
Structured data, entities and AI visibility – future implications
The question is no longer whether structured data is relevant for AI systems. The question is how quickly the window closes in which a clean implementation still provides a competitive edge.
sameAs as a trust signal for Large Language Models
AI systems such as Google AI Overviews, ChatGPT Search and Bing Copilot use structured data for source verification. When an LLM must decide which source to cite, it favours entities it already knows—and sameAs links connect your brand precisely to those known entities. The 2025 BrightEdge report documents the positive correlation: websites with structured data are more likely to be cited in generative AI responses.
Entity-first indexing and Knowledge Graph expansion
Google increasingly processes search queries via entities rather than keywords. An Organization schema with sameAs, knowsAbout and @id forms a machine-readable entity graph that extends far beyond a single web page. The forecast: AI systems will cross-check schema declarations against live sources. Inaccurate data will not be ignored—it will be penalised. Anyone who declares false information in their schema today risks exclusion from AI-generated answers tomorrow.
| Metric | Value | Source |
|---|---|---|
| CTR increase through Rich Results | 20–30 % | Stackmatix 2026 |
| Correlation Structured Data ↔ AI citation | Positive | BrightEdge 2025 |
| Knowledge Graph entities disappeared (2025) | > 3 bn | Search Engine Land 2025 |
The third row is the wake-up call: over three billion entities disappeared from the Knowledge Graph in 2025. Anyone who does not actively maintain and validate their entity will lose it.
From the sameAs array to a complete entity strategy
The sameAs array is the starting point, not the destination. Three extensions turn a single property into a complete semantic architecture:
- knowsAbout property: Declares the thematic expertise of the organisation. When the Organization schema states "We have expertise in content strategy, SEO and structured data", it provides AI systems with a relevance signal for precisely those topics.
- Publisher reference in content schemata: Link BlogPosting and Article schema with a publisher reference to the Organization @id. This way, every published piece of content inherits the entity authority of the organisation—a multiplier that grows with each new article.
- Multilingual strategy: Combine inLanguage and hreflang with consistent entity data. The entity remains the same regardless of language—but the machine must be told this explicitly.
The learning path leads from a single sameAs implementation to a complete semantic architecture: Organization → Service → Person → Article. Each layer references the one above via @id. The result is not markup on a page but a machine-readable graph that maps the entire digital presence of a brand. Methods provide guarantees—and a clean entity graph guarantees machines that they are dealing with a real, verified organisation.
Sources
Google (2025): Introduction to Structured Data Markup in Google Search. URL: https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data (accessed 20 July 2026).
BrightEdge (2025): The State of Structured Data 2025. URL: https://www.brightedge.com/blog/structured-data-ai-search-era (accessed 20 July 2026).
Grudowski, Rafał / Grupa Insight (2026): Structured Data in 2026: Schema.org, AI Search and E-E-A-T. URL: https://www.grupainsight.com/articles/structured-data-in-the-era-of-ai-search-how-schema-org-strengthens-e-e-a-t-and-dominates-ai-overviews-sge-and-zero-click-results (accessed 20 July 2026).
Stackmatix / Matt Pru (2026): Organization Schema Markup: Complete Guide to Knowledge Graph & Entity SEO. URL: https://www.stackmatix.com/blog/organization-schema-knowledge-graph (accessed 20 July 2026).
Schema.org (continuously updated): sameAs – Schema.org Property. URL: https://schema.org/sameAs (accessed 20 July 2026).
Google (2025): Organization Schema Markup. URL: https://developers.google.com/search/docs/appearance/structured-data/organization (accessed 20 July 2026).
Gerrit Grunert
Gerrit Grunert is the founder and CEO of Crispy Content®. In 2019, he published his book "Methodical Content Marketing" published by Springer Gabler, as well as the series of online courses "Making Content." In his free time, Gerrit is a passionate guitar collector, likes reading books by Stefan Zweig, and listening to music from the day before yesterday.
.png)
.jpg)
-1.jpg)
-1.jpg)
.jpg)
.jpg)
.jpg)
