Implement valid BreadcrumbList schema

Rule Details

Breadcrumbs provide a secondary navigation path for users and a clear hierarchical map for search engines.

Code Example

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [{
    "@type": "ListItem",
    "position": 1,
    "name": "Blog",
    "item": "https://example.com/blog"
  },{
    "@type": "ListItem",
    "position": 2,
    "name": "SEO Tips",
    "item": "https://example.com/blog/seo-tips"
  }]
}
</script>

Why It Matters

• Search Appearance: Replaces long, messy URLs in search snippets with a clean, clickable navigation path.
• Crawlability: Helps search engines understand the relationship between different pages and categories.
• User Experience: Allows users to quickly navigate back to higher-level categories or the homepage.
• Internal Linking: Automatically creates a strong internal linking structure based on your site's hierarchy.

Exceptions

• Only add or enforce schema types that the page can truthfully support; irrelevant structured data is worse than no structured data.
• A technically valid schema block can still be misleading if the page content does not visibly back it up; audit rendered content and schema together.
• If indexability, canonical-url, or main content quality is wrong, fix that foundation before optimizing schema details.

Standards

• Use these references as the standard for the final search-facing HTML, metadata, and crawl behavior.
• Check the implementation against Google Search Central: Search Essentials before treating the rule as satisfied.
• Check the implementation against Google Search Central documentation before treating the rule as satisfied.

Verification

Automated Checks

• Inspect rendered HTML and HTTP headers to confirm the expected metadata or crawlability signal is present.
• Test the affected URL with Google Search Console or equivalent tooling where relevant.
• Re-crawl a representative page set after deployment.

Manual Checks

• Confirm the change does not create conflicting canonical-url, robots, or structured-data signals.