Discovered - currently not indexed: causes and fixes
Google knows the URL but has not crawled it yet. Why it happens, when it is a real problem, and the steps that get pages crawled.
Updated
Discovered - currently not indexed means Google knows the URL exists, usually from a link or your sitemap, but has not crawled it yet. Google has not read the page, so it has not judged the content. The page is in a queue, and the work is to make Google want to crawl it sooner.
| Where it shows | Indexing, then Pages, under “Why pages aren’t indexed” |
|---|---|
| Did Google crawl it? | No; the last crawl date is empty |
| Is it a problem? | Short term, usually not; for weeks on key pages, yes |
| Typical fix | Better internal links, fewer junk URLs, a faster server |
What does “Discovered - currently not indexed” mean?
Google’s help page says the page was found but not crawled yet, and that typically Google wanted to crawl it but expected that doing so would overload the site, so it rescheduled the crawl. In plain words: Google decided other URLs, or your server’s capacity, came first.
It is the step before Crawled - currently not indexed. If Google crawls the page and still declines it, it will move there.
Is it a problem?
For brand-new pages, no: it can be a normal stop on the way to being indexed. For a handful of filter or parameter URLs, no. It is a problem when important pages stay here for weeks, or when thousands of URLs pile up, because that usually means Google is spending its visits elsewhere.
What causes it, most likely first?
- Weak internal links. The pages are linked only from the sitemap or deep pagination, so Google gives them low priority.
- Too many low-value URLs. Faceted navigation, tracking parameters, calendars and tag pages create far more URLs than real pages, and Google discovers them faster than it is willing to crawl them.
- Server limits. Slow responses, timeouts and 5xx or 429 errors make Google lower its crawl rate (see Server error (5xx)).
- A new or low-trust site. Google crawls less of a site it knows little about, so new sites see this more.
- Mass publishing. Thousands of pages published at once, especially similar ones, get queued.
How do I fix “Discovered - currently not indexed”?
1. Look at which URLs are waiting
Open the reason in the Page indexing report and scan the example URLs. Parameter URLs, filters, session IDs and endless archives point to a crawl trap. Real, important pages point to weak linking or low priority.
2. Stop crawl traps from soaking up crawling
If the list is full of URL variations, block those patterns in robots.txt (for example faceted filters or internal search), stop linking to them, and keep them out of the sitemap. That frees Googlebot's visits for the pages that matter.
3. Link to important pages from indexed pages
Add links to each waiting page from your menu, a category page, or two or three related pages that are already indexed. Pages reachable in a few clicks from the homepage get crawled sooner than pages found only in a sitemap.
4. Check server speed and errors
Open Settings, then Crawl stats. Slow average response times, or 5xx and 429 responses, make Google crawl less. Fix the server or hosting limits that cause them.
5. Keep the sitemap clean and accurate
List only canonical, indexable URLs that return 200, with lastmod dates that change only when the content does. Remove redirected, noindexed and deleted URLs.
6. Request indexing for the few pages that matter most
Use URL Inspection and Request indexing for your most important waiting pages. There is a daily limit, so save it for pages that count, and use Validate fix in the report for the group.
How do I check that the fix worked?
In URL Inspection, a crawled page shows a last crawl date and moves to “URL is on Google” or to another reason. In the Page indexing report, click Validate fix on this reason and watch it move from Started to Looking good and Passed. Crawl stats (Settings, then Crawl stats) also show whether total crawl requests rise after you cut junk URLs.
How long does it take?
Individual requested pages are often crawled within days. Clearing a large backlog by fixing links and crawl traps takes longer, typically weeks, and depends on how many URLs Google has queued. Google says validation can take up to about two weeks or more.
Test your robots.txt rules for the URL patterns you plan to block with the robots.txt tester, and read more about crawl budget and internal linking.
Sources
Common questions
Why is the last crawl date empty?
Because Google has not crawled the page yet. Google's help page says that when it wanted to crawl the URL but expected it to overload the site, it rescheduled the crawl, which is why the last crawl date is empty in the report.
Is this a crawl budget problem?
On large sites with many URL variations, often yes. On a site with a few hundred or a few thousand pages, it rarely is. There it usually means Google sees the pages as low priority because few pages link to them or similar pages were not worth indexing.
Will submitting a sitemap fix it?
A sitemap tells Google the URL exists, which is how many of these pages were discovered in the first place. It does not make Google crawl them sooner if it considers them low priority. Internal links do more.
Can AI tools still see these pages?
AI search features that use Google's index, such as AI Overviews, need the page indexed. Other assistants run their own crawlers, so a page can be read by them while it waits in Google. Check which AI crawlers your robots.txt allows with the AI crawler checker.