Breadcrumb Schema Generator

Generate BreadcrumbList JSON-LD markup for your website's breadcrumb navigation. Positions auto-assign based on row order. Copy as JSON or HTML <script> tag.

Breadcrumb Items 0 items

Add each breadcrumb level in order. The Home page is usually position 1. URLs must be absolute (starting with http:// or https://). Use the ↑/↓ buttons to reorder items.

Schema Output

// Add breadcrumb items above to generate schema
// Add breadcrumb items above to generate schema

Breadcrumb Preview

This is how your breadcrumb trail will appear to users. The last item is styled as the current page.

What Is Breadcrumb Schema?

BreadcrumbList schema is a structured data format that tells Google and other search engines about the navigation path to a specific page on your website. When eligible, search engines may use it to display a cleaner breadcrumb path instead of a plain URL, such as:

Home > Blog > SEO Tips > How to Optimize Title Tags

Breadcrumbs help users understand your site structure and can make search listings more understandable when search engines choose to display breadcrumb paths.

Why Breadcrumb Schema Matters for SEO

Clearer Listings

Rich breadcrumb results stand out in SERPs with a clear navigation path, attracting more clicks than plain URL results.

Better UX

Breadcrumbs show users exactly where they are in your site hierarchy, reducing bounce rates and improving navigation.

Indexing Signals

Breadcrumb schema helps Google understand your site's information architecture and page relationships.

Best Practices for Breadcrumb Schema

  • Start with Home — Position 1 should always point to your homepage (https://www.example.com/).
  • Use absolute URLs — Every breadcrumb URL must be a full absolute URL starting with https:// or http://.
  • Unique positions — Each item must have a unique position number, starting at 1 and incrementing by 1.
  • Last item = current page — The final breadcrumb should point to the current page URL.
  • Match actual navigation — Breadcrumbs should reflect the real navigation structure of your site, not just keywords you want to rank for.
  • Keep labels concise — Use short, descriptive labels that users can scan quickly (1–3 words each).
  • Test your markup — Use Google's Rich Results Test to validate your breadcrumb schema after implementation.

How to Implement Breadcrumb Schema

  1. Generate your schema using the tool above — add each breadcrumb level in order from Home to the current page.
  2. Copy the JSON-LD output (or use the HTML <script> tab for the ready-to-paste code).
  3. Paste the code into your page's <head> or just before the closing </body> tag.
  4. Verify your implementation using Google's Rich Results Test or Schema.org validator.

Frequently Asked Questions

Use breadcrumb schema on pages that have a visible breadcrumb trail and a clear hierarchy. Google can use this data to understand and sometimes display breadcrumb paths in search results, but it does not guarantee a specific display or click-through lift.
Most pages work well with 2–5 breadcrumb items. The most common pattern is Home > Category > Subcategory > Page. Google recommends keeping breadcrumb trails short and meaningful — avoid excessively deep hierarchies (more than 6-7 levels).
No, breadcrumb schema requires absolute URLs. Each item field must contain a fully qualified URL starting with https:// or http://. Relative URLs like /category/page/ will not work correctly and may cause validation errors in Google's Rich Results Test.
Visible breadcrumbs are the navigation trail users see on your website (usually styled with CSS). Schema breadcrumbs are JSON-LD structured data that search engines read. You should have both — the visible breadcrumbs for users, and the schema markup for search engines. They should match each other.
Breadcrumb schema is not a direct ranking factor and should not be presented as a CTR or ranking guarantee. Its practical value is helping search engines understand page hierarchy and, when eligible, display breadcrumb paths instead of long URLs.
No, each page should have exactly one BreadcrumbList schema with the full navigation path. Having multiple breadcrumb schemas on the same page can confuse search engines and may result in none of them being displayed in rich results. Stick to one coherent breadcrumb trail per page.
Google advises that breadcrumb schema should reflect the actual visible breadcrumb navigation on the page. Mismatches between the schema markup and visible content can be seen as misleading and may lead to manual actions or rich result demotion. Always ensure your schema matches what users see.
Yes — the final breadcrumb in your list should point to the current page URL and use the page title as its label. This gives users and search engines a complete path showing exactly where they are. Omitting the current page leaves the breadcrumb trail incomplete.
For SPAs built with React, Vue, or Angular, inject the JSON-LD dynamically when routes change. Use a library like react-helmet or update the <script> tag via JavaScript on route transitions. Make sure search engines can crawl your breadcrumb schema by rendering it server-side or using SSR/SSG.