Discovered, currently not indexed: why Google skips pages and how to fix it
Discovered, currently not indexed: why Google finds pages and skips them, what the crawled status means, and the fixes that actually work.
These are the two most common reasons pages sit outside Google's index, and they are the two most misunderstood. Neither is an error in the usual sense. Nothing is blocking Google. Google has decided, for now, that the pages are not worth crawling or not worth indexing.
That is the uncomfortable part, and it is also useful, because it means the fix is almost never a technical switch. It is making the pages easier to reach and more clearly worth including. Requesting indexing over and over does not change that decision.
The difference between the two statuses
The two statuses describe different stages, and the fixes follow from which stage a page is stuck at.
| Status | Google has… | It usually means |
|---|---|---|
| Discovered, currently not indexed | Found the URL, from a link or sitemap, but not crawled it yet | Crawling was deprioritised: too many URLs, too few signals the page matters, or a slow server |
| Crawled, currently not indexed | Fetched and read the page, then chose not to index it | Google saw the content and did not consider it valuable or distinct enough to include |
Discovered, currently not indexed: a crawl priority problem
Google's own explanation is that it wanted to crawl the URL but rescheduled because crawling then might have overloaded the site. That happens, particularly with slow servers, but on most sites the larger cause is priority. Google has more URLs from your site than it is willing to crawl right now, and these ones did not make the cut.
Three things drive that. The number of URLs your site exposes: if filters, parameters and pagination generate tens of thousands of URLs, your real pages compete with all of them. How strongly each page is linked: a page linked only from an XML sitemap, or reachable only through several clicks of pagination, reads as unimportant. And site-level quality: if a large share of what Google has already crawled on your site turned out thin or duplicate, it becomes more conservative about crawling the rest.
Reduce the URLs competing for attention
Stop generating and linking crawlable filter, sort and session URLs. This is often the single largest fix on ecommerce sites.
Link the pages from pages Google already crawls
Add the stuck pages to category pages, hub pages and related-content modules that are indexed and linked from your navigation. A sitemap entry alone is a weak signal.
Check server response times
The Crawl stats report in Search Console shows average response time and whether Google hit errors. Consistently slow responses cause Google to crawl less.
Crawled, currently not indexed: a value problem
This status means Google has already read the page. Access and discovery are not the problem. Google looked at the content and decided the index is not better for including it, at least for now. Pages can move in and out of this status over time without any change on your side.
The common causes are consistent. Pages that are thin, such as a product with a one-line manufacturer description shared by every other retailer. Pages that are near-duplicates of each other, such as location pages that differ only by the city name. Pages whose main content only appears after JavaScript runs, so the crawled version looks empty. And pages that answer nothing a searcher would ask. Soft 404s belong here too: an empty category or out-of-stock page with little content can look like an error page to Google.
Check the crawled version first with the URL Inspection tool, and view the crawled HTML and the screenshot. If the content is missing there, you have a rendering problem, not a quality problem. If the content is present, compare the page honestly with what currently ranks for its topic. The fix is usually to consolidate weak pages into fewer stronger ones, or to add the substance that makes the page worth indexing: specifications, original descriptions, genuine answers.
What does not work
Repeatedly clicking Request Indexing. It has a daily quota, it may trigger a crawl, and it does not change whether Google decides the page is worth indexing. If the underlying reason has not changed, the page drops back.
Resubmitting the sitemap. Google already knows about the URLs. That is why they appear as discovered.
Third-party "instant indexing" services. Google's Indexing API is officially limited to job posting and livestream pages, and services that push other page types through it are working outside that scope. Even when a page gets crawled this way, Google still applies the same judgement about whether to keep it.
When it is fine to leave pages unindexed
Not every page should be indexed, and a non-zero count in these statuses is normal on any site. Pagination beyond the first few pages, tag archives, filtered listings and old low-value posts sitting here is often Google making a reasonable decision.
Look at which pages are affected, not how many. Filter the report by your sitemap. If the stuck URLs are core products, services or articles you care about, act. If they are pages you would not miss from search results, noindex or remove them yourself, which tidies the report and concentrates crawling on the pages that matter.
Common questions
How long do pages stay in "Discovered, currently not indexed"?
There is no fixed timeline, which is part of what makes the status frustrating. On a healthy site with good internal linking, newly discovered pages typically get crawled within days to a few weeks. Pages that sit in this status for months have usually been deprioritised rather than merely queued, and they will not move until something about their priority changes. The signals that change it are the ones described in this guide: fewer competing low-value URLs, stronger internal links from pages Google already crawls regularly, and a server that responds quickly and reliably. New sites and sites with little external linking also see longer delays across the board, because Google has less evidence the site is worth crawling heavily. If a whole section is stuck, look at site-wide causes first. If only a handful of pages are stuck while their siblings index normally, those pages are probably weaker or less linked than the others.
Is "Crawled, currently not indexed" a penalty?
No. A penalty, or manual action, is a separate thing reported in its own section of Search Console and applied by a human reviewer for a policy violation. "Crawled, currently not indexed" is an algorithmic decision about individual pages: Google fetched them and chose not to include them in the index for now. It carries no sanction against the rest of your site, and pages can move out of the status on a later crawl without you doing anything. That said, a large and growing number of pages in this status is a meaningful quality signal about your site. It usually means Google is finding a lot of content it considers thin, duplicated or unhelpful. If that describes a large share of your site, it can make Google more conservative about crawling and indexing your other pages too, so treat a high count as a content quality problem to address rather than as noise in a report.
Will adding pages to my XML sitemap get them indexed?
It will get them discovered, and discovery is rarely the problem. A sitemap tells Google a URL exists and, through the lastmod date, when it last changed. It does not tell Google the page is important, and it does not override Google's judgement about whether the page is worth crawling or indexing. That is why pages submitted in a sitemap so often sit in "Discovered, currently not indexed": Google received the list and has not prioritised it. Sitemaps are still worth maintaining carefully. They should list only canonical, indexable URLs that return 200, because a sitemap full of redirects, noindexed pages and duplicates teaches Google to trust it less. Keep lastmod accurate rather than updating it on every build, because a date that changes without content changing is a signal Google learns to ignore. Then put the effort into internal linking, which is the stronger signal of importance.
Services related to this guide
Tell us about your site
A written audit of crawling, indexing, rendering, Core Web Vitals, internal linking and structured data, built from a full crawl plus your Search Console data, with each fix ranked by impact and effort.