Breadcrumb Structured Data Issues: How to Fix Them

What the breadcrumb report is telling you

A breadcrumb trail shows where a page sits in your site, such as Home › Garden Tools › Pruning Shears. BreadcrumbList markup describes the same trail in a form search engines can read. Google uses it to understand your site structure and, on desktop results, can show the trail in place of the raw URL. Since early 2025 Google shows only the site name and domain on mobile results, so the visible benefit is mainly on desktop, but the structural signal applies everywhere.

When Google finds BreadcrumbList markup, it adds the page to the Breadcrumbs report under Enhancements in Search Console. Each issue is listed as an error, which makes the item invalid, or a warning, which leaves it valid but incomplete. Common messages include:

Open each message to see example URLs. Because breadcrumbs come from a template, the examples usually share a page type, which tells you where to look.

The correct shape of BreadcrumbList markup

A BreadcrumbList holds an itemListElement array of ListItem entries. Each entry has a position starting at 1, a name, and an item with the full URL of that level. The last entry is the current page and may leave out item.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {"@type": "ListItem", "position": 1, "name": "Home",
     "item": "https://example.com/"},
    {"@type": "ListItem", "position": 2, "name": "Garden Tools",
     "item": "https://example.com/garden-tools/"},
    {"@type": "ListItem", "position": 3, "name": "Pruning Shears"}
  ]
}
</script>

The same trail in microdata, if your theme prints the visible breadcrumb with markup attached:

<ol itemscope itemtype="https://schema.org/BreadcrumbList">
  <li itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
    <a itemprop="item" href="https://example.com/"><span itemprop="name">Home</span></a>
    <meta itemprop="position" content="1">
  </li>
  <li itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
    <a itemprop="item" href="https://example.com/garden-tools/"><span itemprop="name">Garden Tools</span></a>
    <meta itemprop="position" content="2">
  </li>
  <li itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
    <span itemprop="name">Pruning Shears</span>
    <meta itemprop="position" content="3">
  </li>
</ol>

Use one format, not both. JSON-LD is easier to keep correct because it sits apart from the visible HTML.

The common causes

The first cause is by far the most common. It happens when a category exists in your product data but has no category page, or when the theme prints a level as plain text. Either give the level a real page or leave it out of both the visible trail and the markup.

How to diagnose the problem

Take an example URL from the report and run it through the Rich Results Test. It shows each breadcrumb item it found, with the levels listed and any error on the level that causes it. If two Breadcrumbs items appear, you have duplicate markup.

To see exactly what the page prints, paste this into the DevTools console. It lists every trail, in both JSON-LD and microdata, with the positions, names and URLs:

document.querySelectorAll('script[type="application/ld+json"]').forEach(s => {
  const walk = o => {
    if (!o || typeof o !== 'object') return;
    if (o['@type'] === 'BreadcrumbList') console.table(o.itemListElement.map(i =>
      ({ position: i.position, name: i.name, item: typeof i.item === 'object' ? i.item['@id'] : i.item })));
    Object.values(o).forEach(walk);
  };
  try { walk(JSON.parse(s.textContent)); } catch (e) { console.log('Unparsable block', e.message); }
});
console.log('Microdata trails:', document.querySelectorAll('[itemtype$="BreadcrumbList"]').length);

Check the table for a gap in positions, an empty name or a missing URL on any level except the last. Then check each URL returns 200 directly, not a redirect:

curl -sS -o /dev/null -w "%{http_code} %{url_effective}\n" https://example.com/garden-tools/

If the markup is broken JSON, the console script reports it; fix that first with the structured data syntax errors guide. The schema debugger runs the same checks and flags each failing level.

Platform notes

• WordPress. Yoast SEO and Rank Math each output BreadcrumbList as part of their page graph, and many themes print their own microdata trail too. Choose one: switch off the theme's breadcrumbs or the plugin's, and use the plugin's breadcrumb block or shortcode for the visible trail so both come from the same data. With WooCommerce, check that its own breadcrumb output is not adding a second trail. See debugging schema in WordPress.
• Shopify. Many themes have no breadcrumb at all, and an app or theme snippet adds it. Collection paths are the usual trouble: a product reached from several collections can print different trails. Build the trail from one canonical collection. See debugging schema in Shopify.
• Next.js and headless sites. Generate the JSON-LD from the same route data that renders the visible breadcrumb component, on the server, and build absolute URLs from a single site URL setting rather than the request host.
• Static sites. Use a partial or include that takes the trail as data, so you edit one file rather than every page.

A worked example

A garden shop's Breadcrumbs report shows 1,200 items with Missing field "item". The Rich Results Test on a product page shows four levels: Home, Tools, Garden Tools and Pruning Shears. The error sits on level 2, Tools.

The shop's categories have a parent called Tools with no page of its own; it exists only to group menus. The theme prints it in the visible trail as plain text, and the markup template prints it with an empty URL. The owner has two choices: create a real Tools category page, or drop that level. They drop it from both the visible trail and the markup, which now read Home, Garden Tools, Pruning Shears with positions 1, 2 and 3. A second trail from the theme's microdata is switched off at the same time. After testing a deep product and a product with a long name, the owner validates the fix, and the report's error count falls over the next fortnight.

The fix, step by step

Edge cases worth knowing

• Several genuine paths. A product that really sits in two sections can carry two BreadcrumbList trails, and Google supports that. Two trails are a problem only when they disagree by accident.
• The home page. A trail with only one level, the home page itself, adds nothing. Leave breadcrumb markup off the home page.
• Item as an object. item can be a URL string or an object with an @id URL and its own name. Both are valid; mixing them within one trail is allowed but harder to maintain.
• Trailing slashes and parameters. Use the canonical form of each URL, matching your trailing slash policy, and never include tracking or filter parameters.
• Hidden breadcrumbs. Marking up a trail that visitors cannot see goes against Google's guidelines. Keep a visible trail on every page that carries the markup.

Keeping breadcrumbs correct

Breadcrumb markup drifts when the visible trail and the markup are built from different data. The lasting fix is to generate both from the same source.

• Print the visible trail and the JSON-LD from one function or component, fed by one list of levels.
• Build URLs from a single site address setting so every item is absolute and on the canonical host.
• Keep one breadcrumb generator; after theme or plugin updates, check one page of each type still shows a single trail.
• When you restructure categories, retest a deep page in the Rich Results Test before and after.
• Check the Breadcrumbs report monthly. A sudden jump in errors usually follows a change you can name.

To see how breadcrumbs appear in search, see breadcrumbs in search results.