The Google Search Console page indexing report helps you identify patterns across URLs Google knows about. Its most useful question is whether the pages that matter to your business are eligible for Search and being indexed.
Back to the Google Search Console guide
Not indexed does not always mean broken
Redirected URLs, duplicates and intentionally excluded pages do not all need to be indexed. Trying to turn every row green can create more problems than it solves. Start with a list of pages that should appear: your homepage, important service pages, useful articles and other public content with a clear purpose.
Open Indexing → Pages, review changes over time and open a reason in the report. Inspect representative URLs from that group. For the current status of a particular page, use URL Inspection.
What common indexing reasons mean
| Reason | What to investigate |
|---|---|
| Excluded by noindex | Was the exclusion intentional? Check the SEO plugin and HTTP headers. |
| Page with redirect | Check that the destination is the intended replacement. |
| Alternate page with proper canonical | Confirm the preferred version is the one you want. |
| Not found (404) | Decide whether the page should exist or has been deliberately removed. |
| Crawled, currently not indexed | Review usefulness, duplication and internal links; a successful crawl alone is insufficient. |
| Discovered, currently not indexed | Check accessibility and how clearly the site points to this URL. |
Prioritize by business impact
Suppose 80 excluded URLs include 70 old redirected addresses, nine tag archives you intentionally excluded, and one current service page. The service page deserves attention first. The largest number in the report is not necessarily the largest business problem.
Create a short Google Sheets list with URL, intended status, reported reason, action and review date. Mark intentional exclusions separately from problems. This prevents the same harmless rows becoming a recurring monthly task.
Check for a shared WordPress cause
- Compare affected pages. Are they all posts, a custom post type, an archive or a recently rebuilt section?
- Check the shared setting. A post-type indexing rule can affect an entire section. Fixing individual pages may miss the underlying cause.
- Inspect a current example. Review the public response and live test before assuming the report reflects today’s configuration.
- Check discovery. Important pages should be linked from relevant navigation or content and included in the appropriate XML sitemap.
- Fix the actual cause. Then check several affected URLs, not just the first example in a report.
If legitimate pages unexpectedly return 404, use the WordPress 404 troubleshooting guide. If a page was deliberately deleted without a relevant replacement, a 404 may be correct. Redirecting every removed URL to the homepage is not a meaningful repair.
Validate after fixing
Where Search Console offers validation, start it after correcting the issue across the affected set. Validation checks your work; it does not change WordPress settings for you. Keep the report date and last crawl in mind while waiting for updates.
For content that is accessible but still excluded, review what makes it worth indexing. A page that repeats another article with a slightly different heading may need consolidation, stronger original information or a clearer role in the site.
Frequently asked questions
Should indexed totals match my WordPress post count?
No. A site can expose archives, alternate URLs and other resources beyond posts. Compare the intended indexable URLs instead of demanding equal totals.
Does fixing an exclusion guarantee traffic?
No. First establish that the page can be indexed, then use Performance to measure whether it earns relevant impressions and clicks.
Reference: Google’s Page indexing documentation.
