How this tool works, step by step
Enter one public page URL in the form above. You can paste a full address or type a domain and path without a scheme; the form adds HTTPS when you leave it out. The checker requests that page and reads the HTML returned by the server. It does not crawl the entire website. Here is the sequence behind the report, including the checks that can be limited by a website's response.
Request the page safely
The checker accepts public HTTP or HTTPS pages, follows a small number of redirects on the requested website and retrieves up to 1 MB of the page's HTML. A failed request, inaccessible address, non-HTML response, excessive redirect chain or time limit produces an error instead of an invented result. Images, stylesheets and other page assets are not loaded.
Find JSON-LD in the response
It inspects structured data blocks in the source HTML and looks for Schema.org BreadcrumbList nodes. The report counts the blocks and the breadcrumb lists it can parse. A zero means none was found in the inspected source; it does not prove that a browser-rendered page has no breadcrumb navigation. Malformed JSON-LD and extraction limits are shown as notes rather than silently ignored.
Examine every listed step
For each list, the checker extracts its ListItem entries, their positions, names and destination values. It checks whether there are at least two steps, whether positions run in sequence from one, whether entries have names, and whether earlier steps provide an item destination. The final current-page step may omit its destination. The JSON-LD path cards display the names and URLs found in structured data. A separate HTML navigation section lists breadcrumb trails found in source markup and marks navigation hidden by inline styles or attributes. A nearby category link can be shown as an unconfirmed possible step, without adding it to the breadcrumb count. Other category links are not assumed to be breadcrumb steps.
Verify a bounded set of destinations
Distinct breadcrumb URLs on the same website are requested, up to five per check. The checker records the HTTP response and any followed same-site redirects, then reads a bounded amount of each HTML destination to look for robots noindex directives and canonical link elements. Destination requests run in a small parallel group under a shared time budget. External destinations, further URLs beyond five, oversized HTML and timed-out requests are labelled as unverified. A listed URL and a verified page are therefore different pieces of evidence.
Build the report
The first row shows breadcrumb lists, path items and findings. Eight smaller cards expose the underlying counts, while the JSON-LD path, HTML navigation and destination sections show their distinct evidence. A destination card separates HTTP status, redirect chain, noindex and canonical. Where a field could not be checked, it says “Not confirmed” instead of treating missing evidence as a pass. Review notes identify structural issues and destination concerns that need attention.
How to read the results
Start with the breadcrumb path. Does it describe a sensible route from a broad section to the current page? Read its step labels aloud and check that they match the actual sections a visitor can reach. Then compare the URL beside each step with the destination verification card. A correct position and label are useful only when the destination also leads where that label promises.
HTTP response
A successful response indicates the destination answered this request. A 404 or 5xx response needs investigation. A redirect may be intentional, but the breadcrumb should generally point to the preferred final URL when you can update it.
Indexing directive
A detected noindex is a review signal. Decide whether that section is deliberately excluded from search; do not remove the directive automatically. “Not found” only describes directives checked in this returned response.
Preferred URL
A canonical pointing elsewhere can reveal a breadcrumb that uses an alternate URL. Compare the declared destination with the page users should reach. A missing canonical is reported as missing, not automatically counted as a broken breadcrumb.
A partial destination card might still show HTTP 200 because the server answered before the HTML exceeded the verification limit. In that case the HTTP result is known, but noindex and canonical are not confirmed. The same principle applies to timeouts and non-HTML pages: use the evidence that was actually collected and leave the remaining fields undecided.
Breadcrumb best practices
Match the real hierarchy
Use a route that helps a visitor understand where the page belongs. Avoid adding unrelated keywords or a category that the page does not actually sit under. Sites with more than one meaningful hierarchy may have more than one valid breadcrumb trail.
Keep names and positions clear
Give each step a readable name, use ordered positions and keep the structured-data trail aligned with visible navigation where applicable. If a template changes category labels, update its structured data as well.
Point to usable destinations
Prefer the live, intended URL for earlier steps. Review redirects, broken links and unexpected canonical targets. A current-page final step can omit its item URL, but earlier steps should identify where they lead.
Recheck after changes
Run a single-page check after changing navigation, URL structure, a CMS template or a schema plugin. Try examples from different sections, because a good result on one page does not validate every page on the website.
Google's Breadcrumb structured data documentation describes the supported markup and required properties. Its robots directives guide and canonical guidance explain the indexing signals the destination cards help you inspect. Use those documents for Google-specific eligibility and behavior; this tool reports observable evidence, not a search appearance promise.
FAQ
Why does the checker say no breadcrumb list was found?
The requested page may not contain a BreadcrumbList in its server-returned JSON-LD. A visible or source-HTML breadcrumb navigation can still exist; the checker shows matching HTML navigation separately. A website may also add markup after JavaScript runs or use Microdata or RDFa. This checker does not evaluate those formats. Inspect the page source and the report's JSON-LD block count before deciding what to change.
What does “Destination HTML exceeds the verification limit” mean?
The destination answered, but its HTML was larger than this tool reads for destination verification. Its HTTP status may still be known; its noindex and canonical are left unconfirmed. The limit applies to HTML, not the total size of images and other assets. A large page is not automatically a breadcrumb error.
Why are some destination pages skipped?
The free single-page tool requests only the first five unique same-site HTTP or HTTPS destinations. External links and extra destinations appear as skipped so you can still see what the markup contained. Requests can also stop at the redirect, size or time limits, and the card describes the reason.
Does HTTP 200 mean the page is indexed?
No. HTTP 200 confirms that this request received a successful response. Indexing depends on other conditions and search engine decisions. The checker also inspects selected noindex and canonical signals, but cannot verify a search engine's actual index state.
Does a missing canonical always need a fix?
No. A canonical link can help clarify a preferred URL, but absence alone does not make a breadcrumb invalid. Look at the destination, its redirects and your broader canonical strategy before editing a template.
Can I check my entire website at once?
This free checker accepts one page URL at a time. Each run examines that page's source breadcrumb structure and a small number of its same-site destinations. Check representative templates individually; a result for one URL should not be treated as site-wide coverage.