How to add Breadcrumb schema
A step by step way to add Breadcrumb schema so an AI engine understands where a page sits in your site and how your content is organized.
Breadcrumbs feel like the least important schema on the list, the little "Home > Category > Page" trail you barely notice. But that trail answers a question a machine keeps asking: where does this page sit, and what is it part of. Without it, the engine reads your page in isolation, with no sense of the section it belongs to.
This guide labels that path so the context is a fact, not a guess from your nav bar.
What Breadcrumb schema does
Breadcrumb schema is structured data that describes the path from your homepage down to the current page. It tells a machine that this product sits under this category, that this guide is part of this section.
It describes hierarchy, not content. A page can have great content and still leave an engine unsure how it relates to the rest of the site. Breadcrumb schema supplies that relationship in a form a machine reads directly instead of inferring from a styled navigation strip.
Do the task
Step 1: Map the real path
Write the genuine hierarchy from your homepage to the page. Home, then the category, then the page, in the order a reader actually navigates. Get the real path before you write markup. A fictional tidy path is worse than the messy true one.
Step 2: Write the BreadcrumbList JSON-LD
Build a BreadcrumbList with an ordered list of ListItem entries. Each item carries its name, its item URL, and its position. The positions run in order from the top of the path to the current page.
Step 3: Add it to the page
Wrap it in a <script type="application/ld+json"> tag and add it through a custom HTML block, a snippet plugin, or the page template. Because breadcrumbs describe structure, it usually makes sense on every page in a section, not just one.
Step 4: Keep it honest against your navigation
The labeled path must match the breadcrumb a reader sees and the way your navigation is actually organized. If your markup says the page lives under one category while your nav puts it under another, you are telling a machine something untrue about your own structure.
Step 5: Validate
Run the page through a structured data validator. Confirm the BreadcrumbList parses cleanly and the positions are sequential. A trail with a gap or a wrong order describes a structure you do not have.
The old way and the new way
The old way added breadcrumb schema purely for the small visual perk in Google search results, then never thought about it as structure.
The new way treats it as a statement about how your site is organized, written for a machine that reads your pages one at a time and needs help seeing how they connect. The reader still gets the same little trail. The engine gets a clear map of where each page belongs. The value is context, not decoration.
The honest part
Breadcrumbs are genuinely low-leverage compared to the schema that describes your actual answers. If you have no FAQ, Product, or Article markup yet, adding breadcrumbs first is polishing the hallway before you have built the rooms. Do the content-describing schema first, then come back for this.
And breadcrumbs do not make an engine cite you. They give context, which is one small input among many. Whether ChatGPT, Perplexity, Gemini, or Claude then uses your page is something we measure, not something we promise. The automated apply, with a preview and a per-fix approval, runs only through the connected Citedon plugin on WordPress. Elsewhere the scan diagnoses it and you add the block yourself.
Where to start
Run a free scan to see what an engine understands about your site's structure today, and which schema is actually worth your next hour. If breadcrumbs are the gap, fix them. If something bigger is missing, the scan will say so before you spend time on the trail.