Why Breadcrumb Schema Errors Make Rich Results Disappear
Key takeawayBreadcrumbList structured data displays the hierarchical path from the homepage to the current page in search results. The markup itself is simple, but several field-level details (the @id format, position ordering, itemListElement nesting) are counter-intuitive, and getting them wrong makes the entire rich result vanish.
When this applies
- Sites with multi-level page paths that want breadcrumbs shown in search results
- Sites reporting errors in structured data validation tools
- Sites where breadcrumbs render fine on the page but never appear as rich results
- Sites using JSON-LD for structured data
| Error point | Incorrect markup | Consequence | Correct approach |
|---|---|---|---|
| item missing @id | Only name and url are provided | Rich result is not generated | Give each item both @id and name |
| Intermediate pages not marked | Only the deepest level is marked | The hierarchy chain is broken | Mark every level individually |
| Last level points to itself with a different URL | URL written with query parameters | The chain does not close | Use the canonical address |
| position ordering wrong | Ordered from deep to shallow | Display order is inverted | position starts at 1 and increases with depth |
| Items that are not part of the path | Search result pages included as a level | Semantics do not match | Keep only real path levels |
| Microdata with a broken hierarchy | itemprop nesting is interrupted | Parsing fails | Prefer JSON-LD |
Step-by-step diagnosis
- Check the Structured Data report in GSC for specific error messages and the affected URLs.
- Validate the markup with the Rich Results Test to see whether it parses correctly.
- Verify that every breadcrumb item includes @id, name, and item (item is only needed for clickable levels).
- Confirm that position starts at 1, increases with path depth, and neither repeats nor skips values.
- Check that the chain is complete: homepage → category → subcategory → current page, with a real page marked at every level.
- Verify the last level points to the current page's canonical URL (consistent with the canonical tag).
- After fixing, request recrawling in GSC and wait for re-evaluation.
Common mistakes
- Treating the schema as an on-page navigation element — the markup and the visible breadcrumb navigation are separate things.
- Adding a single annotation for the current page and expecting search engines to reconstruct the hierarchy.
- Writing name without @id on items — the most common reason the rich result is not generated.
- Adding filter parameters to URLs in the chain, introducing non-canonical addresses.
- Pointing breadcrumb markup at paginated URLs on paginated listing pages.
FAQ
Does breadcrumb markup affect rankings?
Not directly. Its main value is rich result display and click-through rate in search results, which indirectly affects clicks and downstream behavior signals.
Does every level need its own annotation?
Yes. The correct BreadcrumbList structure has one ListItem per level, nested via itemListElement to express hierarchy rather than listed side by side.
Should a site without visible breadcrumbs add the markup?
No. Structured data must describe content that is genuinely visible on the page; marking up content that does not exist is a violation.
Version notes2026-11-20: first release, compiled from official Google documentation and public technical sources; updated as engine rules change. Engine behaviour details follow the latest official Google documentation.
Related reading
Why Google Does Not Index Infinite Scroll Product Lists — and the FixesCommon hreflang Errors on Multilingual Sites: The Full ListCanonical Tag Conflicts Causing Duplicate Indexing: How to Fix ThemXML Sitemap Errors: Types and Fixes ComparedOn-Site Duplicate Content: Judgment Criteria and a Prevention ChecklistNote: this page is a summary of publicly documented search-engine rules and is for self-check reference only. Engine behaviour is subject to the latest official Google documentation; verify against your own Search Console data.