Tool
What the Breadcrumb Schema Generator does
Breadcrumb Schema Generator: generates JSON-LD only from One per line: Name | URL.
The inputs are One per line: Name | URL; the output is JSON-LD only. Values update as you type, so comparing options is a matter of editing one field.
Typical users are anyone tuning a snippet. What Google displays is rarely exactly what you wrote, and the difference costs clicks.
Everything happens inside this page. Nothing you type is sent to a server, and there is nothing for us to store.
The field reference, the method and a worked example using the default inputs follow the tool itself.
What do the Breadcrumb Schema Generator fields mean?
The Breadcrumb Schema Generator uses 1 input. Sensible defaults are loaded up front, which means you can change one number at a time instead of filling the whole form first.
| Field | What to enter | Default |
|---|---|---|
| One per line: Name | URL | paste or type any amount of text | Home | https://example.com/ Blog | https://example.com/blog/ Choosing a mortgage | https://example.com/blog/mortgage |
How does the Breadcrumb Schema Generator work?
Each output is derived from the inputs above in a single pass; there is no hidden state carried between runs, so the same inputs always give the same generated output.
Bad input produces a message, not a silently incorrect figure.
Worked example
These are the values the Breadcrumb Schema Generator loads by default, and the result it produces from them. These are the exact values loaded when the page opens, and the answer they produce.
| One per line: Name | URL | Home | https://example.com/ Blog | https://example.com/bl… |
|---|
| JSON-LD only | { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type"… |
|---|
Two items minimum, and it must match reality
BreadcrumbList schema needs at least two ListItem entries to be eligible for the breadcrumb rich result. A single-item "breadcrumb" is not a breadcrumb.
Worth knowing
- Each ListItem needs a position (its order in the trail) and a name. The item URL can be omitted on the final entry, since that one represents the current page rather than a link to follow.
- The markup should mirror the site’s actual navigational hierarchy and the breadcrumb trail visibly shown on the page, if there is one. Google has been known to ignore breadcrumb markup that contradicts what a visitor would actually see and click through on the page.
- A common mistake is building the breadcrumb from a shallow category structure that does not match the URL path or the site’s real navigation. The display breadcrumb should tell a searcher, accurately, how they would get to this page by clicking through the site.
How to use it
- Paste your content into One per line: Name | URL.
- There is nothing to click. The answer keeps pace with your edits.
- Read JSON-LD only in the results panel.
- Print gives a tidy version without the navigation, which is handy for attaching to a file.
What this tool does not do
- This inspects the markup you supply; it cannot see server headers or your live rankings.
- Search engines weigh hundreds of signals. No single on-page check predicts position.
- Values outside the documented ranges are rejected rather than approximated.
Frequently asked questions
The form asks for One per line: Name | URL. Nothing starts empty, so the quickest approach is to replace the one number you actually care about.
With the values loaded when the page opens, JSON-LD only comes out as { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type"…. Overwrite any of the starting values and the result follows.
No. Disconnect from the internet and it still works; that is the simplest proof there is no server call.
No payment and no login. Advertising covers the running costs.
As accurate as the inputs allow. The arithmetic itself introduces no error beyond display rounding.