What is CLS by bot type
CLS by bot type shows how the Cumulative Layout Shift (CLS) performs across different crawler categories - such as Googlebot, Bingbot, and other search or social crawlers.
Instead of looking only at human traffic, this insight reveals how stable your layout appears to bots that crawl, render, and evaluate your pages. Since bots may use different rendering engines, viewport assumptions, and crawl strategies, their measured CLS can differ from real-user CLS.
If your layout shifts more for certain bots, it may impact:
How page quality is evaluated during rendering
How confidently content is indexed
How stable your page appears in search previews and ranking systems
CLS by bot type sample
Should you worry
In a healthy scenario, CLS remains stable across major bot types. That means:
Googlebot sees a visually stable layout similar to Bingbot
Dynamic elements do not shift unexpectedly during bot rendering
Critical assets (images, fonts, ads, embeds) reserve proper space
This indicates your rendering logic is predictable and consistent regardless of user agent.
You don’t need perfectly identical CLS across every crawler - but consistency across major search engines is important.
Healthy signals:
Stable CLS across Google and Bing
No large spikes tied to specific crawler types
Minimal layout instability during crawl peaks
Unhealthy signals:
Googlebot CLS significantly worse than real users
One bot consistently experiencing higher layout shift
High variance that correlates with rendering differences
If Googlebot sees worse CLS, ask:
Are images missing explicit width and height attributes for bot-rendered HTML?
Is dynamic content injected differently for crawlers?
Are consent banners, personalization layers, or A/B testing scripts behaving inconsistently for bots?
Layout instability often stems from rendering logic differences - not just frontend design.
Unhealthy CLS by bot type
Common causes of unhealthy CLS by bot type:
Missing reserved space for media
Images, embeds, or ads without defined dimensions may shift during bot rendering.
Different rendering paths
If bots receive pre-rendered HTML while users receive client-side rendering, layout timing can vary.
Font loading behavior
FOIT/FOUT issues may cause text shifts if fallback and final fonts differ in size.
Late-loading UI elements
Popups, banners, or injected components may appear after initial render.
If one bot consistently shows worse CLS, investigate rendering parity. Subtle differences in delivery logic often explain the discrepancy.
Resolving unhealthy CLS by bot type
Go-to action plan to resolve an unhealthy CLS by bot type:
Ask Uxi to analyze your CLS by bot type values and suggest improvements.
Use Filters to see if slowdowns align with specific geographies, pages, or device types.
Simulate CLS of the suspected insight to see if fixing it will resolve the slow CLS by bot type. If yes, this is where the resolution focus should be.
Once you’ve improved CLS, set an alert to be the first to know if it starts worsening again.
Try it yourself
Explore how your website performs across different bot types using real crawl data.
If bots experience slower CLS than users, your SEO visibility could be quietly affected - even if your Core Web Vitals look healthy on the surface.