BreadcrumbList Schema Generator

Why BreadcrumbList Schema Matters

BreadcrumbList schema serves two functions: it replaces raw URLs with readable page paths in Google search results, and it gives AI engines a map of your site's topical structure.

Every page gets its own breadcrumb: Generate a separate BreadcrumbList for each page, reflecting that page's actual position in the hierarchy.
Always start with homepage: The first ListItem should always be your homepage with position 1.
Final item = current page: The last breadcrumb item should be the page the schema is on. The URL in the last item should match the page's canonical URL.
Topical authority signal: AI engines use breadcrumb paths to infer topical authority. A page at /seo/technical-seo/ signals deeper expertise than a page at /article-about-seo/.

Frequently Asked Questions

How many items should a breadcrumb have? ⌄

Most pages need 2–4 breadcrumb items. A flat site (homepage → page) needs 2. A blog post (homepage → category → post) needs 3. A deeply nested page (homepage → section → subsection → page) needs 4. Avoid creating artificial depth: only add levels that genuinely exist in your URL structure and navigation.

Should breadcrumb schema match visible breadcrumbs on the page? ⌄

Yes. Google's guidelines require that the breadcrumb path in the JSON-LD matches the visible breadcrumb navigation displayed on the page. If they don't match, Google may ignore the schema or issue a Manual Action. Always keep the schema and visible breadcrumbs in sync.

Does the last breadcrumb item need a URL? ⌄

Technically the last item's URL is optional (the current page URL is implied). However, it is best practice to include it. Providing the full URL makes the schema self-contained and easier for parsers to validate. Use the canonical URL of the current page.