Discovered currently not indexed is the quieter sibling of the statuses that get all the attention. Nothing is broken. The page returns 200, it is in the sitemap, and there is no noindex on it. Google simply has the address on a list and has not visited. The usual advice is to be patient. That advice is half right, and the half that is wrong costs months.
What discovered currently not indexed means
Google’s Page indexing report defines the status in one line: “The page was found by Google, but not crawled yet.” Found means Google picked up the URL somewhere, from a link, a sitemap or a redirect. Not crawled means Googlebot has not requested it, so Google has no idea what is on the page.
That distinction decides where you look for the fix. A page Google has never fetched cannot have been rejected for thin content, a weak title or poor writing. Rewriting the copy on an uncrawled page changes nothing Google can see. The problem sits one level up: in how the URL was found, how it is linked, and how many other URLs it is competing with for Google’s attention.
Where it sits among the page-indexing statuses
The report lists many reasons a page is not indexed. Most fall into three groups: Google could not get the page, Google chose another URL, or Google did not want the page. Discovered is the odd one out, because Google has not tried yet.
| Status | Google’s description | Has Google fetched it? |
|---|---|---|
| Discovered – currently not indexed | “The page was found by Google, but not crawled yet.” | No |
| Crawled – currently not indexed | “The page was crawled by Google but not indexed.” | Yes |
| Duplicate without user-selected canonical | “Google has chosen the other page as the canonical for this page.” | Yes |
| Server error (5xx) | “Your server returned a 500-level error when the page was requested.” | Tried and failed |
| URL blocked by robots.txt | “This page was blocked by your site’s robots.txt file.” | Not allowed to |
The closest neighbour is crawled, currently not indexed, and the two are routinely treated as one problem. They are not. Crawled means Google read the page and passed on it, which is a quality question. Discovered means Google never got as far as reading it, which is a crawl-priority question. If your pages have moved from discovered to crawled, that is progress, even though both sit in the same “not indexed” column.
Can the status last forever?
Yes, and Google has said so. As reported by Search Engine Journal, in February 2022, Google’s John Mueller said the status “can be forever. It’s something where we just don’t crawl and index all pages.”
That line deserves more weight than it gets. The common assumption is that discovered is a waiting room and every URL eventually gets called. Mueller describes something closer to a ceiling: Google decides how much of a site is worth crawling, and URLs below that line can sit there indefinitely. His suggested remedy was not a technical trick. He said to “continue working on the website and making sure that our systems recognize that there’s value in crawling and indexing more and then over time we will crawl and index more.”
Read plainly, that means the size of the discovered pile is partly a measure of how much Google trusts the site as a whole. A site that publishes a thousand URLs and has earned attention for two hundred of them will show the rest here, however good the individual pages are.
How to fix discovered currently not indexed
You cannot force a crawl at scale. You can make each crawl cheaper, make the important URLs easier to find, and remove the URLs that are diluting Google’s attention. Four levers do most of the work.
- Internal links from pages Google already crawls. A URL that only appears in the sitemap is a weak candidate. Link to it from indexed, frequently crawled pages such as the homepage, category hubs and strong articles. Our guide to internal linking covers where those links do the most good, and orphan pages explains how to find URLs with no internal links at all.
- A clean sitemap. List only canonical, indexable URLs that return 200. A sitemap padded with redirects, noindexed pages and parameter variants tells Google your list is unreliable.
- Server speed. If pages are slow to respond, Google has a reason to crawl fewer of them. Fix response times before anything else on large sites.
- Fewer low-value URLs. Faceted filters, tag archives, session parameters and auto-generated pages can multiply a few hundred real pages into thousands of crawlable ones. Every one of them competes for the same attention.
The fourth lever is usually the biggest and the least used. Most site owners try to pull more URLs into the index; the faster route is often to push junk out of the crawl path. Our post on crawl budget sets out when this matters and when it does not. On a site with a few dozen pages, crawl capacity is rarely the issue, and a long discovered list there usually points to weak internal linking or a very new domain.
Triage before you fix. Export the discovered URLs and sort them by path. If most belong to one template, such as filter combinations or paginated archives, decide whether that template should be crawlable at all. If they are your newest articles, the answer is links and time. If they are your most important commercial pages, that is the signal to act on the four levers first.
What to stop doing, and what the report cannot tell you
Stop pressing Request Indexing on hundreds of URLs one by one. It is a tool for a handful of important pages, not a substitute for a site Google wants to crawl. Stop rewriting pages that Google has not fetched; it cannot see the changes. And stop reading a growing discovered count as a penalty. It is a priority signal, not a sanction.
The limitation is real. The report tells you a URL is waiting, not why it was ranked below the line, and Google does not publish how it sets crawl priority for a site. You can change the inputs Mueller points to and watch the count over weeks, but you cannot prove which change moved it. Change one thing at a time where you can.
Once pages do get crawled, some will land in other statuses. Duplicates go to duplicate without user-selected canonical, and deliberate variants should show as alternate page with proper canonical tag. Neither of those is a crawl problem, so do not treat them with the fixes above.
Frequently asked questions
Is discovered, currently not indexed a penalty?
No. It means Google found the URL but has not crawled it. It reflects crawl priority, not a sanction against the page or the site.
How long does discovered, currently not indexed last?
There is no fixed time. John Mueller has said it “can be forever”, because Google does not crawl and index every page it finds.
Will improving the content fix it?
Not directly. Google has not fetched the page, so it cannot see the content. Internal links, a clean sitemap, a faster server and fewer low-value URLs are the levers that work.
Should I use Validate fix for this status?
Only after you have changed something, such as adding internal links or cutting low-value URLs. Validation asks Google to recheck; it does not raise crawl priority on its own.
The takeaway Discovered means queued, not judged. Make the important URLs easy to reach, make crawling cheap, and cut the URLs that should never have been in the queue.
