You open Search Console and find a growing list under Crawled – currently not indexed. Some URLs are articles you care about. Others are filters, older pages or near copies. Do you rewrite them all?

Start by sorting the URLs by their job. Google has fetched these pages but has not indexed them. That status does not tell you the reason for each URL, and Google says it can be common without indicating a problem. The useful question is: which of these pages should be a distinct search result, and what evidence would justify changing one?

This guide is for reviewing a group of affected URLs. If you are checking one newly published page, start with my new-page indexing checklist to separate discovery, access and index selection.

Sort affected URLs by intended search role, inspect representative pages, then choose to fix access, consolidate overlap, improve a useful gap or watch.
Use the status to start a review. Choose the action from what the page and its closest alternative actually show.

First, separate pages you want indexed from pages you do not

In Search Console, open Indexing → Pages → Crawled – currently not indexed. First use the sitemap filter: view All submitted pages, Unsubmitted pages only, or one specific submitted sitemap. A submitted URL signals that the site intended Google to find it; an unsubmitted URL needs a decision about its role. If your site submits separate sitemaps by template, select one to review that group. The filter does not explain why a URL is not indexed. Google's Page indexing report documents these choices.

Copy example URLs into a working sheet with the URL, page type, intended search role and last reported crawl date. Google's example list is limited to 1,000 URLs and is not guaranteed to show every URL in that status. On a large site, sample by template or sitemap instead of treating the list as a complete inventory.

Group by page type: articles, service pages, product pages, filtered listings, old URLs or anything else your site generates. Mark each group index intended, index not intended or needs a decision. A filtered listing that repeats its parent page may have a different goal from a service page that should answer a distinct query. Google says you should not expect every URL on a site to be indexed; canonical pages are the ones that matter.

Inspect representative URLs, not just the total

Choose a few URLs from each important group: one affected page, a similar page that is indexed, and another affected page with a different pattern. Inspect each exact URL in Search Console. Record:

  • The indexed status and last crawl date.
  • Whether Google could crawl and fetch the page in its recorded inspection.
  • Whether indexing is allowed and which canonical Google selected, where those fields are available.
  • Whether the live page still shows the same content and settings.

The indexed record describes what Google knows from its crawl. Test live URL checks current access. A live pass cannot predict whether Google will index the page or select the same canonical, so do not treat it as a fix confirmation. Google's URL Inspection guide explains the difference.

If the page changed after the last reported crawl, note that timing before diagnosing the current version. If the wrong URL was inspected, start again with the final address visitors use.

Compare the page with its closest alternative

For an important URL that can be fetched, open it beside an indexed page serving a similar task. Ask what distinct job each page does for the reader. Compare the title, opening answer, example, evidence and next step. Also check whether site navigation or a relevant article links to the affected page.

The comparison might reveal a concrete problem: two pages answer the same question, the affected page is only a short variation, or an important page is hard to reach from the rest of the site. It may reveal no obvious problem. Google's canonical guidance explains how it chooses a representative URL from similar pages; its people-first content guidance offers questions for assessing a page's usefulness.

For example, imagine a fictional software site with several “best invoice tool for [profession]” pages. The pages use the same introduction and comparison table, with only the profession changed. One is indexed and several appear in this status. The useful review is to decide whether each profession has enough distinct needs and evidence to earn its own page. A new heading alone would not answer that question. This is an illustrative editorial decision.

Choose the next action by what you found

What the review shows Reasonable next step
The URL is not meant to be a separate search result Keep it out of the priority queue. Confirm its canonical, redirect or indexing instruction matches the site's intended URL plan.
The live page has a verifiable access or indexing block Fix that specific block, then test the live URL again.
Two pages serve essentially the same reader task Choose a main page and decide whether to consolidate or distinguish them. Check the destination before redirecting anything.
A distinct page misses a useful answer, comparison or evidence Improve that gap for the reader. Record what changed and why. The one-page improvement guide gives a step-by-step way to do it.
The page is new, accessible and no clear gap is found Record the status and review later. Do not manufacture a rewrite from the status alone.

Work on one representative page or template first when many URLs share the same pattern. That gives you a clearer change to inspect than editing every page at once. If the pages have different purposes, treat them as separate decisions.

Recheck the right evidence after a change

Save the affected URL list, inspection dates, what you changed and the next review date. After Google crawls the updated page, inspect the indexed record again. Watch whether the status changes for that URL and whether similar pages follow the same pattern. Search Console reports can lag behind an individual inspection, so keep their dates separate.

For a single meaningfully updated page, Google lets you request indexing through URL Inspection, but submission does not guarantee inclusion. A sitemap helps Google discover many pages; it is not a promise that each will be indexed.

Finish your review with a short decision note: keep, fix access, consolidate, improve or watch. Name the evidence behind that choice. If the pattern spans an important part of the site and you want a second set of eyes, bring the URL groups to an SEO consultation.

Google Search Console documentation reviewed 12 November 2026 and re-checked 13 November. The software-site example is fictional. No indexing or ranking outcome is claimed.

Vishnu Sudevan

Senior SEO, AEO & GEO consultant and practitioner. I write about search strategy, the tools I build and lessons from hands-on work.

More about my work →

TAKE THE NEXT STEP

Put the questions to work.

Use the free content audit planner or discuss a focused review of one important page.

Need help with a wider search challenge? Explore SEO consulting.