What the Page Indexing report shows
The Page Indexing report in Google Search Console summarizes the indexing status of URLs Google knows about for your property. Open it under Indexing > Pages in Search Console.
The report divides known URLs into two main groups:
- Indexed: Google has processed the URL and added it to its index.
- Not indexed: Google has not indexed the URL. The report groups these URLs by reason, such as Crawled - currently not indexed, Discovered - currently not indexed, Excluded by noindex tag, Page with redirect, or Alternate page with proper canonical tag.
Google previously called this area the Index Coverage report, so older articles, exports, and SEO tools still use that name. “Page Indexing report” is the current name. Both terms describe the same general job: showing how Google treats the URLs it has discovered.
Teams use these reports to answer practical questions:
- How many URLs are indexed right now?
- Which exclusion reasons are growing?
- Did a deploy, migration, or template change move a cohort of pages?
- Which statuses deserve investigation versus which are expected?
Google documents the report, its status definitions, and its validation workflow in the official Page Indexing report documentation.
How to read the Page Indexing report
Start with the trend, then examine the reasons underneath it. A growing site will not necessarily reach 100 percent indexed. Duplicate URLs, redirects, filtered pages, and intentionally excluded pages often should not be indexed.
Look for changes that affect URLs you intended to rank:
- Check indexed and not indexed totals. A sudden change can point to a deploy, migration, template change, crawl problem, or reporting delay.
- Open the Why pages aren’t indexed table. Prioritize unexpected increases in a reason, not simply the largest number.
- Check the source. Search Console identifies whether an issue is associated with the website or Google’s systems.
- Inspect example URLs. Confirm whether the affected pages are important, canonical, indexable, and included in your sitemap when appropriate.
- Use URL Inspection for individual pages. The Page Indexing report is organized around sitewide groups. URL Inspection provides Google’s details for one URL.
Google limits the example URLs shown for each reason, so the report should not be treated as a complete export of every affected URL. It is best for finding patterns and deciding which groups need investigation.
Page Indexing report vs. URL Inspection
Search Console gives you several related views, and they do not always line up cleanly:
- Page Indexing report: Aggregated counts by reason, with example URLs and trends.
- URL Inspection: Per-URL detail for the last crawled indexed view and a live test.
- Sitemaps report: Whether submitted sitemap URLs were processed, with limited indexing context.
- Crawl stats: Host-level crawl behavior, not a page-by-page index history.
Use the Page Indexing report to spot patterns across a site. Use URL Inspection when you need to understand a specific URL. Google’s URL Inspection documentation also notes that a successful live test does not guarantee that Google will index the page.
The two tools answer different questions. The Page Indexing report might show that many URLs are Crawled - currently not indexed. URL Inspection shows what Google reported for one URL on one check. Neither view provides a durable, URL-by-URL record of what changed between scheduled reviews.
Where the Page Indexing report falls short
Search Console is the source of truth for what Google reports. It is not designed as a monitoring system for SEO teams, agencies, or multi-site portfolios.
Common friction:
- Limited URL history. Counts move, but you often cannot reconstruct what changed for the URLs you care about without exporting and comparing data over time.
- Example-URL sampling. The report shows examples, not a complete prioritized inventory of important pages.
- Mixed intent. Intentional exclusions (noindex utility pages, correct canonicals) sit next to accidental problems (important pages stuck as crawled or discovered).
- Lag and inconsistency. Aggregated reports, URL Inspection, and live tests can disagree for a while. That mismatch is common enough that teams waste time arguing about which panel to trust. See also our notes on confusing GSC signals in related status guides.
- No client-ready narrative. Agencies and in-house teams still have to translate coverage jargon into “what changed, what matters, what we fixed.”
If you only open Search Console when something feels wrong, you can miss quiet regressions: an important template flipping to noindex, a canonical shift after a release, or a crawl-capacity problem that grows discovered counts for weeks.
What ongoing page indexing monitoring should show
A useful monitoring report should keep Google’s statuses and add the details needed to act on changes:
- Current status for every monitored URL, in plain labels tied to GSC reasons.
- Changed URLs since the last check, with previous and current status.
- Newly problematic URLs that matter to the business, not only the largest exclusion buckets.
- Resolved problems so you can see whether a fix actually moved the needle.
- Site-level trends such as indexed share, problem count, and status movement over time.
- Exportable detail (CSV/JSON and a print-friendly report) for clients, tickets, and audits.
That changes the conversation from “Google’s chart looks worse” to “these 37 important URLs moved from indexed to Crawled - currently not indexed after Thursday’s deploy.”
How BoastIndex tracks page indexing changes
BoastIndex does not replace the Page Indexing report. It uses Search Console URL Inspection data to monitor the URLs you choose, store each result over time, and report what changed.
In practice that means:
- Recurring inspections on a daily, weekly, or monthly schedule.
- Status history for indexed, not indexed, crawled not indexed, discovered, canonicalized, noindex, and related states.
- Alerts when important URLs change.
- Automatic index status reports after check runs.
- A clearer reporting layer than raw coverage exports, via the Google Search Console reporting tool workflow.
BoastIndex cannot force Google to index a page, request indexing as a product action, or guarantee coverage improvements. It tells you what Google reported, what changed, and which monitored URLs need attention.
Sample report
If you need a concrete picture of the deliverable, open the sample index report. It shows a site summary, status movement, changed URLs, and the kind of detail teams hand to clients or stakeholders after a monitoring run.
For agency reporting, start with the sample report and the index status reports product page. BoastIndex provides client-ready indexing reports, not a full white-label SEO suite.
Further reading
- Google Search Console: Page indexing report and status definitions
- Google Search Console: URL Inspection tool
- Crawled — currently not indexed
- Discovered — currently not indexed
- Alternate page with proper canonical tag
- Excluded by noindex tag
- Google indexing issues hub
- Index status reports
- Sample index report
- Google Search Console reporting tool