Do you need breadcrumbs on a landing page?

"Home > Templates > Coach & Consultant": that light-gray trail of links, sitting just under the header, looks so consensual that it sometimes gets added without a second thought — that's what a "professional" site does. The problem is that a breadcrumb trail exists to show where you sit inside a hierarchy, and a pure ad-driven landing page has no hierarchy: it's a single page with a single goal and a single CTA, built so a visitor arriving from a Google Ads or Meta Ads campaign sees only one possible path. Our article on navigation menus already explains why copying the storefront site's header costs conversions; breadcrumbs raise a related but distinct question — part SEO markup, part wayfinding aid — that deserves its own answer.

Two things hiding under one name

"Breadcrumb" actually covers two independent pieces. On one side, the visible trail: the row of clickable links shown on screen, letting a user climb one level up. On the other, the BreadcrumbList markup from schema.org, an invisible JSON-LD block describing the same hierarchy for search engines. You can have one without the other — a visible trail with no JSON-LD still works for users but stays invisible to Google; JSON-LD with no visible trail works for SEO but helps no human visitor. Conflating the two is why both often get added out of reflex, or both get removed when only one of them was actually a problem.

What research says about real-world use of the visible trail

The idea that a breadcrumb trail "always helps" is shakier than it looks. A 2003 study by Bonnie Lida, Spring Hull and Katie Pilcher at the Software Usability Research Laboratory, Wichita State University (available on Google Scholar), observed spontaneous breadcrumb use on two real sites (Google Directory and OfficeMax): 79% of participants noticed the breadcrumb trail, but only 52% ever used it, and those who did use it didn't finish their tasks any faster than those who didn't — many preferred the back button or the main menu. A follow-up study by Spring Hull, published in 2004 in Usability News (available on Google Scholar), adds a nuance: when participants first received a brief explanation of how the breadcrumb worked, they completed tasks 23% to 33% faster than those given no such guidance. So a breadcrumb trail isn't magic — its benefit depends on whether a user understands it at a glance, not on its mere presence on the page.

Why an ad-driven landing page almost never needs one

A page built to receive paid traffic (Google Ads, Meta Ads, an email sequence) has, by design, only one level: it isn't the "detail page" of any category the visitor browsed before arriving. Showing a breadcrumb trail on it comes down to one of two bad options: either a trail reduced to "Home > [Page title]", which offers no real wayfinding since there's nothing to climb back to, or a genuine trail into the storefront site (home, categories, other offers), which reopens exactly the exit door that skipping the nav menu was meant to close. On this type of page, every clickable link that isn't the main CTA is a losing bet: a visitor who clicks "Home" in a breadcrumb trail is no more likely to come back and finish the form than one who clicks a regular menu link — which, per the same mechanics described in our article on Hick's Law, isn't very likely at all.

Where it actually earns its place: pages with a real hierarchy

• A template page like Coach & Consultant: it genuinely belongs to a category ("Templates") a visitor could have browsed before clicking through — a "Home > Templates > Coach & Consultant" trail describes a navigation that actually happened.
• A demo page like the SaaS waitlist template demo: it flows directly from its product page, in a clear parent-child relationship.
• A blog post — the one you're reading belongs to the "Blog" category, itself attached to the homepage: this is the most classic structure where a breadcrumb trail makes immediate sense, even for a reader who arrived straight from a Google search.
• A future category page (by topic, by industry): the moment a site introduces a second level of classification, a breadcrumb trail becomes the cheapest way to expose it, without duplicating a full menu in the header.

Google's January 2025 change shifts the SEO calculus

BreadcrumbList markup is still worth having, but its visible payoff has been cut roughly in half. On January 23, 2025, Google announced on its official Search Central blog that it would stop showing the breadcrumb trail in the visible URL of mobile search results, replacing it with a simplified display showing only the domain name — judged more readable on small screens. On desktop, nothing changed: the breadcrumb trail still shows in the search result, and the "Enhancements > Breadcrumbs" report in Search Console remains active for tracking markup errors. In practice, that means adding a BreadcrumbList today no longer buys a visual win on the majority of traffic (mobile), but it's still worth having for the desktop share and to help Google understand the site's structure — a context signal, not a universal search-result decoration anymore.

Implementing the markup without getting it wrong

1. The JSON-LD must exactly mirror the visible trail on screen — same labels, same order: a mismatch between the two is the most common error flagged in the Search Console's "Enhancements" report.
2. Every item in the BreadcrumbList must be an absolute URL (https://yourdomain.com/templates), never a relative path.
3. Only mark up pages that have a genuine hierarchy (template pages, demos, blog posts) — not ad-campaign-driven sales pages, in line with the general rule of only marking up what's real and visible on the page.
4. On a Next.js App Router project, a single shared server component (for example in the shared layout.tsx for the /templates/[slug], /demo/[slug] and /blog/[slug] routes) can generate both the visible trail and its <script type="application/ld+json"> from the same array of segments, which mechanically removes the risk of the two drifting apart.
5. Test with Google's Rich Results Test after every URL structure change, before treating the markup as final.

The rule worth keeping

A breadcrumb trail is neither good nor bad on principle: it's right, or wrong, depending on whether it describes a hierarchy that actually exists. On a single-goal, ad-driven landing page, there's nothing real to describe — adding one helps no one and opens an unnecessary exit. On a template page, a demo page, or a blog post, it describes a real navigation path and earns its BreadcrumbList markup, with an SEO payoff now concentrated on desktop since the January 2025 change. So the question to ask before adding one is never "does this look more professional?" but "where did this visitor actually come from, and what still sits above this page in the site's structure?"