Crawled currently not indexed is the status that sends site owners hunting for a bug that is not there. The page returns 200, it is in the sitemap, it is not blocked, and still it sits in the “not indexed” column. The instinct is to press Request Indexing and wait. Google’s own documentation says that is pointless, and the reason why tells you what to do instead.
What crawled currently not indexed means
Search Console Help’s Page indexing report documentation defines the status in two sentences: “The page was crawled by Google but not indexed. It may or may not be indexed in the future; no need to resubmit this URL for crawling.”
Read that carefully. Google has already seen the page. Crawling succeeded. The decision not to index was made after reading the content, which makes it a decision about value, not about access. Nothing in the definition points at robots rules, server errors or canonical tags, because those have their own statuses in the same report.
The second sentence matters as much. “May or may not be indexed in the future” means the status is not permanent, and “no need to resubmit” means asking again does not change the assessment. If the page is unchanged, the answer is likely to be unchanged.
Crawled vs discovered: two different problems
Its neighbour in the report is often confused with it, and the fixes are not the same. Google describes “Discovered – currently not indexed” this way: “The page was found by Google, but not crawled yet. Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl.” The report shows an empty last-crawl date for these URLs.
| Crawled – currently not indexed | Discovered – currently not indexed | |
|---|---|---|
| Has Google fetched the page? | Yes | No; last crawl date is empty |
| Google’s stated reason | None given; crawled but not indexed | Crawl rescheduled because it was expected to overload the site |
| What it usually signals | A judgement about the page’s value | Crawl capacity, or too many low-value URLs competing for it |
| Resubmitting helps? | Google says there is no need | Rarely; the queue is the problem |
| Where the fix lives | The page itself and its place in the site | Server response and the number of URLs you expose |
The practical difference: discovered is a queue problem, crawled is a quality problem. Treat them as one and you will spend a week tuning server caching for pages Google has already read and rejected.
Why Google declines a page it has crawled
Google does not give a reason per URL. Anyone who tells you exactly why a specific page was excluded is guessing. What you can do is look for patterns across the excluded set, because they are usually obvious once the list is exported and sorted by URL path.
The patterns that turn up most:
- Thin archives. Tag pages, date archives and paginated category pages that list the same posts in a different order.
- Near-duplicates. Location or product variants where only a word or two changes between pages.
- Pages that answer nothing new. A post that restates what already ranks, with no added data, angle or experience.
- Orphans. Pages reachable only through the sitemap, with no internal links telling Google they matter to you.
If the excluded URLs are mostly in one of those groups, you have your diagnosis. If they are your best articles, the problem is more likely the site as a whole, and that is a slower fix.
The crawled currently not indexed fix
Start by deciding which excluded pages deserve to be indexed at all. Many do not. A tag archive that Google ignores is not a loss, and noindexing or removing it reduces the pile of low-value URLs the crawler has to work through. Our guide to content pruning covers that decision.
For the pages you want indexed, work through these in order:
- Make the page earn its place. Add what the ranking pages lack: a table, a worked example, first-hand detail. If you cannot add anything, merge it into a stronger page.
- Consolidate duplicates. If two pages compete for the same intent, pick one. Our post on keyword cannibalization sets out the five ways to do it.
- Link to it from pages Google already values. An internal link from an indexed, well-linked page is the clearest signal you can send that the page matters.
- Then wait for a recrawl. Change the page meaningfully first; resubmitting an unchanged URL repeats a question Google has answered.
How to fix discovered currently not indexed
Discovered URLs are waiting in a queue Google has slowed down on purpose, so the job is to make crawling cheaper and the queue shorter. Check server response times first; if pages are slow to return, Google has a reason to hold back. Then count how many URLs your site exposes. Faceted navigation, session parameters and auto-generated archives can multiply a few hundred real pages into tens of thousands of crawlable ones.
Cutting those URLs, through noindex, removal or not linking to parameter combinations, often clears the discovered backlog without touching the pages you care about. A sitemap that lists only the pages you want indexed helps Google spend its visits well.
What the status cannot tell you
The limitation is the one Google builds into the report: it states what happened, not why. A URL marked crawled but not indexed might be thin, might be a near-duplicate, or might be a reasonable page on a site Google has not yet decided to trust with more index space. The report cannot separate those, so change one thing at a time and watch the counts over several weeks rather than days.
It helps to compare yourself with sites that clearly do get indexed. In the database explorer, filter to your niche and sort by estimated traffic, then look at how the leaders structure a topic: how many pages they publish on it, how those pages link to each other, and whether they keep tag and date archives at all. That is method, not proof, but it shows what an indexable site in your space looks like. Our guide to internal linking covers the linking side in more depth, and if you are still waiting for a brand-new site to appear, how to get a website indexed by Google covers the request process and timings.
A new site will usually see more of this status than an established one. That is not a penalty. It is Google rationing attention until the site has shown it publishes pages worth keeping.
Frequently asked questions
Should I request indexing for crawled, currently not indexed pages?
Not for an unchanged page. Google’s documentation says there is no need to resubmit these URLs. Improve the page or its internal links first, then let Google recrawl it.
What is the difference between crawled and discovered currently not indexed?
Crawled means Google fetched the page and chose not to index it. Discovered means Google knows the URL but has not crawled it yet, typically because crawling was expected to overload the site.
Does Google tell you why a page was not indexed?
No. The Page indexing report gives the status, not a per-URL reason. Look for patterns across the excluded URLs instead.
Is crawled, currently not indexed permanent?
No. Google says the page may or may not be indexed in the future. Pages that are improved and better linked often move into the index on a later crawl.
The takeaway Crawled means judged; discovered means queued. Improve, merge or remove the crawled pages, and cut the URL count and server load for the discovered ones.
