Is it true that CLS isn't a ranking factor yet—should you still optimize it?

What does “not yet” mean in this statement?

The wording from John Mueller is interesting: “not yet.” This implies that Google was planning to integrate Core Web Vitals, including CLS, as a ranking factor, but it was not the case at the time of this statement. CLS measures the visual stability of a page—how much elements move during loading. A high score indicates a poor experience.

Mueller clarifies that while CLS is not a direct ranking factor, it can have an indirect impact through user experience. Specifically? A site with a disastrous CLS can generate frustration, increase bounce rates, and reduce time spent on the page. These behavioral signals, in turn, can influence rankings—but with a time lag.

Why is this distinction between direct and indirect impact important?

Google always distinguishes between algorithmic ranking factors (direct, measurable, coded into the algorithm) and behavioral consequences (indirect, mediated by users). At that time, CLS was not a direct signal. The algorithm was not consulting this metric to adjust rankings.

On the other hand, a user who clicks a button that moves at the last moment often abandons the page. This abandonment, measured through signals like pogo-sticking or dwell time, can have an indirect SEO impact. However, this effect takes time to accumulate and be detected by Google—never an instant drop overnight.

What should be remembered for an SEO audit?

If you notice a sudden drop in traffic and your first hypothesis is “it’s CLS,” you are probably on the wrong track. A sudden drop has direct algorithmic causes: core update, manual penalty, partial de-indexing, keyword cannibalization, loss of backlinks. Even a catastrophic CLS has never been documented as a trigger for an immediate drop.

This does not mean that you should ignore CLS. A degraded score hurts user experience, and therefore your conversions and engagement. It’s an issue to address, but within a logic of continuous improvement, not emergency SEO firefighting.

• CLS was not a direct ranking factor at the time of Mueller's statement.
• An indirect impact through user experience exists, but it manifests over the long term, never instantaneously.
• A sudden drop in traffic cannot be attributed solely to CLS—look for direct algorithmic causes.
• Optimizing CLS remains relevant for UX, conversions, and preparing for a potential future integration as a direct signal.
• Do not confuse correlation and causation: a site with a poor CLS may lose traffic, but for other reasons.

Is this statement consistent with what we observe in the field?

Let's be honest: Google statements are often cautious and dated. Mueller refers to a time when Core Web Vitals were not yet a ranking factor. Since then, Google has announced their gradual integration as a signal (notably with the Page Experience Update). But even after this integration, the effect remains moderate and gradual, not a major ranking lever.

In practice, sites with excellent CLS do not mechanically rise in SERPs. Conversely, sites with mediocre CLS maintain their positions if their content, backlinks, and authority are strong. CLS is a signal among others, and not the most decisive. [To be verified]: Google has never published precise weighting of Core Web Vitals in the overall algorithm.

What nuances should be added to this position?

Mueller emphasizes the lack of immediate effect. This is true for a direct algorithmic signal, but it simplifies things for indirect effects. An e-commerce site with a disastrous CLS may see its conversions drop within days. This decline in business performance may translate to a reduced update frequency, deteriorating engagement, and ultimately an SEO impact—but over several weeks or months.

Another nuance: Google is constantly testing. It is possible that certain sites, in certain niches, were subjected to algorithmic A/B tests incorporating CLS before the official deployment. If you have noticed a correlation between a degradation of CLS and a drop in traffic, it is not necessarily a coincidence—but it remains an exception, not the rule.

In what cases does this rule not apply?

If your site is in an ultra-competitive niche where all signals are balanced (equivalent content, similar backlinks, comparable authority), then micro-signals like CLS can become tiebreakers. In this case, even a small advantage on Core Web Vitals can make a difference. But that is the exception, not the norm.

Another special case: sites where UX is a critical business criterion (SaaS, platforms, media). A degraded CLS can lead to a rapid user exodus, resulting in a drop in engagement metrics. Google may interpret these behavioral signals as a sign of low quality, and adjust rankings accordingly—but it is still an indirect and delayed effect.

What should you do if your CLS is poor?

Start by precisely measuring your CLS using Google PageSpeed Insights, Lighthouse, or Search Console (Core Web Vitals section). Identify the most impacted pages. CLS is calculated based on the sum of unexpected shifts of visible elements during loading. Common causes include images without explicit dimensions, web fonts causing FOIT/FOUT, ads or widgets loading after the main content.

Once the pages are identified, fix the technical errors: add width and height attributes to all images, reserve space for iframes and embeds, load fonts optimally (font-display: swap), avoid inserting dynamic content above the fold. These fixes are often simple, but require a systematic review of the front-end code.

What mistakes should be avoided in optimizing CLS?

The first mistake: treating CLS as an SEO emergency. If you have a drop in traffic, CLS is probably not the cause. First, look for direct signals: penalty, de-indexing, loss of backlinks, content cannibalization, algorithm update. CLS is a continuous improvement project, not an emergency lever.

The second mistake: optimizing CLS at the expense of real experience. For example, some sites hide all content until resources load to avoid shifts. The result: a perfect CLS but a perceived loading time that is catastrophic. The goal is to stabilize the layout without sacrificing speed or accessibility.

How to verify that your optimizations are effective?

Use field data from Search Console, not just lab data. CLS measured in real conditions can differ from the Lighthouse score because it depends on user behaviors, screen sizes, and network connections. Monitor the evolution over a minimum of 28 days to detect stable improvement.

Also test the impact on your business metrics: bounce rate, time spent, conversions. If your CLS improves but these indicators stagnate, it means the UX issue lies elsewhere. Do not set a number for the sake of the number—set it to enhance the real experience.

• Measure your CLS via Search Console and PageSpeed Insights on critical pages.
• Fix images without dimensions, poorly optimized web fonts, and dynamic widgets.
• Do not treat CLS as a probable cause of a sudden traffic drop—look for direct algorithmic signals.
• Track the evolution of Field Data over a minimum of 28 days to validate improvement.
• Check the impact on business metrics (bounce rate, conversions, engagement) to confirm that the optimization is relevant.
• Never sacrifice perceived speed or accessibility to artificially improve CLS.