A breadcrumb trail has inconsistent structure
In the reportBreadcrumbList structure is invalid
structured_data_breadcrumb_invalid_structure · Issue
A captured breadcrumb trail has invalid positions, missing non-final fields or conflicting declarations of the same trail.
Severity: Low. Correct the breadcrumb markup when updating the page.
Why it matters
Consistent positions and labels help consumers interpret the intended navigation trail.
What to do
- Compare the recorded positions with the expected contiguous sequence 1–n.
- Give each non-final element a name and item URL. A named item Thing can supply its name.
- Reconcile conflicting declarations of the same trail identity while retaining legitimate alternative navigation trails.
When to leave it as it is: Keep multiple valid alternative trails. They do not become errors merely because their paths differ. The final element may omit its item URL; Google uses the containing page’s URL.
What we read
We read the page’s captured HTML and its JSON-LD, Microdata and RDFa declarations without executing JavaScript or fetching remote contexts or linked targets. Findings retain the original declarations and source byte positions.
Missing or ambiguous data is not checked and cannot confirm a correction. A definite error can still be reported when another part of the same page remains unknown.
We compare ListItem positions and captured name/item values. An unresolved reference, ambiguous field or empty declared trail cannot provide clean evidence.
Conflicting trails require the same declared IRI identity. Unidentified alternative labels do not prove a conflict.
The site’s URL-path shape and the target’s HTTP status are separate checks.
Example & evidence
Illustrative correction; this is not a live audit.
"itemListElement": [{"position": 1, "name": "Books", "item": "https://shop.example/books"}, {"position": 3, "name": "Lamp"}]"itemListElement": [{"position": 1, "name": "Books", "item": "https://shop.example/books"}, {"position": 2, "name": "Lamp"}]Confirm & check again
Check for yourself: Compare the reported property with the HTML served at this URL. Validate the corrected markup with the appropriate structured-data test.
Check again: Full audit — Run another full site audit. A correction is confirmed only for the same page with sufficient captured coverage and no remaining violation. Missing coverage does not close the finding.
Limits & sources
This is a captured structure check, not proof of indexing or breadcrumb display.
Blank-node references whose scope cannot be established, unsupported fields and positions outside the supported integer range remain not checked.
Confidence: High The finding preserves an exact captured structural or value conflict with source evidence. It does not establish Google indexing, ranking or rich-result display.
Sources
- Google, Breadcrumb structured data — Documents positions, name/item requirements, the final item exception and multiple alternative trails. Checked 3 October 2026.
Editorial review: 2 November 2026