In short
"Crawled — currently not indexed" means Googlebot fetched the page, evaluated it, and chose not to index it. It is a quality decision, not a technical error. The usual causes are near-duplicate content, thin pages, no internal links, or a page that answers nothing a user searches for. Requesting indexing does not override it; changing the page does.
What the status actually means
"Crawled — currently not indexed" means Googlebot fetched your page, looked at it, and decided not to add it to the index. Nothing is broken. There is no error to fix. Google made a judgment.
That is why it is more useful than it feels. Most Search Console statuses tell you about a mechanism; this one tells you about quality, in Google's own assessment, for free.
How it differs from 'Discovered'
The two get confused constantly, and they mean different things.
Discovered — currently not indexed: Google knows the URL exists but has not fetched it. This is usually about crawl priority — Google does not consider the page worth spending a fetch on yet, often because the site has produced many low-value URLs recently.
Crawled — currently not indexed: Google did fetch it, read the content, and passed. This is a content judgment.
Seeing large numbers of both on the same path usually means the same underlying problem: you published a lot of pages that are not individually worth having.
The real causes
Near-duplicate siblings. By far the most common cause on templated sections. If a page is substantially the same as dozens of others, Google may index a few representatives and skip the rest. It is not being punitive; it has no reason to store the same content 130 times. This is the mechanism behind most scaled content problems.
No internal links. A page reachable only from the sitemap reads as unimportant, because your own site treats it as unimportant. Sitemaps are a hint; internal links are a vote. Orphaned pages are routinely crawled and skipped.
Nothing a person searches for. Some pages exist for structure — thin category indexes, tag archives, paginated fragments. They are useful navigation and terrible search results. Google is right to skip them.
Thin against the competition. Not thin in the abstract, thin relative to what already ranks for that query. If the top results answer the question thoroughly and your page restates the definition, there is no reason to add it.
Recency and site-level quality. New sites and sites that recently published a large volume of weak pages get less benefit of the doubt. Quality assessment operates at section and site level, not only per page — which is why weak pages harm strong ones.
What does not fix it
Requesting indexing. It re-queues a crawl. Google already crawled it. The judgment was not about access.
Resubmitting the sitemap. Same reason. The URL was never the problem.
Adding words. Padding a thin page makes a longer thin page. If the additional words do not answer something, nothing changes.
Waiting. Time helps only if something changed. A page that was not worth indexing in March is not more worth indexing in June.
What actually fixes it
Work out which cause applies. Do not guess. Open two or three affected pages beside a page on the same site that is indexed, and look for the difference. It is usually obvious within minutes.
If they are near-duplicates: consolidate. Merge the thin siblings into one substantial page and 301 the rest to it. This is the single most effective fix, because it addresses the actual problem — too many pages for the amount of unique material — rather than the symptom.
If they are orphaned: link to them. From relevant pages, in context, with descriptive anchor text. If you cannot find a natural place to link a page from, that tells you something about whether it should exist.
If they are structurally thin: noindex them. Tag archives, filtered views, and internal indexes can be genuinely useful to visitors while having no business in search. Removing them from the index also improves how the rest of the site is assessed.
If they are competitively thin: make them better or drop them. Add something the ranking pages do not have — original data, a real example, a specific answer. If you cannot, that query may not be yours to win.
How to read it at scale
The status is most useful in aggregate. One affected page is noise. Several hundred on one path is a diagnosis.
Group affected URLs by pattern. If they share a template, the template is the problem. If they are spread evenly across the site, the issue is more likely site-level quality or crawl budget.
And track the direction. After a consolidation, expect Crawled — currently not indexed to fall while Page with redirect rises. That pairing is the shape of a fix working. Give it several weeks — reprocessing a few hundred URLs is not a five-day job.
If you are staring at a few hundred unindexed URLs and want a second read on which cause applies, book a call.
Common questions
What does 'Crawled — currently not indexed' mean?
Googlebot fetched the page, evaluated its content, and decided not to add it to the index. It is a quality judgment rather than a technical error, which is why there is no setting to change and no error to fix — the page itself has to change.
What is the difference between 'Discovered' and 'Crawled — currently not indexed'?
'Discovered' means Google knows the URL exists but has not fetched it, usually a crawl-priority decision. 'Crawled' means Google did fetch and read the page, then chose not to index it — a content judgment. Seeing both at scale on one path usually points to the same underlying cause.
Does requesting indexing fix 'Crawled — currently not indexed'?
No. Requesting indexing queues another crawl, but Google already crawled the page — access was never the issue. The decision was about the content's value, so only changing the page, its internal links, or the number of near-identical siblings will change the outcome.
How many pages being not indexed is normal?
A handful is unremarkable on any site. Several hundred on a single URL pattern is a diagnosis, not noise — group the affected URLs by template, because a shared template almost always means the template is spreading too little unique material across too many pages.
How long after fixing pages will they get indexed?
Typically several weeks for a few hundred URLs. Google has to recrawl, follow any redirects, and reprocess the surviving pages. Watch for 'Crawled — currently not indexed' falling while 'Page with redirect' rises, which is the shape of a consolidation working.
