BreadcrumbList Schema

What is BreadcrumbList Schema?

BreadcrumbList¹ is the schema.org JSON-LD type that declares the hierarchical path from a site's root to the current page. It is a flat ordered list of ListItem entries, each with a position, a display name, and (usually) a URL. The list powers Google's breadcrumb rich result in the SERP and provides what practitioners hypothesize AI search engines use to infer where a page sits in a site's topical structure (observed behavior, not vendor-documented).

Minimum viable BreadcrumbList payload

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/" },
    { "@type": "ListItem", "position": 2, "name": "Guides", "item": "https://example.com/guides/" },
    { "@type": "ListItem", "position": 3, "name": "Schema-first SEO" }
  ]
}

Position is 1-indexed. The final ListItem can omit item because it refers to the current page². A single page can declare multiple BreadcrumbList objects if it is legitimately reachable through more than one navigation path (a tutorial reached from both /guides/ and /topics/seo/, for example).

Status in 2026

Mature and broadly expected. BreadcrumbList has been Google's canonical breadcrumb signal since the mid-2010s schema.org transition and is now commonly generated automatically by mainstream CMSes and static-site frameworks: WordPress (via Yoast or Rank Math plugins), Hugo, Next.js (via metadata API and manual page hierarchy), Astro, Drupal². Some frameworks generate it from URL paths; others require explicit page-hierarchy declaration. Its weight in 2026 has grown beyond classical SERP cosmetics: AI search engines appear to use the path to infer a page's topical neighborhood, which in turn shapes whether the page is cited for parent-topic queries or only for the leaf-topic query (observed behavior, not vendor-documented). Pages without breadcrumb schema can still be indexed and cited. Practitioners report that breadcrumb-less pages tend to surface for narrower, leaf-topic query matches more often than for parent-topic queries, consistent with the hypothesis that engines use breadcrumb-derived hierarchy as a topical-neighborhood signal. The causal relationship has not been isolated by public study; pages without breadcrumb schema but with strong on-page topical signals (clear H1, descriptive title, internal linking) often perform comparably.

A worthwhile counterweight: Google's own breadcrumb structured-data documentation explicitly states that rich-result display is not guaranteed even with valid markup; visibility depends on query, page authority, and competing rich-result candidates. Independent SEO consultant Jono Alderson argued more broadly in a November 2024 piece that schema markup may be "just labels and connections," not a citation-amplifying power³. Ship BreadcrumbList for SERP eligibility and clean machine-readability, not as a guaranteed AI citation lever.

Note on this entry's territory (paired with the FAQ schema, HowTo schema, answer block, DefinedTerm schema, and JSON-LD entries as schema cluster siblings): BreadcrumbList as a schema.org type is vendor-canonical. Schema.org maintains the vocabulary, and Google Search Central documents the breadcrumb rich result. The application to AI search engine citation (whether breadcrumb-derived hierarchy actually influences citation selection) is non-vendor-canonical because none of the major AI engines publish their hierarchy-based weighting. The content-side application (mirroring visible breadcrumb trails, using absolute URLs, shipping one list per legitimate path) sits in practitioner-discipline territory: writers can directly verify schema validity via Google's Rich Results Tester or schema.org's validator without needing vendor-confirmed citation mechanisms. Paired with the other schema cluster anchors: each declares a different facet of a page; BreadcrumbList declares hierarchical position, which is the schema cluster's spatial / contextual dimension.

How to apply

BreadcrumbList is a 10-line schema that most teams ship once and never touch again. The three places where implementations go wrong:

• Mirror the visible breadcrumb trail, not the URL path: if your visible breadcrumb reads Home › Guides › Schema-first SEO but your URL path is /2026/05/schema-post, the BreadcrumbList should follow the visible trail (the user's mental model), not the URL slug fragments. Practitioners report that AI engines appear to align citations to the visible breadcrumb path when it diverges from URL slugs (observed behavior, not vendor-documented).
• Use absolute URLs for item: relative URLs validate as schema but confuse cross-domain consumers. Always emit fully qualified https://example.com/... URLs. The cost is zero; the ambiguity removed is non-trivial.
• Ship one BreadcrumbList per legitimate path, not duplicates of the same path: declaring the same trail twice does not help ranking and may trigger rich-result suppression on strict validators. Multiple lists are for pages with multiple legitimate parents (categories + tags), not for redundancy.

What to skip: hand-maintaining BreadcrumbList in HTML when your framework already generates it. The maintenance overhead vastly outweighs any control benefit.

How it relates to other concepts

• Sibling of Article schema and FAQ schema: each declares a different facet of a page (editorial metadata, Q-and-A blocks, hierarchical position). Most content pages ship all three together.
• Sibling of DefinedTerm schema on glossary sites: a term page typically carries DefinedTerm for the term itself plus BreadcrumbList for the path back to the glossary index.
• A useful technical hygiene layer for GEO because it clarifies site hierarchy. Breadcrumbs may help engines answer "what is this page about at the next level up," but they do not determine citation eligibility on their own; eligibility depends on content quality, page authority, query fit, and many signals beyond schema syntax.