Unit 1: Foundations · Lesson 6 of 15

BreadcrumbList

Breadcrumbs show where a page sits in your site: Home, then Services, then this page. BreadcrumbList says the same thing in a form machines can read.

6 min readBeginnerBreadcrumbList, ListItem

When to use it

Use BreadcrumbList on any page that sits below the homepage in a clear hierarchy: service pages, blog posts, product pages, portfolio pieces. If your design shows a breadcrumb trail, it should almost always have this markup.

Unlike WebPage, this one can change how you look in search. Google can show the trail (something like fernandink.example › Services › Letterpress Printing) in place of a bare URL. Google's docs list this feature for desktop results. As always, valid markup makes you eligible, not guaranteed.

Start with the visible trail

Here's the breadcrumb a visitor sees on Fern & Ink's letterpress printing page. Your markup will mirror this exactly.

HTML · The visible trail
<nav aria-label="Breadcrumb">
  <ol>
    <li><a href="/">Home</a></li>
    <li><a href="/services/">Services</a></li>
    <li aria-current="page">Letterpress Printing</li>
  </ol>
</nav>

The code

Here's the matching markup, along with the page's WebPage block from Lesson 5. They sit together in one @graph, and the WebPage points to the breadcrumb by @id.

JSON-LD · WebPage + BreadcrumbList
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "WebPage",
      "@id": "https://fernandink.example/services/letterpress-printing/#webpage",
      "name": "Letterpress Printing",
      "url": "https://fernandink.example/services/letterpress-printing/",
      "isPartOf": { "@id": "https://fernandink.example/#website" },
      "breadcrumb": { "@id": "https://fernandink.example/services/letterpress-printing/#breadcrumb" }
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://fernandink.example/services/letterpress-printing/#breadcrumb",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://fernandink.example/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Services",
          "item": "https://fernandink.example/services/"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "Letterpress Printing"
        }
      ]
    }
  ]
}

Line by line

PropertyStatusWhat it means
itemListElementRequiredThe ordered list of steps in the trail. Google wants at least two.
ListItem.positionRequiredThe step number, starting at 1 for the top of the trail. It's a number, so no quotes.
ListItem.nameRequiredThe label for that step, as shown in the visible breadcrumb.
ListItem.itemRequiredThe full URL of that step. Required for every step except the last one.
@idOptionalOur advice: the page URL plus #breadcrumb, so the WebPage can point to it.

Why the last item has no URL

The last step is the page you're already on. Google's docs say you can leave out its item, and Google will use the current page's URL. Including it is fine too. We leave it out because it's one less thing to get wrong when a URL changes.

Use full URLs

Your HTML can use /services/, but the markup should use the full https://fernandink.example/services/. Schema doesn't know what domain it's on, so spell it out.

One trail per page is simplest

Some pages live in two places. A wedding invitation case study might belong under both Services and Portfolio. Google does allow more than one BreadcrumbList on a page. But it's more to maintain, and visitors only see one trail anyway.

Our advice: pick the main path, show that one, and mark up that one. If you really do show two trails on the page, you can mark up both.

If your CMS already does this

Many platforms generate breadcrumb markup for you. On WordPress, SEO plugins like Yoast and Rank Math output a BreadcrumbList as part of their own schema, and plenty of themes add one too. Before you write your own, check what's already there:

  • View the page source and search for BreadcrumbList.
  • If you find two (one from the theme, one from a plugin), turn one off. Two trails that disagree are worse than none.
  • If the generated trail doesn't match the visible one, fix the source of truth (your menu or category setup), not just the markup.

Writing it by hand is still worth learning. It's how you'll spot when the automatic version gets it wrong.

Common mistakes

Match what visitors seeIf the page shows "Home › Services › Letterpress Printing," the markup shouldn't say "Home › Minneapolis Letterpress › Best Letterpress Printer." Same steps, same labels, same order. Schema describes the page. It doesn't rewrite it.

  • Positions out of order. 1, 2, 3, from the top down. Skipping a number or starting at 0 confuses parsers.
  • Positions as strings. "position": "2" usually still validates, but 2 is the clean form.
  • Linking to pages that don't exist. If "Services" in the trail has no real page, either build one or drop that step.
  • Hard-coding one trail in a template. If every page's breadcrumb says the same thing, your CMS template isn't filling in the values. Spot-check a few pages.

Try it

Pick a page on your site that's two or three levels deep. Write down its visible breadcrumb trail. Then write the BreadcrumbList for it, with the last item having no item. Add a breadcrumb pointer to that page's WebPage block. Run it through the Rich Results Test, which does check breadcrumbs.

Check yourself

  • Every step has a position and a name.
  • Every step except the last has a full-URL item.
  • The markup matches the visible trail: same steps, labels, and order.
  • The WebPage points to the breadcrumb with "breadcrumb": { "@id": "…#breadcrumb" }.
  • I'm sticking to one trail per page unless the page really shows two.
Go deeper on Double Atari

How these foundation types fit together on a real site: Schema Markup Explained, Part 1: Organization, WebSite, WebPage, and BreadcrumbList.