How to read the Indexing Report

Should you panic when your Search Console indexing report is showing pages that aren't indexed? Is a 404 error code always a sign of a broken website?

In this episode of Search Off the Record, Martin Splitt and John Mueller from the Google Search Relations team dive deep into the Page Indexing report in Google Search Console. They unpack why treating this report as a static inventory checklist to "fix" things is the wrong response, how to spot massive SEO-ruining hosting or CDN traps, and why a healthy website doesn't actually need a 100% index rate.

In this episode, you'll learn: The Indexing Report Shift: Insights from the Search Console team's Hillel on why you should look for trend lines and systemic patterns rather than treating the report as a giant list of errors.

When 404s are Good: Why expected 404 errors are technically correct for deleted content, and how to survive the "boss panic" of numbers that won't go down.

The Domain Property Advantage: How setting up a domain property handles canonical shifts, www vs. non-www tracking, and performance data much cleaner.

The Site Query vs. Search Console: Why the site: query is an artificial tool that might show old domain moves or hreflang swaps for years, making Search Console your only true source of truth.

Hosting & CDN Traps: How aggressive bot protections, hidden interstitials, and "Soft 200" error pages completely destroy your crawl data and lead to malicious canonicalization.

Discovered vs. Crawled: What it actually means when pages sit in "Discovered/Crawled - currently not indexed," and how to recognize holistic site quality issues over technical bugs.

Key Takeaways for SEOs & Developers: Patterns over Inventories: Use the report to verify that your intentional changes (like site migrations or page removals) are processing correctly over time.

Forget the Ratio: There is no magic metric for indexed vs. non-indexed pages. Even Google's own developer documentation has a massive chunk of non-indexed content due to intentional choices.

Watch Out for Soft Blocks: Ensure your security layers or CDNs aren't serving "Are you a bot?" challenge screens to Googlebot with a 200 success code.

Computers Fail (And That's Fine): Minor server blips, failed DNS requests, or temporary 500 errors happen. Google's systems are resilient and will just try again later.