How to Fix “Discovered – Currently Not Indexed”
This status makes many site owners panic, but it simply means Google knows your page exists and has not visited it yet. Sometimes that needs no action, and sometimes it points to a real problem. This guide explains the status, the true causes, how to tell which one you have, and the exact steps to fix it.
- What the status means
- Five real causes
- Fix plan in order
- When to just wait
Illustration of the report row.
“Discovered – currently not indexed” means Google found the URL, usually through a sitemap or a link, but has not crawled it. Google says it likely postponed the crawl so it would not overload your server. The usual fix is to make sure your server is healthy and the page is well linked internally, then give it time.
What the status means
The Page indexing report sorts every URL Google knows about. For this status, Google has the address but has not fetched the page. The page has not been judged yet, so this is different from being rejected. The status carries no penalty and says nothing about page quality, because Google has not looked at the page.
Discovered
Google learned the URL exists. You are here.
Crawled
Googlebot fetches the page.
Indexed
Google stores it.
Ranking
It can appear in results.
Is it actually a problem?
Not always. Google’s guidance says the fix is usually none, apart from checking that your server can handle the load and the page is well linked. Use this table to judge your situation.
| Your situation | Verdict | Action |
|---|---|---|
| Page published in the last few days | Normal | Wait, and make sure it is linked |
| A few unimportant URLs | Usually fine | Ignore or clean them up |
| Key pages stuck for weeks | Worth investigating | Follow the fix plan |
| A large share of your site | Real issue | Check server, duplicates, quality |
The five real causes
Server could not cope
Google slows crawling when a site is slow, returns server errors or sends rate-limit signals such as 429.
- signs
- 5xx errors, slow responses
- fix
- Upgrade hosting or caching, check firewall
Weak internal links
A page buried deep or linked from nowhere looks unimportant.
- signs
- No links from other pages
- fix
- Link from strong pages. See internal link audit
Low crawl demand
New or low-popularity sites get crawled less. Demand rises with popularity and freshness.
- signs
- Young domain, few links
- fix
- Earn links, publish useful content, wait
Too many unwanted URLs
Duplicates, filters and parameter URLs inflate the list Google tries to crawl.
- signs
- Thousands of near-identical URLs
- fix
- Consolidate. See duplicate content
Messy sitemap
A sitemap packed with redirects, 404s and noindex URLs wastes Google’s attention and signals low care.
- signs
- Sitemap lists URLs that redirect or error
- fix
- List only canonical, indexable pages. See sitemap guide
Diagnose in five minutes
Open the status and view examples
Go to Indexing, Pages, click the status. Note whether the pages are important and what they have in common.
Run URL Inspection and a live test
Confirm the page loads and is not blocked. See request indexing.
Open Settings, Crawl stats
Look at host status and response times for failures. Google points to this report for server problems.
Is the page linked from your site?
Open Links, then Internal links, and look for the page.
Does it list only good URLs?
Remove redirected, noindex and missing pages from the list.
The fix plan, in priority order
Make the server healthy
Fix 5xx errors, speed up slow responses, and make sure no security rule blocks Googlebot. Read how to speed up WordPress.
Link to the pages internally
Add descriptive links from your homepage and best pages. Every important page needs at least one internal link.
Clean the URL inventory
Consolidate duplicates, return 404 or 410 for permanently removed pages, avoid long redirect chains and fix soft 404s.
Tidy the sitemap
Keep it current, list only pages you want indexed, and use accurate lastmod dates.
Improve the pages
Make each page clearly useful and different from the others on your site.
Request indexing for a few key URLs
Only once, only for important pages, only after the fixes above.
Do not remove noindex-free pages or delete content in a panic. Google also says you should not use robots.txt to free up crawl for other pages unless you are hitting your capacity limit, and noindex does not stop crawling, so neither is a crawl-saving tool.
Discovered vs Crawled: not the same
| Discovered – currently not indexed | Crawled – currently not indexed | |
|---|---|---|
| Google visited? | No | Yes |
| Main issue | Crawl scheduling, links, server | Quality, duplication, value |
| Typical fix | Links, server, wait | Improve content |
| Guide | This page | Crawled guide |
Validate and wait
After fixing, open the status and click “Validate fix” once. Google checks sample pages first, then rechecks the rest, which can take up to about two weeks or longer. Each URL is marked Pending, Passed or Failed. If validation fails, fix the named problem and start a new validation after the cycle ends. For how to confirm indexing afterwards, see checking if your site is indexed.
Mistakes to avoid
Resubmitting daily
It does not speed up a crawl.
Deleting pages in panic
The status is not a penalty.
Blocking URLs to save crawl
It rarely frees capacity for other pages.
Publishing thin filler
More low-value URLs make it worse.
Discovered, not indexed: questions
Is this status a penalty?
No. Google simply has not crawled the page yet, so it has not judged it.
How long does it last?
It varies from days to months, depending on your server, links and how much Google wants to crawl the site.
Will Request indexing fix it?
It can prompt a crawl for one URL, but it will not solve the underlying cause. Fix the cause first.
Why do new sites see it so much?
Google is cautious with new sites and crawls them slowly until trust and demand grow.
Can duplicate URLs cause it?
Yes. Many near-identical URLs waste crawl attention.
Should I noindex these pages?
Only if you truly do not want them in Google. Noindex does not save crawling.
Does it affect my other pages?
Not directly, but a slow server that causes it can slow crawling of the whole site.
The five-cause grouping and the fix order are my own practical framework built on those sources.