🤖NEW:AI-Powered Incremental Builds — your site updates in under 30 seconds. See what's new →
← All Tools
100% Free • Breadcrumb Schema Builder

Breadcrumb Schema Generator

Build valid BreadcrumbList Schema.org JSON-LD markup to display clean website hierarchy breadcrumbs in Google Search results.

Breadcrumb Steps (3)

Position #1
Position #2
Position #3

Generated JSON-LD Code

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://example.com"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Category",
      "item": "https://example.com/category"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Current Page",
      "item": "https://example.com/category/page"
    }
  ]
}
</script>
Technical Deep-Dive

BreadcrumbList Schema.org Guidelines & Search Hierarchy

Last updated: August 2026 • Reviewed by Nimbica Technical SEO Team

2. Formatting ListItem Positions & URLs

Each entry in the itemListElement array needs a ListItem type, an integer position starting at 1 (not 0), a human-readable name, and an absolute (not relative) item URL. A common mistake is using relative paths like /category/page instead of the full https://example.com/category/page — Google's parser expects fully-qualified URLs, and a relative path can cause the entire markup to be rejected or ignored. This tool's generator handles that formatting for you, but if you're editing the output manually, double-check every URL is absolute.

3. Combining Breadcrumbs with FAQPage & HowTo Schema

A single page can carry multiple structured data types simultaneously — a product page might have BreadcrumbList alongside Product schema, or an article might combine BreadcrumbList with FAQPage schema if it includes an FAQ section. Each schema type is added as its own separate JSON-LD script block; they don't need to be merged into one object. If your page has a genuine FAQ section, generate matching markup with the FAQPage Schema Generator.

4. Where Static Delivery Fits In

Nimbica pre-renders WordPress pages, including any JSON-LD schema blocks they output, into static HTML served from edge locations — meaning crawlers reading the structured data get a fast, consistent response rather than waiting on dynamic PHP rendering for each request. This affects delivery speed only; it doesn't validate or generate the schema itself, which still needs to be correctly authored (by this tool, a plugin, or manually) before it's meaningful to search engines.

5. How to Use This Generator

  1. Add a step for each level of your page's actual navigation hierarchy, from the homepage down to the current page.
  2. Use real, absolute URLs for each step — the tool won't catch a typo in a URL that happens to still be syntactically valid.
  3. Copy the generated code and paste it into your page's HTML — a theme template, a custom fields plugin, or your SEO plugin's custom schema field.
  4. Validate the live page afterward with Google's Rich Results Test to confirm the markup was picked up correctly once deployed.

6. Common Mistakes

  • Using relative instead of absolute URLs. Every item URL needs the full domain — a common copy-paste error when adapting markup between environments.
  • A breadcrumb hierarchy that doesn't match the visible page. If your on-page breadcrumb shows Home > Blog > Post but the schema describes Home > Category > Post, the mismatch can undermine trust in the markup's accuracy.
  • Forgetting to update schema after restructuring site navigation. If a category gets renamed or the URL structure changes, stale breadcrumb schema left behind describes a hierarchy that no longer exists.

7. Limitations

This tool generates syntactically valid JSON-LD from the steps you enter — it doesn't verify those steps match your site's actual navigation structure or that the URLs you enter are real, live pages. Adding valid schema doesn't guarantee Google will display breadcrumbs in search results; that decision is made algorithmically per Google's own stated policy, independent of markup validity.

Pre-render structured data with Nimbica Static Edge

Transform dynamic PHP rendering bottlenecks into ultra-fast static HTML deployed across 300+ global edge locations.

Frequently Asked Questions

What is BreadcrumbList Schema.org markup?

BreadcrumbList structured data describes a page's position within a site's navigational hierarchy — Home > Category > Product, for example. When Google can parse this markup, it can render the breadcrumb trail directly in the search snippet instead of a raw URL, giving searchers immediate context about where a page sits in your site before they even click.

Should the current page be included in the BreadcrumbList schema?

Yes — Google's structured data guidelines include the current page as the final ListItem in the array. Some implementations omit the URL for the final item (since a page technically doesn't need to link to itself), but the item itself, with its position and name, should be present.

Where should I paste the generated JSON-LD code?

Paste the generated script tag anywhere in your page's HTML — commonly the <head>, though JSON-LD is valid anywhere in the document since it's not rendered visually and search engines parse it regardless of placement. On WordPress, this typically means a theme template edit, a custom fields/schema plugin, or your SEO plugin's custom schema field if it supports one.

Do I still need visible breadcrumb navigation on the page if I add this schema?

Yes — this generates only the structured data, not the visible on-page breadcrumb trail your visitors see and click through. Google's guidelines expect the schema to reflect real page structure, and having matching visible breadcrumbs is both better practice for the reasons breadcrumbs help usability in the first place, and reduces the risk of the schema being flagged as not matching visible content.