Yes—keep breadcrumb navigation and structured data on mobile, but do not expect breadcrumbs to appear in Google’s mobile search results. Since January 23, 2025, Google has shown the domain instead of the breadcrumb in mobile results; breadcrumbs remain supported and continue to appear on desktop. Their value on mobile is helping visitors understand where they are, navigate the site, and access a clear hierarchy—not earning a breadcrumb display in mobile search.
Why breadcrumbs still matter on mobile
Google’s January 23, 2025 change removed breadcrumbs from mobile search-result URLs across languages and regions where Google Search is available. Google Search Central says the breadcrumb element is less useful to mobile searchers because it can be cut off on smaller screens. The change affects how results are displayed; it does not mean breadcrumb navigation or its structured data should be removed from a site. Google continues to support breadcrumb markup, and breadcrumbs remain visible in desktop results. Google’s announcement explains the change.
Google uses the mobile version of a site for indexing and ranking, and recommends equivalent structured data on mobile and desktop. It specifically names Breadcrumb among the structured-data types to prioritize when implementing mobile data. That makes accurate breadcrumbs worthwhile for site hierarchy and navigation even though they no longer produce a breadcrumb display in mobile search. Google’s mobile-first indexing guidance covers the mobile and desktop requirements.
Design a breadcrumb trail that works on a phone
Place the trail consistently near the page content, with concise labels that readers can recognize. W3C guidance describes placing breadcrumbs high on the page, typically after the header, as helpful for conveying a user’s location. Check the layout at narrow viewport widths: labels should remain understandable, links usable, and the trail free of collisions or ambiguous truncation. W3C’s breadcrumb technique offers further guidance.
Recommended Free Tools
#1 Best Overall
There is no universal maximum number of breadcrumb items, truncation rule, or pixel-size requirement in the cited guidance. If a long trail needs a responsive treatment, preserve its meaning and destination links rather than hiding or altering the hierarchy in a way that misleads users or produces different structured data from the visible trail.
Choose a useful hierarchy, not a copy of the URL
Google recommends representing a typical user path through the site rather than mechanically mirroring URL segments. Use names visitors understand, keep naming consistent, and link each ancestor to a real destination. When a page has more than one reasonable route through the site, Google supports multiple breadcrumb trails for that page. Google’s BreadcrumbList documentation describes this approach.
Keep mobile and desktop versions aligned
For a responsive site that serves the same page at one URL, check that the meaningful breadcrumb content and structured data are present in the rendered mobile experience as well as desktop. If the site uses separate mobile URLs, ensure the mobile version’s markup points to the correct mobile URLs. Google recommends equivalent structured data across mobile and desktop versions, and its indexing guidance emphasizes that the mobile version is used for indexing and ranking.
Do not remove useful page content simply to save screen space. Google notes that content can be moved into accordions or tabs as one option, but the breadcrumb itself should still convey the same hierarchy to users and search systems.
Rank #3
Add valid BreadcrumbList structured data
Google supports breadcrumb structured data using BreadcrumbList. A list must contain at least two ListItem entries in order. Give each item a name and position; include an item URL for every entry except the final one, where the item property may be omitted because Google uses the URL of the page containing the markup. Google illustrates JSON-LD and also documents Microdata and HTML approaches. Whichever format you use, make the markup represent the same hierarchy as the visible navigation.
Use Google’s BreadcrumbList requirements and examples as the implementation reference. Structured data can make a page eligible for supported search features, but Google does not guarantee that a feature will appear in results.
Use accessible breadcrumb semantics
Present the trail as a labeled navigation landmark and an ordered sequence. A typical structure uses a nav element with an accessible label such as “Breadcrumb,” containing an ordered list. This allows people using assistive technology to identify the navigation and follow its sequence.
- If the current page is represented by a link, mark it with
aria-current="page". - If the current page is plain text rather than a link,
aria-current="page"is optional according to the WAI-ARIA Authoring Practices Guide. - Keep decorative separators out of the accessibility tree when they would merely repeat the structure already conveyed by the labeled navigation and list.
See the WAI-ARIA Authoring Practices Guide breadcrumb pattern for an illustrative example. It cautions that browser and assistive-technology support can vary, including on mobile and touch devices, so test the implementation with the technologies your audience uses.
Best Value
Validate the implementation before and after release
- Check the markup: Run representative pages through Google’s Rich Results Test and correct critical errors.
- Inspect deployed pages: Use URL Inspection in Search Console on representative live URLs to see how Google accesses them and confirm they are accessible to Google.
- Test the actual mobile experience: Check the trail at narrow widths, follow its links, and test keyboard operation and relevant assistive technologies. These are practical usability checks, in addition to Google’s markup requirements.
- Monitor after indexing: Review the breadcrumb rich-result report in Search Console after pages are indexed. Repeat the checks after template changes; investigate increases in invalid items or unexpected losses of valid items.
Google notes that recrawling and reindexing can take several days. Valid markup makes a page eligible for supported results but cannot guarantee that Google will display a particular feature.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
