Skip to the content
searchboar.

Crawling and indexing

Page indexing report: intentional exclusion or an error?

The Page indexing report is Search Console’s site-level view of which known URLs entered Google’s index and the status groups of others. Exclusion can be intentional and correct. URL Inspection provides the detailed examination of an individual URL.

Also known as: indexing report

At a glance

  • Indexing every technical URL is not the goal; important independent pages matter.
  • Discovered but not yet fetched differs from crawled but not indexed.
  • Report groups and examples do not replace detailed inspection of an important URL.
On this page
Website pages appear in different status groups, with one selected for detailed inspection.
Whether an indexing status requires intervention depends on both the reported state and the page’s purpose.

What does the report summarize?

A website can include articles, products, filter variants, redirects and retired pages. The report groups known URLs by status. The objective is appropriate handling of important content rather than forcing every row into a favorable-looking category.

Google's guidance directs individual-page investigation to URL Inspection. The overview helps reveal patterns, such as many excluded new articles versus intentionally excluded technical addresses.

When is exclusion normal?

A secondary URL pointing to an appropriate canonical may not need separate indexing. A login page's noindex can be deliberate. A genuine 404 can correctly describe a discontinued page.

Compare intended behavior with actual content. Accidental noindex on a public service page is a problem; seeking independent indexing for every parameterized duplicate may be the wrong goal. Start with purpose rather than status labels alone.

Discovered or crawled, but not indexed?

“Discovered – currently not indexed” means Google knows the URL but has not yet fetched it. “Crawled – currently not indexed” means fetching occurred without the page entering the index. These suggest different investigations.

For the first, examine discovery, access and serving. For the second, inspect content independence and what Google received. Neither label alone proves poor writing or guarantees eventual inclusion. Resubmitting without diagnosis does not explain the state.

Example: fifty excluded URLs

Imagine a service business with fifteen independent pages and fifty excluded URLs. Investigation identifies forty campaign-parameter duplicates, eight old redirects and two important new guides.

The forty-eight technical exclusions may be appropriate. The guides deserve URL inspection: what response did Google receive, when did it crawl and which canonical did it select? The work narrows to two meaningful pages rather than fifty presumed faults. These figures are illustrative; report examples may not include every affected URL.

How do freshness and verification differ?

Reports contain processed data, so today's repair need not immediately change the status. A live test can establish current fetchability without promising indexing.

Record both the actual change and what was verified. “Returns HTTP 200” differs from “is indexed.” Indexing involves processing and decisions after retrieval, with possible delay.

Which pages deserve priority?

Main services, independent products and useful guides generally deserve more attention than incidental technical variants. Combine Search Console performance data with your content inventory to identify business priorities.

A practical list records each URL, desired state, observed state and next investigation. This turns the report into reviewable work rather than general anxiety. The aim is accessible, understandable important content, not eliminating every exclusion row.

Sources

  1. Search Console: Page indexing report
  2. Search Console: URL Inspection
  3. Google: preventing indexing