AnyTool
Your files never leave your device. All processing happens locally in your browser.

How do I generate breadcrumb schema (BreadcrumbList JSON-LD) for a page?

Open AnyTool’s Breadcrumb Schema Generator, list the levels of your page’s trail — Home, then each section down to the current page — with a name and absolute URL for each, and it instantly builds a valid schema.org BreadcrumbList object and wraps it in a <script type="application/ld+json">…</script> block you can paste into your page. Positions are numbered automatically and sequentially from 1, a visual Home › Category › Page preview shows the trail, and a live validation panel flags missing names, relative or missing URLs, single-level trails and duplicate URLs. Everything runs in your browser — nothing is uploaded. Unlike the FAQ snippet, the breadcrumb rich result still works for normal sites: Google can show the trail in the search result instead of the plain URL, though whether it appears is at Google’s discretion, so test in the Rich Results Test.

  • Builds a valid BreadcrumbList object: itemListElement array of ListItem with position, name and item URL
  • Positions are auto-assigned sequentially from 1 (no gaps) over your named levels
  • Outputs a copy-ready <script type="application/ld+json"> block plus the bare JSON
  • Live validation: missing names, relative / missing URLs, single level, deep trails, duplicate URLs
  • 100% client-side — your content never leaves the browser; visual Home › Category › Page preview

What is

Breadcrumb Schema (BreadcrumbList structured data)

Breadcrumb schema is schema.org BreadcrumbList structured data — usually written as JSON-LD — that marks up the trail of pages leading to the current page. It uses an itemListElement array of ListItem entries, each with a position (sequential from 1), a name (the visible label) and an item (the absolute URL); the last item is the current page and its URL is optional. The markup should match the breadcrumb visible on the page. Google can use it to show the breadcrumb trail in the search result instead of the plain URL.

SEO & Web

Related terms

JSON-LDStructured dataRich resultsListItemschema.org

Frequently Asked Questions

Yes — unlike the FAQ snippet, the breadcrumb rich result still works for normal sites. Google can show the trail in the search result instead of the plain URL, though it is at Google’s discretion.

The breadcrumb rich result is one of the structured-data features that still works broadly: when your BreadcrumbList markup matches a visible breadcrumb on the page, Google may replace the plain URL in the search result with the breadcrumb trail (Home › Category › Page). It is not guaranteed — whether the trail is shown is at Google’s discretion — but valid breadcrumb markup is worthwhile and also helps search engines understand your site structure. Always test in Google’s Rich Results Test.

Yes. Every item URL in a BreadcrumbList must be a full absolute URL including https:// and the domain. Relative paths like /category/page are not allowed.

Google requires the item value of each breadcrumb ListItem to be an absolute URL — for example https://example.com/category, not /category. Relative URLs are not recommended and may be rejected. Only the last crumb (the current page) may omit its URL entirely, in which case Google uses the page’s own URL; including it and matching your canonical URL is still recommended. This tool validates each URL and flags any that are relative or missing.

Each ListItem has a position number that must start at 1 and increment by 1 with no gaps. This tool assigns positions automatically in the order you list the levels.

In a BreadcrumbList, every ListItem carries a position property: the first (top-level) crumb is position 1, the next is 2, and so on down to the current page. The numbers must be sequential whole numbers starting at 1 with no gaps. The Breadcrumb Schema Generator numbers your levels for you as you add, remove and reorder them, so the positions are always correct.

Yes. The BreadcrumbList should match the breadcrumb a visitor sees on the page, using the same labels and the typical user path — not just the raw URL segments.

Google asks that breadcrumb structured data represent a typical user path to the page and match the breadcrumb shown on the page. Use the same labels visitors see and the same order; don’t mirror every URL segment if that isn’t how users navigate. Marking up a trail that differs from the visible breadcrumb can prevent the rich result. Build or confirm the on-page breadcrumb first, then mark up the same trail.

Detailed Explanation

Breadcrumb schema generation: in-browser (AnyTool) vs typical online generators
CapabilityAnyToolTypical online generators
ProcessingRuns entirely in your browserOften server-side
Your contentNever uploaded, works offlineSometimes sent to a server
Output<script> block and bare JSON, both copy-readyUsually one block only
PositionsAuto-sequenced from 1, no gapsOften manual / error-prone
ValidationMissing names, relative / missing URLs, single level, deep trails, duplicate URLsOften none
Visual previewLive Home › Category › Page trailRarely offered
Honesty about rich resultsClear that the trail shows at Google’s discretionOften implies it always shows
Cost / signupFree, no signupOften gated or ad-heavy

AnyTool builds the BreadcrumbList JSON-LD locally and uploads nothing. Unlike the FAQ snippet the breadcrumb rich result still works for normal sites, but whether Google shows the trail is at its discretion; the markup must match the visible breadcrumb, use absolute URLs and keep positions sequential from 1, and should be tested in the Rich Results Test. Comparison as of June 2026.