Why Do Web Pages Drop Out Of Search Console Reports?

A query was raised by a user regarding Search Console reports. The user stated they are having a problem with some of their web pages showing up and then dropping out of Search Console reports. Especially in regards to the Core Web Vitals report, they are seeing a steady decline in the number of pages reported from month to month.

Google’s John Mueller recently addressed this issue in an office hours segment. He said, “it’s a matter of how Search Console reports on web pages. Rather than attempt to include every page in the report, they use a sample of the URLs from your site. The number of pages they use to sample your site can vary from month to month in exactly the way that you’re reporting.”

He further added, “it’s something where having fewer URLs in these reports doesn’t mean that the other URLs are bad or problematic. It’s just we didn’t check them.

So especially for the aggregate reports, which is for the Core Web Vitals to some extent, the AMP report, the Structured Data report, mobile friendliness … for those reports, we only take a look at a sample … and that sample can change over time.”

He explains, “they might look at 200 URLs in one month and then in the next, they’ll look at maybe 100 URLs or something like that. It doesn’t mean that anything bad is happening; it’s just that Google is looking at a smaller sample of pages from your site.”

He advises that, instead of stressing out about the changing sample size, you should focus on what is actually being reported – specifically the relationship between the bad pages that are reported and the good ones.

If you see that all of the URLs in the report are without errors, you’re good to go. But, if you’re seeing errors, especially if the proportion of errors is increasing over time, you’ve probably got some fixing to do.

In any case, the total number of URLs in the report should not be your primary concern. It’s the relationship between the pages and the reported negatives you should focus on and attempt to fix.

You can watch the video below, where John discusses the issue, starting at the 51:33 mark: https://youtu.be/rCcDsmjn-SA