Skip to main content
7BBusyBoss

BreadcrumbList JSON-LD Generator — Rich-Result Breadcrumbs

Generate BreadcrumbList JSON-LD schema to replace raw URLs with readable breadcrumb trails in Google search results. Position validation included.

No limitsZero data leaksSuper fast

BreadcrumbList JSON-LD Generator

#1
#2
#3

json output

<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": "Calculators",
      "item": "https://example.com/calculators"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Tax Calculators",
      "item": "https://example.com/calculators/tax-calculators"
    }
  ]
}
</script>

Embed in the <head> of the relevant page. Google may turn this into a breadcrumb trail in SERPs (replacing the URL line).

You're on 7BusyBoss — 300+ free tools that run instantly in your browser. No signup, nothing uploaded.

Slug GeneratorFAQ Schema (JSON-LD) GeneratorCron Expression BuilderAI Code GeneratorHTML to JSX ConverterJSON Formatter & Validator
Browse all Technical SEO →
About this tool

Breadcrumb markup replaces the URL in search results

Google uses BreadcrumbList JSON-LD to render a breadcrumb trail in place of the raw URL in a search result. For a deep path like /calculators/tax-calculators/gst-calculator, that turns an unreadable string of slugs into Home › Calculators › Tax Calculators › GST Calculator.

This is worth singling out because it is a current, live benefit, which is not true of all structured data — FAQ rich results, for instance, were largely withdrawn in 2023. Breadcrumbs still render, which makes this one of the few schema types with a payoff you can actually see in the SERP.

The position field is where implementations break

Each ListItem carries a position, and the values must start at 1 and increase by exactly 1, in the order the trail reads from broadest to most specific. A three-level trail uses 1, 2, 3.

Gaps and out-of-order values cause the markup to be rejected or misread, and this is comfortably the most common implementation error — usually from generating the trail in a loop that skips a level, or from reversing the order so the current page comes first. Read the output and check the positions ascend before shipping.

A complete example

<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": "Calculators",
      "item": "https://example.com/calculators" },
    { "@type": "ListItem", "position": 3,
      "name": "GST Calculator",
      "item": "https://example.com/calculators/gst-calculator" }
  ]
}
</script>

Note that every item is an absolute URL. Relative paths are a common cause of silent failure — the markup validates as JSON but the URLs cannot be resolved.

The current page as the final item

The trail includes the current page as its last entry. This tool emits a URL for it; schema.org also permits omitting item on the final entry, since a page has no need to link to itself. Both are accepted, and the name is required either way.

The rule that matters more: the trail must match a breadcrumb navigation the user can actually see. Structured data describes the page, so inventing a hierarchy that exists nowhere on it is a policy violation rather than a clever shortcut. If your page has no visible breadcrumbs, add them before adding the markup.

One trail per page, and validation

Emit exactly one BreadcrumbList in normal circumstances. Multiple trails are legal for a page genuinely reachable through more than one hierarchy — a product in two categories, say — but most sites should pick the canonical path rather than listing every route that leads there.

The script tag goes in the <head> or the body; both work. Before deploying, check it with Google's Rich Results Test, which reports whether the trail is eligible to render, and the Schema Markup Validator for spec conformance. See also the FAQ schema generator and the robots.txt generator.

How to use the Breadcrumb Schema (JSON-LD) Generator

Takes about a minute. No signup, no download, your data stays in your browser.

  1. 1
    Open the tool. Scroll up to the Breadcrumb Schema (JSON-LD) Generator above — it loads instantly in your browser, no install needed.
  2. 2
    Enter your values. The fields come pre-filled with realistic defaults so you can see how it works — replace them with your own numbers.
  3. 3
    Read the result. The output updates instantly. Copy or share it — nothing is uploaded to a server, everything stays on your device.

Frequently asked questions

Common questions about the Breadcrumb Schema (JSON-LD) Generator.

What happens if my breadcrumb positions are out of order or have gaps?

The markup is rejected or misread, and no trail renders. Positions must begin at 1 and increase by exactly 1, ordered from the broadest level down to the current page. This is the most frequent implementation error, usually caused by a loop that skips a level or by building the list in reverse.

Should I include a URL for the final breadcrumb item?

Either way is valid. This tool includes the current page URL, while schema.org also allows omitting the item field on the last entry since a page need not link to itself. The name field is required regardless. Do not omit it from the trail altogether — the current page belongs there.

Does the markup have to match the breadcrumbs shown on the page?

Yes. Structured data is a description of the page, so the trail must correspond to navigation a visitor can actually see. Inventing a hierarchy that does not appear on the page breaks Google structured-data policy and can attract a manual action. If there are no visible breadcrumbs, add them first.

Why do breadcrumbs still work when FAQ rich results stopped?

Because Google withdrew one specific treatment rather than deprecating structured data. FAQ rich results were restricted in 2023 to a narrow set of authoritative sites, while breadcrumb trails continue to replace the URL in results for ordinary sites. That makes breadcrumb markup one of the few schema types with a visible payoff today.

Can a page have more than one breadcrumb trail?

It is permitted when a page is genuinely reachable through several real hierarchies, such as a product filed under two categories. In practice most sites should emit one trail for the canonical path, since multiple trails add complexity without benefit unless the alternate paths actually exist in the navigation.

Community rating

Discussion (0)

No comments yet. Start the discussion.

Keep exploring

Related tools across 7BusyBoss — all free, all instant.