Breadcrumb markup

What this check looks for

This check applies to any page that isn't the homepage (page type isn't "home" and crawl depth is greater than zero). If the page declares a BreadcrumbList block, it passes. If it has structured data but no BreadcrumbList, it warns, reporting the types that were found instead. Homepages report "na", since breadcrumbs aren't expected there; pages without structured data extracted also report "na".

Why it matters

BreadcrumbList markup is what lets Google replace the raw URL in a search result with a readable path (Home › Audio › Headphones), which makes the listing easier to scan and gives searchers a clearer sense of where the page sits in your site before they even click. It's also a lightweight but genuine site-structure signal: it tells a crawler explicitly how this page relates to the categories above it, reinforcing the same hierarchy your internal linking implies. AI systems building a mental model of a site's structure use the same breadcrumb data to understand a page's place in a broader topic, which helps with disambiguating similarly-named pages across categories.

How to fix it

Add BreadcrumbList JSON-LD reflecting the page's actual position in the site hierarchy:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.acme.com/" },
    { "@type": "ListItem", "position": 2, "name": "Audio", "item": "https://www.acme.com/audio" },
    { "@type": "ListItem", "position": 3, "name": "Headphones", "item": "https://www.acme.com/audio/headphones" }
  ]
}
</script>

Keep this markup consistent with any visible breadcrumb UI on the page — mismatched visible and structured breadcrumbs can look like an attempt to mislead crawlers.