Crawled, currently not indexed
not indexed / discovered currently not indexed / page indexing report / indexing status
Crawled, currently not indexed is a Search Console status meaning Google fetched a page and chose not to index it. Google says it may or may not be indexed later and that there is no need to resubmit the URL. Discovered, currently not indexed is different: Google has not fetched it yet.
Google's own wording is short and does most of the work. The page was crawled by Google but not indexed. It may or may not be indexed in the future, and there is no need to resubmit the URL for crawling. Read that last clause twice, because it rules out the thing most people do next.
The status it gets confused with is the one directly above it in the same report. Discovered, currently not indexed means the page was found but has not been crawled yet. Google explains why in plain terms: typically it wanted to crawl the URL, but that was expected to overload the site, so the crawl was rescheduled. That is also why the last crawl date is blank on those rows. One status says Google looked and passed. The other says Google has not looked.
A third entry is worth knowing because it looks like a fault and is not. For pages listed as duplicate without user-selected canonical, Google says it has chosen another page as the canonical and will not serve this one, and then says outright that this is not an error but is working as intended, because Google does not serve duplicate pages.
Bing describes the mechanism that makes the queue slow, from the other side. It says duplicate and near-duplicate URLs slow down discovery and indexing, because crawlers may spend time revisiting duplicate or low-value URLs instead of finding new or updated content, and that this can delay when new pages are discovered and indexed at all.
In practice
A batch of pages arrives from a content order and most of them land in this status. The instinct is to resubmit them, which Google has explicitly said is unnecessary. The status is not a queue position. It is feedback. Google fetched those pages, considered them, and declined, and doing the same thing again with the same pages gets the same answer.
Not the same as
- An error or a penalty
- Nothing is broken. Google says of the related duplicate status that it is working as intended.
- noindex
- That is your instruction to leave a page out. This is Google's decision, and it can change on its own.
Why it matters to you
Indexing services are sold on this status, and the platform's own documentation says resubmission is not the answer. That leaves the useful question, which is harder and cheaper: what would make this page worth indexing. Bing's point sharpens it, because a site full of thin or near-identical pages consumes the crawling that new pages need. The pages you wish were indexed are competing with the pages you should not have published.
What to ask or check
- 01Is the status crawled and not indexed, or discovered and not crawled, which are different problems?
- 02What does each affected page offer that an already-indexed page does not?
- 03Is anyone proposing to resubmit URLs, which Google says is not needed?
What people get wrong
That the page is stuck in a queue and needs resubmitting. Google says there is no need to resubmit the URL, and that it may or may not be indexed in the future.
Red flags
- A proposal to fix this by resubmitting URLs or pinging an indexing service.
- The two statuses treated as one problem, when one means Google looked and the other means it has not.
- A large batch of new pages landing in this status at once, which is feedback about the batch.
Where you will see it
In the page indexing report in Search Console, usually after a site migration or a bulk content order.