What Is Crawled – Currently Not Indexed?
Crawled - Currently Not Indexed is a Google Search Console status that means Google fetched the URL, read what was on it, and decided not to index it.
Crawled – Currently Not Indexed is a Google Search Console status that means Google fetched the URL, read what was on it, and decided not to add it to the index. It is not a crawl failure and not a technical block. The page was reachable, the render completed, nothing timed out, and the answer was still no.
Why this status should worry you
Every other indexing status points at something you can fix. Blocked by robots.txt names a file. Redirect error names a chain. Server error names a response code. This one names nothing, because there is nothing to name, and that is precisely what makes it expensive to ignore.
Left alone, the pattern compounds. Pages sitting in this status earn no impressions, so they earn no clicks, so nothing feeds back to suggest they were worth publishing. Teams keep producing more of the same template, and the status count climbs with each release. The useful first move is not a technical audit at all: check which sections already pull real traffic, then compare those pages against the ones Google declined. The difference between the two sets is usually the whole diagnosis.
What Google is actually doing
Indexing is a selection process, not a queue. Google is not working through a backlog and will not reach your URL eventually. It has already reached it and made a call.
- The URL is discovered. A sitemap entry, an internal link, or an external link puts the address in front of the crawler.
- The fetch succeeds. Google receives a 200 response and the HTML, then renders the page as a browser would.
- The content is parsed and compared. Google matches it against what is already indexed, from your own site and from everyone else’s.
- Near-duplicates are consolidated. If the page repeats a pattern Google has already stored many times, storing it again buys nothing.
- Selection happens. Google weighs the predicted value of holding this URL in the index against the cost of holding it. Pages that lose that comparison land in this status.
- Re-evaluation runs on Google’s schedule. The decision is revisited when the page changes materially or the signals around it change, not when you ask.
The scale of the problem matters as much as the cause. A dozen URLs in this status on a blog is noise. Several thousand across one directory is a template generating pages nobody needed, which is the same fault line described in what happens when a site indexes too much. Read the report by pattern rather than by page, because the pattern is where the fix lives.
| What the report shows | What it usually means |
|---|---|
| A handful of URLs published in the last fortnight | Normal lag, not a problem yet |
| An entire directory, all of it | The template produces pages that repeat each other |
| Thousands of filtered or parameter URLs | Crawlable surface generated by faceted navigation |
| Pages with no internal links pointing at them | Sitemap-only discovery, no importance signal attached |
| Pages that were indexed, then were not | A quality reassessment, not a fault |
| Tag or author archives in bulk | Pages that exist for the CMS rather than the reader |
The blunt version
This status is a quality judgement wearing the costume of a technical error. Google looked at the page and decided the index is better off without it. There is nothing to debug, which is why the standard response fails: opening the URL Inspection tool and clicking Request Indexing, then doing it again next week, then again the week after.
Requesting indexing asks Google to fetch a URL. It does not ask Google to reconsider. If the fetch already succeeded and the assessment already ran, another fetch of unchanged content returns the same verdict, because the input has not changed. Repeat submissions are the SEO equivalent of pressing a lift button harder.
The decision rule is simple. If the URL genuinely deserves to rank, change the page so a second assessment has something new to assess, and add internal links from pages that already perform. If it does not deserve to rank, stop trying: noindex it, consolidate it into a stronger page, or delete it. Both routes are cheaper than a monthly ritual of resubmission.
Note who profits from the confusion. Instant indexing services, indexing APIs sold outside their documented use cases, and tools that fire submissions in bulk all sell a fix for a problem that is not mechanical. They are selling repeated knocking at a door that opened, was looked through, and was closed on purpose. Understanding how crawling and indexing differ is what keeps that invoice out of your budget.
Example
Say a recruitment site publishes 8,000 location pages: jobs in one town, then the same template for the next town, with the town name swapped and the job listings pulled from the same national feed. Search Console reports most of them as Crawled – Currently Not Indexed. Nothing is blocked, the sitemap validates, and every page renders correctly in the inspection tool. The pages are near-identical, and Google already holds one version. The fix is not resubmission. It is fewer pages, each carrying something only that location can offer: local salary ranges, named employers, transport links, actual vacancy counts. Fifty pages of that will outperform 8,000 of the other, and the report stops climbing.
FAQ
How long should I wait before acting on this status?
For a page published in the last couple of weeks, wait. Indexing lag is normal and the status often clears itself. If the URL has sat there for a month or more while comparable pages on the same site index without trouble, the delay is not the issue and the page itself is.
Does requesting indexing again help?
Not if the page has not changed. Requesting indexing schedules a fetch, and a fetch of identical content produces an identical decision. The tool is built for genuinely new or genuinely updated URLs. Repeated submissions of unchanged pages do not escalate anything, and there is no queue position to improve.
Is this status a penalty?
No. It carries no manual action and no site-wide consequence. It is an ordinary selection decision made per URL, and it applies to pages Google judged not worth storing. Plenty of healthy sites carry a long tail of these, usually thin archives and filter URLs that were never going to earn traffic.
Related terms
- Dynamic Rendering — the serving workaround that can leave crawlers with a thinner page than your visitors see.
- Subdomain vs Subdirectory — where content lives, which changes how easily its signals reach the rest of the site.
- Index bloat — the opposite failure, where too many low-value URLs did get indexed.
Nothing is broken, so nothing can be repaired; the page was read and turned down. Either give Google a reason to change its mind, or accept the verdict and stop paying to have it re-delivered.