Search Console’s Indexed and Not Indexed Groups: How to Audit Warnings
Search Console reports can look worse even when your important URLs, rankings, and lead flow have not changed. The reason may be a reporting reclassification rather than a new technical SEO failure.
Google has changed how several Search Console reports group top-level statuses. In the Page Indexing report, pages previously grouped as Valid or Valid with warning are grouped under Indexed. Pages previously grouped as Error or Excluded are grouped under Not indexed.
This makes broad prioritization easier, but it can disrupt historical comparisons. It can also make an apparent error count rise when Search Console combines submitted and excluded versions of related issues.
Need help checking this on your WordPress, Google Ads, Analytics, local SEO, or website setup? Splinternet Marketing can review the issue and help you prioritize the next fix.
Read the issue details before changing the site
The top-level bucket is not a complete diagnosis. A Not indexed group can include intentional exclusions, such as duplicate URLs, alternate URLs, pages blocked by robots.txt, redirects, or pages that were never meant to appear in search.
Start with the issue-level tables below the chart. Review four details:
- Reason: Identify the specific condition, such as a 404, duplicate URL, noindex directive, redirect, or crawl problem.
- Source: Check whether Search Console attributes the condition to your website or to Google. A website-attributed issue deserves review, but it may still be intentional.
- Submitted-page filter: Compare all known URLs with URLs found in a sitemap. Use the submitted and unsubmitted views to determine whether the issue affects URLs you intentionally submitted.
- Representative URLs: Open a sample of affected pages instead of assuming every URL in the category has the same cause.
For example, a larger Not indexed total may reflect duplicate WooCommerce filter URLs or old WordPress attachment pages rather than lost product or service pages. Conversely, a smaller-looking group can still contain a serious problem if important sitemap URLs return errors or carry an unintended noindex directive.
What to do next
Use URL Inspection on several representative URLs, including at least one page that matters to revenue. Check:
- whether crawling is allowed;
- whether Google successfully fetched the page;
- whether indexing is allowed;
- the Google-selected canonical;
- the last crawl date; and
- the live-test result after a fix.
Keep the two URL Inspection views separate. The Google index view reflects information from Google’s indexed data and is used to generate search results. The live test checks the current page and helps troubleshoot a fix, but Google says it does not use live-test information as index data.
An indexed URL can still have non-critical structured-data, mobile-usability, HTTPS, or other enhancement issues. A verdict such as URL is on Google is not a guarantee that the page will appear for every query. For an important page, review the technical signals and then confirm actual visibility with a Google search for the URL.
Agencies and developers should also review operational reporting. Update dashboard formulas, spreadsheet labels, alert rules, exports, and API-dependent workflows that assume Valid, Warning, and Error are stable top-level categories. Google lists the Search Console API among the affected areas, and terminology or report changes may require workflow review. At the same time, Google notes that some automated alert messages may continue using older terminology.
Document the reporting change in monthly SEO reports. Clients should be told when a chart reflects a new grouping rather than a confirmed loss of indexed pages, rankings, or qualified traffic.
Decision rule: investigate the affected URLs, issue details, source attribution, sitemap status, URL Inspection results, and real search visibility before changing WordPress, robots.txt, canonical, sitemap, or noindex settings. Treat the new top-level groups as prioritization buckets—not as the incident itself.
Sources
Need help checking this on your WordPress, Google Ads, Analytics, local SEO, or website setup? Splinternet Marketing can review the issue and help you prioritize the next fix.
This article is for informational purposes only and reflects general marketing, technology, website, and small-business guidance. Platform features, policies, search behavior, pricing, and security conditions can change. Verify current requirements with the relevant platform, provider, or professional advisor before acting. Nothing in this article should be treated as legal, tax, financial, cybersecurity, or other professional advice.
Editorial note: Splinternet Marketing articles are researched from cited platform, documentation, regulatory, and industry sources. AI may assist with drafting and review; final content is checked for source support, practical usefulness, and platform/date accuracy before publication.
