Why does the number of URLs in Search Console's Web Vitals vary each month?

Where do the data in the Web Vitals report actually come from?

The Web Vitals report from Search Console does not measure the entirety of your traffic. It relies on field data collected via Chrome, as part of the Chrome User Experience Report (CrUX).

In practical terms, only a fraction of visits — those made by Chrome users who have opted into usage statistics sharing — are included in your reports. This means that two consecutive months can show different URL volumes simply because the sample has changed.

Why is this monthly variation normal?

Statistical sampling is based on a simple principle: observing a portion of traffic to infer overall trends. If your site receives 100,000 visits monthly, Google will not necessarily analyze each of them — it will capture a representative subset.

As a result, on a given month, some URLs might not appear in the report because they did not generate enough data in the sample. The following month, they may reappear. This is not a malfunction — it is the expected behavior of a sample-based measure .

Should you monitor absolute numbers or trends?

Google insists: focus on trends , not on the raw fluctuations in the number of URLs. If you drop from 150 detected URLs to 120 the next month, it does not necessarily mean degradation — perhaps the sample simply changed.

On the other hand, if your LCP, FID, or CLS scores are consistently degrading over several months, that is a signal to address. The volume of URLs is secondary; it is the measured performance that matters.

• The Web Vitals data come from a CrUX sample , not a comprehensive measurement.
• The number of detected URLs can vary monthly without reflecting a technical issue.
• Analyze performance trends (LCP, FID, CLS) over several months, not individual fluctuations.
• A decrease in URL volume is not necessarily alarming — statistical sampling explains these variations.

Does this explanation align with what we observe in practice?

Yes, completely. Any SEO practitioners who track Search Console on medium-traffic sites have noticed these monthly variations that can sometimes be perplexing. A site might show 200 URLs one month, 175 the next, and then bounce back to 210 without any technical modifications.

Google confirms here what we already suspected: these fluctuations are related to sampling, not to an algorithm change or a crawl bug. This is reassuring — but it also raises a limitation: we never have a comprehensive view of actual performance .

What nuances should we add to this statement?

First point: not all sites are created equal. A site with massive Chrome traffic will have more stable data than a niche site with 5,000 monthly visits. The smaller the sample, the greater the statistical variance .

Second nuance: Google does not specify how URLs are selected in the sample. Is it random? Weighted by traffic volume? By bounce rate? [To be verified] . This opacity makes fine analysis difficult — we must settle for observing trends without fully understanding the underlying mechanics.

How should you properly interpret the fluctuations in the Web Vitals report?

The first rule: never draw conclusions from a single month's data. If the number of detected URLs drops in February, wait for March and April before raising an alert. Trends should be assessed over at least 3 months .

The second rule: focus on performance scores (LCP, FID, CLS) rather than URL volume. A decrease of 20 URLs without degrading Core Web Vitals is insignificant. An increase in LCP from 2.0s to 3.5s on your main pages, however, requires immediate action.

What mistakes should you avoid when analyzing Web Vitals data?

Error #1: panicking over an isolated monthly variation. Sampling explains these discrepancies — there’s no need to launch a comprehensive technical audit because you dropped from 180 to 150 URLs.

Error #2: ignoring URLs that systematically disappear from the report. If an entire category of pages never appears in Web Vitals, it may be that it receives no Chrome traffic — a signal of poor organic visibility.

Error #3: relying solely on Search Console. CrUX data has its limitations — always supplement with PageSpeed Insights , Lighthouse in lab mode, and your own RUM (Real User Monitoring) tools.

What should you implement concretely?

A rigorous follow-up on Core Web Vitals requires a robust methodology . Export Search Console data monthly, track developments over at least 6 months, and segment by page type (product, category, editorial content).

Cross these data with your own performance metrics: real-world loading times, bounce rates, conversion rates. A degradation in LCP coupled with a drop in conversion rate is a clear signal — a simple sampling fluctuation without business impact is just noise.

• Export the Web Vitals data from Search Console every month and maintain a history for at least 6 months.
• Analyze performance trends (LCP, FID, CLS) rather than variations in URL volume.
• Segment data by page type to identify specific issues across categories.
• Cross-check Search Console with Google Analytics, PageSpeed Insights, and server logs for a complete view.
• Do not launch a technical investigation based on an isolated monthly fluctuation — wait 2-3 months for confirmation.
• Implement RUM (Real User Monitoring) to capture field data independent of CrUX.
• Prioritize optimizations on pages with high traffic and strong business impact, not on raw URL volume.
  Statistical sampling of Web Vitals data explains the monthly variations in the number of detected URLs — it is normal and expected. A practicing SEO must focus on performance trends over several months, segment analyses by page type, and cross-check Search Console with other data sources. These fine-tuned optimizations for monitoring and interpreting Core Web Vitals require advanced statistical and technical expertise; if you lack internal resources, enlisting an SEO agency specialized in performance issues can save you valuable time and prevent costly analysis errors.