"Crawled - currently not indexed" is the most frustrating status in Search Console, because nothing is broken. Google found your page, fetched it, read it, and decided not to include it. There is no error to fix, no tag to remove, no server response to correct.
That makes it a judgement, not a bug. And judgements are changed by changing the page, not by resubmitting it.
What the status actually means
Two separate steps sit behind every indexed page, and conflating them is why this status confuses people.
| Step | What Google does | Will Google do it on request? |
|---|---|---|
| Crawling | Fetches the URL and reads the HTML | Generally yes. Submitting a URL reliably gets it crawled. |
| Indexing | Decides whether the page is worth storing and serving | No. This is an editorial judgement about the page itself. |
"Crawled - currently not indexed" means step one succeeded and step two did not. Compare it with the statuses it gets mistaken for:
- Discovered - currently not indexed: Google knows the URL exists but has not fetched it yet. Often a crawl budget or server speed issue.
- Excluded by noindex tag: You told Google not to index it. Technical, and trivially fixable.
- Duplicate, Google chose different canonical: Google indexed a different version of the same content.
- Crawled - currently not indexed: Google read it and was not convinced.
Note the word currently. It is not permanent, and pages do move out of this state, usually because the page or the site around it improved.
How to find every affected page
- Open Search Console → Indexing → Pages.
- Under "Why pages aren't indexed", click Crawled - currently not indexed.
- Export the list. The report samples, so treat it as representative rather than complete.
- Sort by what the URLs have in common: a template, a directory, a publication date, a content type. The pattern is usually the diagnosis.
If a whole directory is affected, the problem is the template. If scattered individual posts are affected, the problem is those pages. That single distinction saves hours.
The eight causes, and what fixes each
1. The content is thin
Not merely short, but lacking substance: a 300-word post that restates its own title, a product page with a manufacturer description and nothing else. Length is a symptom rather than the disease. The fix is genuine added value, whether that is specifications, comparison, original photography or first-hand experience.
2. It duplicates something Google already has
Syndicated articles, manufacturer copy used by fifty retailers, near-identical location or service pages differing only by a city name. Google indexes one and skips the rest. The fix is to make each page genuinely different, or to consolidate them into one strong page and redirect the others.
3. It is orphaned or barely linked
A page reachable only through a sitemap, with no internal links, signals that even the site's owner does not consider it important. Internal links are the clearest vote you get to cast. Three to five contextual links from relevant, already-indexed pages move more pages out of this state than any other single action.
4. The site has little crawl demand
New domains, private blog networks and sites with almost no inbound links get a small share of Google's attention. Nothing about an individual page fixes this. It improves as the domain earns links and traffic.
5. It does not match any real search intent
Pages written for a keyword rather than a question. If everything ranking for the target term is a comparison table and your page is a personal essay, Google has ten better answers already. Look at what actually ranks and ask whether your page belongs in that set.
6. Quality problems elsewhere on the site
Indexing decisions are partly site-wide. A few hundred thin tag archives or auto-generated pages can drag down how Google treats everything else. Pruning or noindexing genuinely low-value pages often lifts the ones you care about.
7. It is slow or renders poorly
If the meaningful content only appears after JavaScript executes, or the page takes many seconds to become useful, Google may evaluate very little of it. Check the rendered HTML rather than the source you wrote.
8. It is simply too new
Newly published pages on low-authority sites often sit in this state for weeks before moving. If the page is strong, well linked and recent, waiting is a legitimate strategy.
What it looks like by page type
The same status has different usual suspects depending on what kind of page it is.
| Page type | Most likely cause | First thing to try |
|---|---|---|
| Ecommerce product pages | Manufacturer description used verbatim across many sites | Rewrite descriptions, add real photos, specifications and reviews |
| Blog posts | Thin or covering ground already answered better | Consolidate weak posts into one comprehensive piece |
| Category and archive pages | Near-duplicate, paginated, little unique text | Add genuine introductory copy, or noindex the thin ones deliberately |
| Landing and campaign pages | Templated pages differing only by city or keyword | Make each substantively different, or keep one and redirect the rest |
| Multilingual or regional pages | Hreflang errors making versions look duplicate | Validate hreflang is reciprocal and self-referencing |
| Forums and user content | Huge volume of low-value threads | Noindex thin threads so crawl attention reaches the good ones |
| Older content | Stale, overtaken by fresher results | Update substantively, or merge into a current page |
When not to worry
Not every page in this report is a problem. Leave these alone:
- Pages you never wanted indexed: filtered search results, internal utility pages, thin tag archives. Add a
noindextag so the signal is deliberate rather than accidental. - Paginated pages beyond the first: Google frequently skips deep pagination and that is normal.
- Genuinely new pages: a few weeks is not yet evidence of anything.
- Very small fractions of a large site: a few hundred unindexed URLs out of a hundred thousand is unremarkable.
Chasing every URL in the report wastes effort that belongs on the pages that earn money.
A recovery process that works
- Rule out the technical blockers first. Confirm the page returns 200, carries no
noindex, and has a self-referencing canonical. If any of these is wrong, nothing else matters and no service can override them. - Check the pattern. Template-wide or scattered? That decides whether you fix one page or one layout.
- Add internal links. Three to five contextual links from indexed, relevant pages. This is the cheapest intervention with the highest hit rate.
- Improve the page materially. Not a paragraph. Add what a reader would actually want and a competing page does not have.
- Request indexing once in Search Console, after the page has genuinely changed. Requesting it repeatedly without changing anything does nothing.
- Wait two to four weeks before judging the result, then recheck in bulk with an index checker rather than clicking through URLs one at a time.
The order matters. Most people start at step five, which is why most people see no change.
What resubmitting can and cannot do
The "Request indexing" button re-queues a URL for evaluation. If the reason Google declined is still true, it will decline again, usually within hours. Indexing services work the same way: they get a URL crawled, which is the step Google will do on request, and they cannot influence the judgement that follows.
That is worth being clear about, because it defines when submission is the right tool. Use it when a page is new, or genuinely improved, and needs to be looked at again sooner than Google would get to it. It is the wrong tool for a thin page that Google has already assessed, and no provider can change that.
For backlinks specifically, the same logic applies to the page hosting the link: if it is unindexed, the link passes nothing, and why backlinks fail to get indexed covers that case in more depth.
FAQ
How long does it take to get indexed after fixing the page?
Anywhere from a few days to several weeks, depending on how much crawl attention the domain gets. Established sites see changes quickly; new domains do not.
Will requesting indexing repeatedly help?
No. It re-queues the same evaluation. If nothing about the page changed, the outcome will not change either, and there is no benefit to submitting the same URL repeatedly.
Is this a penalty?
No. It is an ordinary quality and priority decision, applied to most sites on the web. It carries no manual action and nothing appears in the Manual Actions report.
Does the number of pages in this report matter?
Only as a proportion, and only for pages you wanted indexed. Large sites always have a long tail here. A small site with most of its pages listed has a real problem.
Can a page recover from this on its own?
Yes, and it frequently does, particularly for newer pages and as a site earns more links. The word "currently" in the status is doing real work.
Should I delete pages that will not index?
Not automatically. Consolidate them into a stronger page and redirect, or improve them. Deleting is right only when a page has no purpose for readers either.
The short version
Google crawled the page and decided it was not worth storing. That is a judgement about the page, so the fix is the page: make it substantively better, link to it properly from content that is already indexed, and make sure nothing technical is blocking it.
Then request indexing once, and give it a few weeks. Resubmitting an unchanged page is the most common wasted effort in SEO, and it is the one thing that reliably does nothing at all.