If you have ever opened Search Console's Page indexing report and found a long list of pages marked "Crawled - currently not indexed", you have probably wondered whether your site is broken. The short answer, now in Google's own words, is usually no.
On November 3, 2026, Google rewrote the help text for this status to say plainly that it is common, that Google does not index every page on the web, and that the status does not necessarily indicate a problem. The old advice — "no need to resubmit this URL" — is gone, replaced with a clear instruction: check your important pages with URL Inspection, and only escalate if you suspect a site-wide indexing bug.
This article explains what the status actually means, what exactly changed in Google's guidance, when to ignore it, and the four checks that fix the cases that do matter.
| What changed | Before (until Nov 2, 2026) | Now (from Nov 3, 2026) |
|---|---|---|
| Main message | Crawled, not indexed; may be indexed later | Crawled, not indexed; Google does not index every page |
| Is it a problem? | Not stated | Common, and does not necessarily indicate an issue |
| Resubmitting | No need to resubmit this URL | Not mentioned at all |
| What to do | Nothing stated | Check important pages with URL Inspection; report site-wide bugs |
| Page quality | Mentioned in earlier guidance | Not mentioned in the new text |
What "Crawled - currently not indexed" actually means
The status means exactly what it says: Googlebot visited the page, looked at it, and decided not to put it in the index. That is the whole story for that URL. It does not mean the page is blocked, broken, or penalised. A blocked page shows up under a different status, "Blocked by robots.txt". A page Google cannot reach at all shows up as a crawl error.
This status sits in between: Google reached the page fine and chose not to index it.
Google's index is selective by design. It does not keep a copy of every page it crawls, because most of the web is made of pages nobody would ever search for: filtered category pages, tag archives, print versions, old campaign landing pages, and near-duplicates of pages that already exist. When Google says it "doesn't index all pages across the web", it is describing normal operation, not a failure.
A site with a few dozen URLs in this status is behaving the way Google expects a site to behave.
The number that matters is the share, not the count. Ten URLs in this status on a 50-page site is a different situation from ten URLs on a 50,000-page site, and both are different from 3,000 product pages in this status on a store that depends on those pages for revenue.
The first question to ask when you see the status is always the same: are the pages in the list pages that should be earning traffic? If the answer is no, the status is housekeeping, not a problem.
What Google changed on November 3, and what it did not change
The change is small but the tone shift is real. The new help text, as Search Engine Roundtable reported on November 3, 2026, reads: "The page was crawled by Google but not indexed.
Google doesn't index all pages across the web, so this is a common message for many sites and doesn't necessarily indicate an issue that needs attention." It then points you to URL Inspection for important pages, and to a form for reporting an indexing issue if you have fully diagnosed the problem and suspect a complete, site-wide indexing bug.
Two things disappeared. The old line, "It may or may not be indexed in the future; no need to resubmit this URL for crawling", is gone entirely. Google no longer tells you that resubmitting is pointless, and it no longer promises the page might appear later. The second disappearance is subtler: the new text says nothing about page quality, even though Google has named quality as a factor behind this status before.
Search Engine Roundtable flagged that omission as odd, and it is worth noting — but it does not mean quality stopped mattering. It means Google chose not to repeat it in this particular help text. A before-and-after comparison of the old and new wording lays out the same five differences side by side.
What did not change is the underlying behaviour. Google did not announce a new indexing system, a new ranking signal, or a change to how it picks pages for the index. The crawler still visits pages and the indexer still keeps only a subset. The November 3 update is a documentation change, and it should be read as one: Google is telling site owners to stop treating this status as an emergency and start treating it as a triage list.
When to ignore it, and when to act
Ignore the status when the pages in the list are ones you never expected to rank. Filter and sort URLs, tag archives, search-result pages, pagination beyond page two, old UTM-tagged campaign pages, and printer-friendly versions all belong in this group. If a page has no search demand, no links pointing at it, and no business value, its absence from the index costs you nothing.
Spending an afternoon trying to force it in is time taken away from pages that could actually earn clicks.
Act when the pages in the list are ones your business depends on. Product pages, service pages, location pages, and your newest blog posts should not sit in this status for weeks. If a page you published a month ago is still listed as crawled but not indexed, that is a real signal, and it is worth the four checks below.
The same applies to a pattern: if most of the pages sharing one template are in this status, the template is the problem, not the individual pages, and fixing one URL at a time will not help.
A useful rule of thumb is to sort the list by value before you do anything else. Open the Page indexing report, click into "Crawled - currently not indexed", and ask of each URL: would I notice if this page never appeared in search? If the honest answer is no, leave it alone. If the answer is yes, put it on the shortlist and work through the checks.
Most sites find the shortlist is much smaller than the full count — and that is the point Google is making with its new wording.
The four checks for important pages
1. Inspect the page with URL Inspection. Paste the URL into Search Console's URL Inspection tool, exactly as Google now suggests. It tells you whether Google can fetch the page, what canonical it sees, whether a noindex tag is present, and when it was last crawled. A noindex tag left over from staging, a canonical pointing at a different URL, or a crawl date from months ago each point at a different fix.
Do this for a sample of affected pages, not just one: if five pages share the same problem, you have found a pattern.
2. Check for blocks and bad signals. Confirm the page is not blocked by robots.txt, does not return a soft 404, and does not redirect somewhere unexpected. A quick way to cover the first two is to check your robots.txt and sitemap with a validator, then fetch the URL yourself and look at the status code it returns.
Pages that return a 200 status but show almost no content — a blank template, a "coming soon" message, a login wall — are common residents of this status, and the fix is content, not a resubmission.
3. Look for duplication. Google often leaves a page out of the index because a near-identical page is already in it. Check whether the same content exists at another URL on your site: a product listed under two categories, a blog post republished with a new slug, a page available with and without a trailing slash. If a duplicate exists, pick one canonical version, point the others at it with a canonical tag or a redirect, and let Google consolidate.
Trying to index both versions is fighting the system instead of working with it.
4. Fix the pattern, then resubmit in batches. If the problem is a template — thin product descriptions, auto-generated location pages with the same text, a tag system creating thousands of near-empty pages — fix the template first. Add genuinely useful content, merge near-duplicates, or noindex the pages that should never have been crawlable. Then request indexing for a small batch of the fixed pages and watch whether the indexed count moves before doing the rest.
Resubmitting hundreds of unchanged URLs is what the old guidance warned against, and it still does not work.
For the broader picture, it helps to know how the rest of the indexing report fits together. Search Console's other statuses each point at a different problem, and confusing them wastes time. Our guide to what each sitemap status actually means covers the sitemap side of the same report, and the robots.txt and XML sitemaps guide explains how the two files work together to control what Google crawls in the first place.
Best tools to check indexing status
The honest answer is that the best indexing tool is the one Google already gives you for free. Search Console's URL Inspection tool is the only tool that tells you what Google actually did with a specific page: whether it was crawled, when, what canonical it chose, and whether anything blocked it. No third-party tool can see that, because only Google holds the data.
If you are choosing between paid indexing checkers, ask each one where its numbers come from — a tool that cannot point at Search Console data is guessing from its own crawl, and its guess is not what Google sees.
That said, two free tools cover almost everything a small site needs. Search Console itself gives you the Page indexing report, the URL Inspection tool, and the sitemap report in one place. Alongside it, a robots.txt and sitemap validator catches the configuration mistakes that put pages into this status before Google ever sees them — a disallowed path, a sitemap listing URLs that redirect, a sitemap that has not been updated since a migration.
FrostRank's own validator does this without an account, which makes it a fast first check before you dig into Search Console. For bulk work, the Search Console API can export the full list of affected URLs so you can sort and prioritise them in a spreadsheet instead of clicking through pages of results.
What no tool can do is decide for you which pages deserve to be indexed. That is a judgement call about your own site: which pages earn money, answer a real query, or support a page that does. The tools give you the list; the triage is yours. Google's rewritten guidance is, in the end, an invitation to do that triage instead of panicking at the count.
What not to do
Do not resubmit the same unchanged URLs over and over. Requesting indexing does not make Google index a page; it asks Google to look again, and if nothing changed, the answer will be the same. Do not delete pages just to shrink the count, either — a page that is gone is a page that can never rank, and deleting useful content to make a report look tidy is the wrong trade.
And do not assume a drop in indexed pages means a penalty. Index counts move for ordinary reasons: a template change, a sitemap update, a crawl-budget shift after a traffic spike.
The one escalation Google now offers is worth knowing about. If you have fully diagnosed the problem — checked URL Inspection, fixed blocks and duplicates, confirmed the pages are genuinely valuable — and you still believe there is a complete, site-wide indexing bug on Google's side, the new guidance points to a form for reporting it.
That bar is deliberately high: a handful of unindexed pages is not a site-wide bug, and the form is not a shortcut around fixing your own templates. Use it only when the evidence points at Google, not at your site.
The bottom line is calmer than the old wording made it sound. "Crawled - currently not indexed" is Google telling you it saw the page and passed on it, for now. For most pages on most sites, that is fine. For the pages that matter, the fix is almost never a button in Search Console — it is better content, a cleaner canonical, or a template that stops generating pages nobody needs.
Sort by value, check the important ones, fix the pattern, and let the rest go.
Frequently asked questions
What does "Crawled - currently not indexed" mean?
It means Googlebot visited the page but Google chose not to add it to its search index. The page is not blocked or broken — Google reached it fine and decided not to keep it. Google does not index every page it crawls, so this status is common and, on its own, does not necessarily indicate a problem.
What did Google change about this status in November 2026?
On November 3, 2026, Google rewrote the help text for the status in the Search Console Page indexing report. The new text says Google does not index all pages across the web, that the status is common and does not necessarily indicate an issue, and it points site owners to URL Inspection for important pages and to a form for reporting site-wide indexing bugs. The old line saying there was no need to resubmit the URL was removed.
Should I worry if many pages have this status?
It depends on which pages they are. Filter, tag, and pagination URLs in this status are normal and harmless. Worry only when pages your business depends on — product pages, service pages, new blog posts — sit in this status for weeks. If most pages sharing one template are affected, fix the template rather than the individual URLs.
How do I fix a page that is crawled but not indexed?
First inspect it with URL Inspection to check for a noindex tag, a wrong canonical, or a block. Then check that it returns a 200 status with real content, and look for a near-duplicate page already in the index. Fix the underlying issue — content, canonical, or template — then request indexing for a small batch and watch whether the indexed count moves before doing the rest.
Will requesting indexing get my page indexed?
Not on its own. Requesting indexing asks Google to look at the page again, but if nothing about the page changed, the result is usually the same. Fix the reason Google passed on it first — thin content, duplication, a wrong canonical — and then request indexing so the fixed version gets seen.
What are the best Google indexing tools to check if a page is indexed?
Search Console is the best tool, because it is the only one that shows what Google actually did with your page — URL Inspection reports the crawl date, the canonical Google chose, and any blocks. A robots.txt and sitemap validator is the best companion check for configuration mistakes, and the Search Console API is the best way to export the full list for bulk triage.
Paid indexing checkers can only estimate from their own crawls, so ask where their numbers come from before trusting them.
