Audit breadcrumb structured data, a machine-readable description of a page’s navigation path. Check that BreadcrumbList matches the visible trail and site hierarchy, then guide JSON-LD changes using the rendered HTML and HTTP response.
Use when auditing metadata, crawlability, structured data, or indexability related to Implement valid BreadcrumbList schema. Verify the rendered HTML and HTTP response rather than relying only on source files.
Review the instructions the agent will receive before you install.
Breadcrumbs help search engines understand your site's structure and often appear in search results, improving navigation and click-through rates.
BreadcrumbList structured data only when the page has a visible, meaningful breadcrumb trailVerify that the page contains valid BreadcrumbList structured data matching the visible breadcrumbs.
Implement a JSON-LD script that defines each level of the page's hierarchy using ListItem properties.
Explain how breadcrumb schema replaces URLs in search results with a more readable navigation path.
Review metadata generation, rendered HTML, structured data, and response headers related to Implement valid BreadcrumbList schema. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/breadcrumb
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.