Do you really need to duplicate breadcrumbs on the mobile version to stay indexed?

Why does Google now only index the mobile version?

Since the shift to mobile-first indexing, Google exclusively uses the mobile version of a page to analyze, index, and rank it. This is no longer an addition — it is the only source of truth. If a structural element like breadcrumbs exists only on desktop, it becomes invisible to the engine.

This change responds to usage logic: the majority of searches are conducted on mobile. Google has therefore chosen to align with the actual user experience. Websites that neglect their mobile version find themselves penalized, even if their desktop version is flawless.

What does this change mean for technical SEO?

Breadcrumbs play a crucial role in understanding the architecture of a site. They help Google establish the hierarchy of pages, identify main categories, and distribute PageRank coherently. Without them, the engine may misinterpret the site's structure.

Let’s be honest: many responsive sites hide breadcrumbs on mobile to save space. This is a defendable UX choice, but it becomes problematic for indexing. If the Schema.org BreadcrumbList markup is only present in the desktop DOM, it serves no purpose.

How can I check if my breadcrumbs are being considered?

You need to test using Google’s Mobile-Friendly Test or the Search Console in URL inspection mode. Check the rendered HTML: the breadcrumbs should be visible in the mobile source code, not just displayed via CSS for wider screens.

Beware of classic pitfalls: a breadcrumb injected using client-side JavaScript may not be crawled properly if rendering takes several seconds. And a breadcrumb hidden with display:none only on mobile is likely to be ignored, even if the JSON-LD markup is present.

• Google indexe only the content present on the mobile version since the switch to mobile-first indexing.
• Breadcrumbs missing from this mobile version are no longer used to understand the site structure.
• It is imperative to ensure that the BreadcrumbList Schema.org markup is present in the mobile HTML, not just the desktop.
• Overly aggressive CSS hiding or slow JavaScript rendering can negate the effects of breadcrumbs.
• URL inspection in the Search Console allows you to validate what Google actually sees on mobile.

Is this statement consistent with field observations?

Yes, absolutely. It has been observed for several years that sites maintaining structural differences between desktop and mobile suffer from indexing inconsistencies. Breadcrumbs are a typical case: hidden on mobile for UX reasons, they disappear from the index.

The problem is that many developers are still thinking in terms of classic responsive design—which means the same HTML for all screens, with CSS variations. But if the CSS hides a crucial element, Google does not see it. And that's where the issue lies.

What nuances should be added to this rule?

John Mueller does not clarify whether Google tolerates visually hidden but DOM-present breadcrumbs. In theory, a breadcrumb in aria-hidden or position:absolute off-screen could be crawled. But it's risky — Google has previously penalized content deemed manipulative in similar contexts.

[To be verified]: Google has never clarified whether a breadcrumb present only in JSON-LD Schema.org, without a visible HTML counterpart, suffices. Field tests suggest that it does, provided that the JSON-LD is correctly injected server-side or during the first render. But caution: if the JSON-LD script is loaded lazily, it may be ignored.

When does this rule not apply?

For sites with strict responsive design — that is, a single HTML served to all devices, with no server-side variation — the question does not arise. Breadcrumbs are present everywhere, even if CSS displays them differently.

However, for sites with adaptive design or with distinct mobile templates (less common, but they still exist), this is a major risk. If the mobile template does not generate breadcrumbs, they are lost. And this is exactly what Mueller points out.

What should be done concretely to comply?

The first step: audit your site in mobile mode. Use the Search Console, ‘URL Inspection’ section, and verify that the rendered HTML actually contains the breadcrumbs — both in semantic markup (HTML tags like <nav> or <ol>) and in the JSON-LD Schema.org BreadcrumbList.

If your site is responsive and the breadcrumbs are only hidden via CSS on mobile, ensure they remain in the DOM. Avoid display:none that could be interpreted as cloaking if Google judges the content deceptive. Prefer a visual concealment via visibility:hidden or clip-path, or better: actually display them.

What mistakes should absolutely be avoided?

Don’t let a developer remove the breadcrumbs from the mobile HTML on the grounds that “it takes up space.” This is a strategic error that directly impacts how well Google understands your architecture. If UX requires them to be hidden, keep them in the code and add the JSON-LD in duplicate.

Another classic pitfall: modern JavaScript frameworks (Next.js, Nuxt, Gatsby) that generate the breadcrumbs client-side after the first paint. Google may crawl the page before the JavaScript has fully executed. As a result: no breadcrumbs seen, no structure understood. SSR or SSG is absolutely necessary for these critical elements.

How can I verify that my site is compliant?

Run a Mobile-Friendly test on a typical page (for example, an e-commerce product sheet or a blog article). Inspect the generated HTML and search for the presence of the markup itemtype="http://schema.org/BreadcrumbList" or its JSON-LD equivalent. If you don’t find it, Google won't see it either.

Also, use Screaming Frog in “Mobile Googlebot” mode to crawl your site and extract detected breadcrumbs. Compare with a crawl in desktop user-agent. Any difference is a warning sign. And that’s where many sites discover they have a problem.

• Ensure that breadcrumbs are present in the mobile HTML via the Search Console URL Inspection.
• Check that the Schema.org BreadcrumbList markup is generated server-side or during the first render (SSR/SSG).
• Avoid display:none on mobile to hide breadcrumbs — prefer reduced display or an alternative UX solution.
• Crawl your site with Screaming Frog in mobile user-agent and compare with desktop to detect discrepancies.
• Test each important template (homepage, category, product, article) systematically to validate the presence of breadcrumbs.
• Document your technical choices: if you visually hide breadcrumbs but keep them in the DOM, note this to prevent a future developer from removing them.