Breadcrumb schema errors in item and position fields
Fix BreadcrumbList errors by matching the visible trail to ordered ListItem entries, valid destination URLs, and the final page after a category change.
By Crawlito · 5 min read
In short
- Each breadcrumb trail needs a coherent ordered sequence of ListItem entries.
- Google permits the final breadcrumb to omit item and use the containing page's URL.
- A valid JSON structure can still describe a category hierarchy that no longer exists.
On this page
- Locate the trail the error actually describes
- Check positions and destinations together
- Trace errors caused by optional categories
- Verify localization and alternate paths
- Test the template after a real data change
- Catch a category deleted after publication
- Frequently asked questions
- Check a page with a category change
When a breadcrumb report flags item or position, inspect the full BreadcrumbList emitted by the affected template and compare it with the visible navigation. Check the order, labels, destination URLs, and handling of the final entry. Repair the generator or category data that produced the mismatch, then test another page using the same template. Google’s breadcrumb structured data reference
Locate the trail the error actually describes
Open the exact URL from the report and save the generated HTML. Search every structured data block for BreadcrumbList. A theme, SEO plugin, and manually inserted snippet can each emit a trail. The reported error may refer to an older duplicate even when the visible breadcrumb and one valid graph look correct.
Identify each trail by its labels and destinations. A product can appear in several categories, and a site may legitimately describe more than one useful path. Treat each list as a complete sequence. Combining the beginning of one hierarchy with the ending of another creates a path that nobody can follow through the website.
Compare the report's observation date with the release that changed the category structure. An old error can describe a previous version of the page. Use a current live test to inspect today's output and retain the earlier sample as evidence of the defect you intended to fix. The JSON-LD troubleshooting guide explains how to identify repeated graph nodes.
Check positions and destinations together
A trail needs ordered items that correspond to the intended navigation. Use integer positions beginning at the start of the trail and progressing consistently. Read the values after serialization; a template can accidentally emit a localized label or an empty string in the position field when a content record is incomplete.
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Repair guides",
"item": "https://example.com/repairs"
},
{
"@type": "ListItem",
"position": 2,
"name": "Lantern maintenance"
}
]
}This example shows a fictional two-step trail. Google's documentation permits the last item to omit its destination, in which case the containing page supplies the URL. Intermediate entries need the appropriate destination under the documented rules. A validator warning about a nonfinal category therefore deserves different attention from a final entry intentionally using the supported omission.
Click each intermediate destination. A syntactically valid URL can redirect to an unrelated category or return a generic error page. A trail labeled “Repair guides” that opens the store checkout is a content mapping problem. The breadcrumb navigation guide explains how to choose a hierarchy people can use.
Trace errors caused by optional categories
Many failures appear only on pages with an empty parent category or a recently changed hierarchy. Suppose a generator builds four entries, removes a missing category, and leaves position values of 1, 3, and 4. Another implementation might retain the empty entry with a missing name or destination. Build the final logical trail first and assign its positions after the intended entries are known.
Choose a page with a complete hierarchy, one with an intentionally shallow hierarchy, and one affected by the recent category change. Compare their source records and generated trails. If only the shallow page fails, investigate assumptions about a mandatory parent. If all category changes fail, inspect whether the generator reads a stale path or an old cached parent relationship.
| Observed output | Likely place to inspect |
|---|---|
| Empty name on one category entry | Category display-name record or locale fallback |
| Same position on several items | Loop state or merged trail fragments |
| Old destination after a category rename | Stored path or cache invalidation |
| Two conflicting lists | Theme and plugin ownership |
| Final item points at another product | Shared template context or reused content object |
Keep the diagnosis tied to the actual output. Adding another hand-written valid breadcrumb block can make a test show success while leaving the defective block in place. Correct or remove the component that owns the invalid duplicate through the site's normal configuration.
Verify localization and alternate paths
A localized page can use a translated category label but accidentally link to the default language. Test the trail from a direct visit with no remembered language preference. The link should have the purpose the visible label implies and fit the publication's locale routing policy. A browser's automatic redirection can conceal a mismatched destination in a casual check.
If a page has two meaningful category paths, inspect each complete list independently and verify both routes on the site. A product under “Lighting” and “Camping equipment” may have two valid paths. A category generated only by a search filter may have a less stable role. Decide which trails actually help someone navigate before emitting every possible classification.
Check the page's canonical identity too. A collection-specific product path might declare a canonical at the main product URL. The breadcrumb should describe an understandable path to the actual item, while canonical handling follows the site's duplicate policy. The canonical guide helps separate those responsibilities without making the trail contradict the public page.
Test the template after a real data change
Run the affected public URL through the current rich-result testing tool and inspect every breadcrumb item it recognizes. Confirm the absence of the original error, then click the destinations as a visitor. Include the shallow and localized examples in the same acceptance set.
Make a category change in a preview or fixture and regenerate the page. Check that the displayed labels, structured labels, destination paths, and positions all move together. Returning the category to its prior value should also restore a coherent trail. This exercise catches a one-time repair that updates the currently broken row but leaves the generator unable to handle the next edit.
Record the page, category identifiers, corrected output, and release time. Follow the corresponding Search Console report separately as it refreshes. A clean live test shows what you publish now, while the report can still include an earlier crawl. Preserve that distinction when handing the task to an editor who monitors the search appearance.
Catch a category deleted after publication
Suppose an editor removes a seasonal category while several products still reference its identifier. The breadcrumb generator may receive a valid product and an unresolved parent, then serialize an empty entry. Reproduce this in a preview with one product assigned to that category and another assigned to a retained category. Inspect the final trail after the deletion, including any fallback parent the editor selects.
The repair should define what happens to that orphaned relationship in the content model. It may require assigning a maintained category or deliberately using a shallower trail. Confirm that the visible navigation and structured list use the same decision. Then restore or recreate a category and test a new assignment. This checks that both deletion and ordinary editing produce a usable path.
Frequently asked questions
Is item required on the final breadcrumb?
Google documents an exception for the last entry. Inspect whether the error refers to that entry or to an intermediate category that needs a destination.
Can two breadcrumb trails be valid on one page?
They can describe different useful paths. Keep each list complete, ordered, and accurate for the page it accompanies.
Does the URL path have to match every breadcrumb label?
A useful hierarchy can differ from the literal URL segments. Verify that the labels and links still form a real navigational path.
Check a page with a category change
Run the free page check on the affected URL and compare its structure with the breadcrumb validator's output. Follow the category links to complete the navigation test.
Filed under Structure and schema. Topics: structured-data, breadcrumbs, google