Will breadcrumbs in SERPs continue to evolve?

What does it really mean for a status to be 'in development'?

When Google refers to a feature as 'in development', it indicates ongoing experimentation on the algorithm side. Breadcrumbs in SERPs do not follow a fixed pattern: the engine tests different display formats, string lengths, and depth levels depending on the context of the query.

Specifically, your breadcrumb might appear complete one day, truncated the next, or completely replaced by a simplified URL. This instability is not a bug but a permanent testing phase where Google collects behavioral data to optimize the CTR.

Why doesn't Google establish a stable standard?

Because the engine adjusts display based on multiple variables: query length, device, content category, and even user profile. A breadcrumb effective for an e-commerce search may not be suitable for an informational query.

Google prioritizes user experience over technical predictability. If a test shows that an alternative format generates more clicks or reduces bounce rates, the engine switches without prior consultation. This empirical approach explains why no exhaustive documentation exists on the exact selection criteria.

What determines whether or not the breadcrumb is displayed?

Several factors come into play. The presence of structured markup (Schema.org BreadcrumbList) is necessary but not sufficient. Google may choose to ignore it if the URL is deemed more readable, if the navigation structure seems artificial, or if the breadcrumb exceeds an undocumented maximum length.

The consistency between the markup and the visible HTML structure also matters. If your schema.org indicates a hierarchy that the source code contradicts, Google may decide to display nothing rather than validate inconsistent information. Tests also show that sites with a flat architecture (less than 3 levels) see their breadcrumbs displayed less often.

• Structured markup is mandatory but does not guarantee actual display in results.
• Display varies by context: type of query, device, content category, user history.
• Google may reformat or truncate the breadcrumb according to its own non-public UX criteria.
• Architectural consistency between markup, HTML, and sitemap boosts chances of stable display.
• No fixed standard exists: following the Google Webmaster blog remains the only way to detect major changes.

Is this statement consistent with field observations?

Absolutely. SEOs have been witnessing a chronic volatility of breadcrumbs in SERPs for years. A site may have its breadcrumbs perfectly displayed for months, then abruptly switch to bare URLs without any technical modification on their part. This instability affects all sectors, including major e-commerce players with impeccable implementations.

What is even more intriguing is the inter-query variability on the same site. A product page may display a complete breadcrumb for a transactional query and a raw URL for a related informational query. This confirms that Google adjusts the display in real-time based on contextual signals that it does not disclose.

What nuances should be added to this communication?

Google talks about 'continuous improvement' but never specifies the criteria for evaluating these improvements. Improvement for whom? For overall CTR? For user satisfaction? For semantic coherence? This opacity leaves practitioners in the dark regarding the direction of developments. [To be verified]: Google has published no public metric on the CTR impact of breadcrumbs versus bare URLs.

Another point: the invitation to 'follow the Google Webmaster blog' suggests that major changes will be announced. However, history shows that many display adjustments roll out without prior communication. Practitioners discover modifications by crawling SERPs, not by reading official announcements.

In what cases does this instability pose a problem?

For sites with a complex architecture with high semantic value, the absence of a breadcrumb degrades immediate understanding of the page's context. A blog post under 'Home > Resources > Guides > Technical SEO' loses clarity if it simply appears as 'mysite.com/technical-seo/article-slug'. The click-through rate may suffer.

Marketplaces and multi-brand e-commerce sites suffer particularly. When Google replaces a structured breadcrumb with a URL, the user no longer immediately sees the product category or brand, which reduces the result's attractiveness compared to competitors whose breadcrumbs display correctly. This display inequality creates a random competitive imbalance.

What should be implemented concretely today?

Start with a clean Schema.org BreadcrumbList markup on all pages with a depth greater than 1. Each item must point to a real URL that aligns with the visible navigation. Test the markup via the Search Console and the structured data testing tool to eliminate syntax errors.

Then, align your visible HTML breadcrumb with the structured markup. Google compares the two: if your code displays a hierarchy different from that declared in JSON-LD, the engine often favors the raw URL to avoid confusion. Consistency between the two layers is a signal of technical quality.

What errors should be avoided to maximize display chances?

Do not create artificial breadcrumb levels just to inject keywords. Google detects hierarchies inconsistent with the actual structure of the site. Also avoid excessively long breadcrumbs (beyond 4-5 levels): the engine often truncates or ignores excessive strings to maintain snippet readability.

Another common pitfall: leaving breadcrumb levels pointing to 404s or redirects. Google validates the complete navigability of the breadcrumb. If an intermediate level is broken, the entire breadcrumb may be excluded from the SERPs. Regularly audit the integrity of your navigation links.

How to monitor the evolution of display on my site?

Set up an automated SERP monitoring on your strategic pages. Tools like SEMrush, Ahrefs, or custom scrapers allow you to capture the display format daily (breadcrumb vs bare URL) and detect switches. Cross-reference this data with your CTR curves in the Search Console to identify any correlations.

Document the display changes after technical updates to your site. If a deployment coincides with the disappearance of breadcrumbs, you will know that an element of your implementation is problematic. This historical traceability will help you react quickly in case of visible regression.

• Implement Schema.org BreadcrumbList on all pages with depth > 1
• Validate markup via Search Console and the structured data testing tool
• Strictly align the visible HTML breadcrumb with the structured markup
• Avoid artificial levels or those stuffed with unnatural keywords
• Audit link integrity: no 404s or redirects in the breadcrumb
• Monitor SERP display with automated scraping tools