Agent view · Guides · 2026-09-30
JSON-LD @id errors: what breaks and how to fix it
This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/guides/json-ld-id-and-iri-errors-what-breaks-and-how-to-fix-them: fetched when you opened this page, shown byte for byte. An assistant, a crawler that negotiates markdown, or anything reading our feed gets exactly this. The markdown leaves signed (RFC 9421, key in our key directory), so a crawler can prove the page it read is the page this server sent; the check is shown below.
| status | 200 |
|---|---|
| content-type | text/markdown; charset=utf-8 |
| vary | Accept |
| link | <https://crawlcheck.io/llms.txt>; rel="describedby"; type="text/plain", <https://crawlcheck.io/.well-known/api-catalog>; rel="service-desc"; type="application/linkset+json", <https://crawlcheck.io/guides/json-ld-id-and-iri-errors-what-breaks-and-how-to-fix-them>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory" |
| cache-control | public, max-age=900, stale-while-revalidate=2400 |
| bytes | 18,160 |
| words | 2,649 |
| sha-256 | 07206c5e7b259320d1850e247fe705064da61005db059880270800cdfa862a70 |
| repr-digest | sha-256=:ByBsXnslkyDRhQ4kf+cFBk2mEAXbBZiAJwgAzfqGKnA=: ← matches the body shown |
| signature-input | sig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795182381;expires=1795185981;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="zcOgCGc-ceFb2M4VenmNag";tag="crawlcheck-page" |
| signature | sig1=:uD1ggwwBOiVmt5m8JdsmD90VZa7U8yDVnN1Ey4LMgbOVnRaM5euUsz62YN5JStAn3nKNl30SKi0lo2HYlqnyAw==: |
| verified | yes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3600 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba |
Guides · 2026-09-30 · By [VSNARY | Emmanuel Orta](/author) · 2 views
# JSON-LD @id errors: what breaks and how to fix it
Six identifier defects no vocabulary validator reports: blank nodes, path @ids that 404, Unicode normalisation, raw IDN hosts, encoding drift and rival roots. Plus the duplicate that is not a defect.
A JSON-LD @id is the IRI that identifies a node in the graph a consumer builds; two nodes with the same @id are one node. Six defects slip past vocabulary validators: blank-node identifiers (_:), path-form @ids that can 404, values not in Unicode NFC, raw internationalised hostnames, percent-encoding that varies on one path, and rival roots (one business under two @ids). The fix is one fragment-form @id per entity on the canonical host, NFC-normalised, referenced rather than restated everywhere.
Check your own site free
Check my site
About a minute. First scan free with your email, nothing installed.
On this page
- What an @id is for
- Six identifier defects to check
- Two nodes, one @id: duplicate or collision?
- The sameAs side
- How to fix it in one pass
- Checking a page by hand
- What this is not
An `@id` is not a label. It is an [IRI](/glossary/iri), an internationalised [URI](/glossary/uri), and the graph a consumer builds from your page treats two nodes with the same `@id` as one node and two nodes with different `@id`s as two things, whatever their names say. Most pages that carry one got it from a plugin default rather than a decision. Six identifier defects follow from that rule, and no validator checking schema.org vocabulary mentions them, because the vocabulary is fine; it is the identifiers that are wrong.
## What an @id is for #
A consumer that reads [JSON-LD](/glossary/json-ld), whether a search engine, an [answer engine](/glossary/answer-engine) or a knowledge-graph pipeline, converts it to triples: subject, predicate, object. The subject of every [triple](/glossary/triple) is the node's `@id`. A node without one gets a blank node, an identifier that exists only inside that one document and can never be referred to from anywhere else. A node with `@id` `https://example.com/#organization` can be referenced from every other page on the site, from a [Wikidata](/glossary/wikidata) entry and from another site's `sameAs`, and all of those references resolve to the same subject. That is the entire value of the field: it lets the world agree on which thing you are.
## Six identifier defects to check #
**Blank-node identifiers.** An `@id` beginning `_:` is a blank node written out by hand. It is legal JSON-LD and it is useless as an identity, because `_:b0` in your document and `_:b0` in anyone else's are unrelated. The fix is to give the node a real IRI on your own domain.
**Fragment versus path.** An `@id` on your own host can be in fragment form, `https://example.com/#org`, or path form, `https://example.com/org`. Both are valid IRIs. The difference is what happens when someone fetches them. A path IRI is a [URL](/glossary/url) that should return something, and if `/org` returns a 404, the identifier points at nothing. A fragment IRI resolves to the page that carries the node, which always exists. Fragment form is the safer default for entities that do not have a page of their own.
**Unicode normalisation.** An IRI containing accented characters can be written in composed form (one code point per accented letter) or decomposed form (base letter plus combining mark). They render identically and compare unequal. The fix is to normalise to NFC before writing the value, which every language runtime can do in one call.
**Raw internationalised hostnames.** When an `@id` or `url` carries a hostname with non-ASCII characters, consumers differ on whether they convert it to punycode before comparing, so the same business can appear under two hosts. Write the punycode form, `xn--`, in identifiers.
**Percent-encoding drift.** The same path written with two different encodings, `/caf%C3%A9` and `/café`, decodes to one path and compares as two identifiers.
**[Rival roots](/glossary/rival-roots).** Two top-level organisation-like nodes with the same normalised name but different `@id`s are the same business declared as two entities. This is the one that does the most damage, because a consumer has no way to merge them, and the corroboration that one node earns from a directory or a review site does not accrue to the other. Unlinked organisation nodes of this kind turn up on 2.6% of scanned sites. The opposite case, one node parsed twice under the same `@id`, is not a defect at all; see below.
| Defect | Looks like | Consequence | Fix |
| --- | --- | --- | --- |
| blank node | `"@id": "_:b0"` | cannot be referenced from anywhere | own-domain IRI |
| path @id that 404s | `https://x.com/org` | identifier points at nothing | fragment form or a real page |
| not NFC | é as e + combining acute | same string compares unequal | normalise to NFC |
| raw IDN host | `https://müller.de/#org` | two hosts to some consumers | punycode host |
| encoding drift | `/caf%C3%A9` and `/café` | one path, two identifiers | one spelling site-wide |
| rival roots | two Organization nodes, one name, two @ids | corroboration split across two entities | one @id, referenced everywhere |
## Two nodes, one @id: duplicate or collision? #
Before calling anything a collision, count the distinct `@id`s on the live page. Two records sharing an `@id` are one record appearing twice: a template-level block and a page-level block, or the same block read twice. Compare them and they always look like a perfect collision, same phone, same address, same everything, because every field is the same field. A real collision is two records with *different* `@id`s, or none, that claim the same phone number, coordinates or identity.
| Read from the live HTML | Value |
| --- | --- |
| Business nodes | 1 |
| Their @ids | https://example.com/#business |
| Distinct @ids | 1 |
We learned this by getting it wrong. CrawlCheck once reported four collisions on one site, including a shared phone and a shared `@id`, and we wrote it up as a real defect. The live page held one business node; our extraction had read it twice and compared it with itself. The fix was not to ignore shared `@id`s, which would also hide two different businesses handed one identifier by a careless template. One record read twice now counts once, and a site with two genuinely distinct business nodes still reports two. The lesson for anyone auditing markup: verifying that a check fired is not verifying the finding. For any finding that accuses a site, fetch the page and count the nodes by hand.
## The sameAs side #
The same applies to `sameAs` values, with one extra point for Wikidata. A Wikidata link can be written as `https://www.wikidata.org/wiki/Q42`, the human page, or `http://www.wikidata.org/entity/Q42`, the entity IRI. Both are commonly written; only the entity form is the identifier of the thing in Wikidata's own graph. The broader question of whether a `sameAs` target links back is explained in the [entity SEO guide](/guides/what-is-entity-seo).
## How to fix it in one pass #
Choose one `@id` per entity, in fragment form on your [canonical](/glossary/canonical) host: `https://example.com/#organization` for the business, `https://example.com/#website` for the site, `https://example.com/page/#webpage` for pages. Write it identically on every page, NFC-normalised, punycode host, one encoding. Reference it, rather than restating the node, wherever another node needs to point at the business: a `publisher` field that contains `{"@id": "https://example.com/#organization"}` and nothing else is a reference, and the graph merges it with the full node. Which of two rival roots is the real one is a business fact, not a markup fact: decide it, keep that `@id`, and point everything else at it.
## Checking a page by hand #
View the page source, not the rendered DOM, and copy every `<script type="application/ld+json">` block into a JSON parser. List every `@id` with its host, its form (fragment or path) and its `@type`. Any identifier beginning `_:` goes on the [fix list](/glossary/fix-list) at once. For each path-form identifier on your own host, fetch it and note the status; a 404 is a dangling identifier. Sort the remaining list by normalised name and look for the same name under two identifiers, which is the rival-roots case. Then run one more pass over the raw bytes for `%` sequences and for any non-ASCII character in a hostname. The whole pass takes a few minutes on a typical page and finds the defects the vocabulary validators skip, because those tools check that `telephone` is a string and never ask what `@id` points at.
## What this is not #
None of this is a schema.org vocabulary check. A page can pass every vocabulary validator and still have two rival roots and a blank node, and a page can carry a warning about a recommended property and be perfectly identified. For which tool checks what, see [the schema validators comparison](/guides/schema-validators-compared-rich-results-test-vs-schema-markup-validator); for where identifier findings appear in a scan, see the [report guide](/guides/how-to-read-a-crawlcheck-report). Live shares for each finding are on the [dataset page](/data).
Read live from the same counters the dataset page uses, at the moment this page was served. Bars are scaled to the largest value shown, not to 100%.
Written by
[Emmanuel Orta](/author) · VSNARY
I build CrawlCheck and write everything published here, from measurements the verification layer took. Where a post got something wrong, the correction stays in the post.
[Every post, and where I got it wrong →](/author) · [Follow on LinkedIn →](https://www.linkedin.com/in/emmanuelorta)
Share this finding: [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fjson-ld-id-and-iri-errors-what-breaks-and-how-to-fix-them%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fjson-ld-id-and-iri-errors-what-breaks-and-how-to-fix-them%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=JSON-LD%20%40id%20errors%3A%20what%20breaks%20and%20how%20to%20fix%20it)[Email](mailto:?subject=JSON-LD%20%40id%20errors%3A%20what%20breaks%20and%20how%20to%20fix%20it&body=https%3A%2F%2Fcrawlcheck.io%2Fguides%2Fjson-ld-id-and-iri-errors-what-breaks-and-how-to-fix-them)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta)
## Questions this post answers
### What is an @id in JSON-LD?
The IRI that identifies the node as a subject in the graph a consumer builds from the page. Two nodes with the same @id are one node; two nodes with different @ids are two things, whatever their names say.
### Are two JSON-LD nodes with the same @id a collision?
No. Two nodes with one @id are one subject described twice, and their properties merge. A collision is two records with different @ids, or none, that claim the same phone number, coordinates or identity. Count the distinct @ids on the live page before reporting one.
### Is a blank node identifier like _:b0 an error?
It is valid JSON-LD but useless as an identity: it exists only inside that document and cannot be referenced from any other page or from another site's sameAs. Replace it with an IRI on your own domain.
### Should @id use a fragment or a path?
Fragment form, such as https://example.com/#organization, resolves to the page carrying the node and always exists. A path form is a URL that should return something, and one that returns 404 points at nothing.
### What are rival roots?
Two top-level organisation-like nodes on one page with the same name and different @ids: the same business declared as two entities. Corroboration earned by one does not accrue to the other, and a consumer cannot merge them.
### Which Wikidata URL form belongs in sameAs?
The entity form, http://www.wikidata.org/entity/ followed by the item ID, is the identifier of the thing in Wikidata's graph. The /wiki/ form is the human page.
## Related findings
[2026-09-23 How to find broken internal links and dead anchor links on your site A 7-step internal link audit: inventory from your sitemap, check every link, tell broken links from correct errors, and find dead](/guides/how-to-audit-internal-links-and-dead-anchors)[2026-09-16 Brand schema for multi-location businesses: link both ways A parent site listed twelve businesses under its brand; the locations never pointed back. How to declare brand from each location,](/blog/the-parent-declared-the-chain-none-of-the-locations-declared-it-back)[2026-09-01 Dead link or blind spot? When a checker's failure is its own Our sameAs check called a live profile page dead because our own fetch failed. It now reports such targets as unverifiable. How to](/blog/the-scanner-that-cannot-fetch-its-own-host)
The main product
Found this on your own site? **We fix it for $100.**
Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.
[Fix it all — $100](https://buy.stripe.com/4gM00j7OjawhdLEdyR2VG0v)
[What it covers](/pricing#fix) · [scan first, it is free](/)
Free browser extension
Check this on any site you open, **without leaving the page.**
CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.
[Add to Chrome — free](https://chromewebstore.google.com/detail/plgjengobhbdmbgckiiaaflgiepdbcpi?utm_source=crawlcheck.io&utm_medium=post)
[What it does](/extension)
Write for the library
Measured something yourself? **Submit an article.**
Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published.
[Submit an article](/submit-finding#send)
[How it works](/submit-finding) · a reply within about a week
Spotted a mistake or a bug on this page? [Report an error](/report-error?k=article). Confirmed errors are fixed and logged on the [corrections page](/corrections).
## Comments
Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain ([how](/api/comment/signed)). Those appear at once, marked *verified*.
Send for review
Writing about this? [Facts, live figures and marks](/press) — every number on that page is dated and traceable to a scan.
[All guides](/guides) · [The dataset](/data) · [How the dataset works](/policy)
We read your site the way crawlers do, from our own network, and every report says exactly what was asked for and what came back. [Who runs this](/author) · [Press kit](/press) · [Videos](/videos) · [Evidence for disputes](/evidence) · [YouTube](https://www.youtube.com/@crawlcheck) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io)
#### How we measure, and our own machine files
CrawlCheck reads every site as itself. Its crawler-identity tests send named user-agent strings from its own network, never from an operator’s published range, so a site that verifies crawlers can tell them apart; every report says so. Results reflect what an anonymous non-browser client receives. [What we collect and how to opt out](/policy) · [how every report is timestamped](/proof) · [who runs this](/author) · [press kit](/press) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io).
**Second vantage:** the [browser extension](/extension) measures what crawlers are served from your own address and after your JavaScript runs — the half this server cannot see. From 1.0.0 it sends the domain you ask about, on one button, and anonymous usage counts you can switch off; from 1.0.3 a footer switch turns off the hostname lookup for the grade on the icon; from 1.0.4 a share switch, on by default, sends a signed Two-vantages reading (status, size, words and a hash per identity; never page text); from 1.0.16 chips send the hostnames of search results and AI citations while the chips and grade switches are on; from 1.0.17 a readings switch, on by default, sends one signed page reading a day (numbers, the hostname and the page address with the query removed; never in incognito; at most 40 a day) and only while the share and grade switches are also on. Earlier versions send nothing.
**Our own machine layer for the agentic web:** [llms.txt](/llms.txt) · [llms-full.txt](/llms-full.txt) · [agents.md](/agents.md) · [SKILL.md](/SKILL.md) · [entitymap.json](/entitymap.json) · [media kit](/.well-known/media-kit.json) · [MCP server card](/.well-known/mcp/server-card.json) · [API catalog](/.well-known/api-catalog) · [OpenAPI](/openapi.json) · [robots.txt](/robots.txt) · [sitemap.xml](/sitemap.xml) · [security.txt](/.well-known/security.txt) — every one named in robots.txt, which is exactly what we check for on yours.
**Pages:** [/](/) · [Listing check](/listing-check) · [SDK](/sdk) · [Certificates](/certificates) · [Conduct: Duckduckbot](/agents/conduct/duckduckbot) | **Blog:** [Six in ten websites already use post-quantum encryption. Whether yours does mostly depends on one thing](/blog/post-quantum-key-exchange-six-in-ten-websites-november-2026) | **Glossary:** [E-E-A-T](/glossary/e-e-a-t) · [Normalized discounted cumulative gain](/glossary/normalized-discounted-cumulative-gain) · [Search intent](/glossary/search-intent) · [Data exfiltration](/glossary/data-exfiltration) · [canonical origin](/glossary/canonical-origin) · [HTTP/3](/glossary/http-3)
[Contact](/contact) · [Partnerships](/partnerships) · [Terms of service](/terms) · [Refund policy](/refunds) · [Trust center](/trust) · [Subprocessors](/subprocessors) · [Changelog](/changelog) · [Report an error](/report-error)
Same body as a file: /guides/json-ld-id-and-iri-errors-what-breaks-and-how-to-fix-them.md · as data: /feed.json · what we tell agents site-wide: /llms.txt, /agents.md. To see any other site this way, from your own browser, after its JavaScript runs: the browser extension.