Crawled, Currently Not Indexed: What It Means and How to Fix It
Crawled, currently not indexed means Google fetched the page, looked at it, and decided not to add it to the index for now. The URL is not blocked and not broken. Google simply judged it not worth indexing yet, almost always because of content quality, duplication, or weak internal signals.
What the status means
You will find this label in the Google Search Console Pages report, under the pages that are not indexed. It sits next to two related statuses that people often confuse: Discovered, currently not indexed, and Duplicate without user-selected canonical. They are not the same problem.
| Status | What happened | The core issue |
|---|---|---|
| Discovered, currently not indexed | Google knows the URL but has not crawled it | Crawl priority or perceived value |
| Crawled, currently not indexed | Google crawled it and chose not to index it | Content quality or duplication |
| Duplicate without user-selected canonical | Crawled, treated as a duplicate of another URL | Canonical and duplication signals |
Scroll table horizontally →
The distinction matters because the fixes differ. Discovered is a crawl and internal-linking problem. Crawled, currently not indexed is usually a value problem. Getting this wrong sends teams off rewriting robots.txt when the real issue is thin content.
Why Google does this
Google does not index everything it crawls. Indexing costs storage and compute, and the bar for inclusion has risen over the years. When a page is crawled and left out, it is usually one of a few reasons.
- The content is thin, or close to identical to other pages on the site.
- The page has almost no internal links pointing to it, so it reads as unimportant.
- It is a near-duplicate of a stronger URL, and Google is holding off.
- The site has published a large volume of low-value pages, and this one got caught in that judgement.
That last point is common on large sites. If you ship 50,000 auto-generated pages, Google may index a sample, watch how they perform, and leave the rest in this state. It is a quality signal about the pattern, not just the single URL.
How to diagnose it
Start in the URL Inspection tool. Confirm the page returns a 200, is not noindexed, and renders its main content in the crawled HTML. If rendering hides the content, that is a different problem, and our guide to what Google renders and skips is the place to look.
Then ask three questions. Is this page genuinely different from others on the site? How many internal links point to it, and from where? Would a person searching find this page useful, or is it filler? Be honest on the third one. Most pages in this bucket are there because the answer is no.
How to fix it
The fix depends on what the page is. For a page that should rank, strengthen it. Add substance a searcher actually wants, make it clearly distinct from neighbouring pages, and give it real internal links from relevant, well-indexed pages. Internal linking is the lever people underuse here. A page with ten contextual internal links from strong pages is treated very differently from an orphan.
For a page that should not exist as a separate URL, consolidate it. Redirect it to the stronger version, or canonicalise it, and stop generating the pattern if it is templated bloat. On large ecommerce sites this is often the right call, and our post on fixing index bloat covers the consolidation approach in detail.
After you make changes, request indexing for a sample of the affected URLs and wait. Reprocessing is not instant. Give it a couple of weeks before judging whether the change worked, and watch the status in the Pages report rather than refreshing a single URL.
A realistic timeline
People expect a fix to work overnight. It does not. Google has to recrawl the page, reassess it against the signals that made it skip indexing in the first place, and then decide to include it. On a healthy site that recrawl might happen within days. On a large site with a stretched crawl budget, the same page might not be revisited for weeks, which means your improvement sits unseen until then.
Set expectations accordingly. After you strengthen a batch of pages and add internal links, give it two to four weeks before judging the result, and track the count in the Pages report rather than obsessing over a single URL. If the number of affected pages is falling, the fix is working and you just need patience. If it is flat after a month, the change was not enough, and the honest answer is usually that the content still is not distinct or valuable enough to clear the bar. That is feedback too, and it is more useful than another round of requesting indexing.
On very large sites, crawl priority is the hidden variable. A page Google considers unimportant gets crawled rarely, so even a good fix takes longer to register. That is why internal linking does double duty here: it raises perceived importance, which lifts crawl priority, which shortens the wait for your change to be seen.
What not to do
Do not spam the request indexing button on thousands of URLs. It does not override a quality judgement, and it wastes your time. Do not add these URLs to the sitemap and assume that forces indexing. Sitemaps help discovery, not the decision to index. And do not block the pages in robots.txt to make the report look cleaner. That hides the symptom and can strand pages you actually wanted.
When to accept it
Sometimes the right answer is to leave it. If a page is a genuine dead end, printer-friendly versions, thin tag archives, endless filter combinations, then Google declining to index it is correct behaviour. Consolidate or noindex those deliberately and move your attention to the pages that earn revenue.
The takeaway: Crawled, currently not indexed is Google telling you a page did not clear the bar. Treat it as feedback. Improve the pages worth keeping, consolidate the ones that are not, and stop trying to force the decision with buttons and sitemaps. If a large share of your important pages sit in this state, that is a signal worth a proper technical SEO audit.