“Discovered – currently not indexed” means Google has found the URL but has not crawled it yet, so it cannot be indexed. Search Console's help says Google typically wanted to crawl the page but expected the visit to overload the site, so it rescheduled. The fix is to make the page worth crawling sooner: link to it internally, list it in your sitemap, request indexing, and cut low-value URLs.
What does discovered currently not indexed mean in Search Console?
It means Google knows the address exists but has not fetched the page. The page has not been judged and rejected; it has simply not been visited yet.
Google's Page indexing report help page describes the status in one line: “The page was found by Google, but not crawled yet.” It goes on: “Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl. This is why the last crawl date is empty on the report.”
That empty last crawl date is the useful clue: you are looking at a scheduling problem, not a content verdict.
The same help page reminds site owners that “Not indexed is not necessarily bad”. The first job is to check whether the pages in the list are ones you actually care about.
How is it different from crawled currently not indexed?
The difference is where the page stopped. “Discovered” stopped before the crawl; “crawled – currently not indexed” was fetched and then not added to the index.
Google's crawl budget guide explains why a crawl is not the finish line: “not every page that is crawled will necessarily be indexed. After crawling, each page must be evaluated, consolidated, and assessed to determine its suitability for the index.”
| Status | Has Google fetched the page? | Where the problem usually sits | What we check first |
|---|---|---|---|
| Discovered – currently not indexed | No. The last crawl date is empty. | Crawl scheduling: how easily Google can find and reach the page, and how many other URLs compete for its time | Internal links, sitemap entries, duplicate and low-value URLs, server responses |
| Crawled – currently not indexed | Yes. | The evaluation after crawling: whether the page earns a place in the index | Whether the page duplicates another, how much unique substance it carries, and which URL is canonical |
| URL is unknown to Google (URL Inspection) | No, and Google has not seen the address either | Discovery: nothing points Google to the page | Whether the page is linked from anywhere or listed in a sitemap |
The third row comes from the URL Inspection tool help page: “URL is unknown to Google” means Google has not seen the URL before. A discovered page is one step further along.
Why does Google leave pages discovered but not crawled?
Because crawling is rationed. Google says it cannot fetch everything it knows about, so each site gets a share of its time, and your less important URLs can wait a long while.
The crawl budget guide puts it bluntly: “The web is a nearly infinite space, exceeding Google's ability to explore every publicly accessible URL.” A site's crawl budget, it says, is determined by two elements: crawl capacity limit and crawl demand.
Two more lines from that guide explain how sites make it worse for themselves. “Without guidance from you, Google tries to crawl all or most of the URLs that it knows about on your site.” And if many of those URLs are duplicates or unimportant, “this wastes a lot of Google crawling time on your site.” Filtered listings, tag archives and tracking-parameter variants all compete with your new article.
The guide also says that if your pages seem to be crawled the same day they are published, you do not need to read it; its intended readers include sites with a large portion of their URLs in this status. On a small site with a handful of such URLs, we look at linking and server responses before crawl budget.
How do you fix discovered currently not indexed?
Work through the fixes Google's own documentation supports, in this order.
- Confirm the page matters. Sort the report's URL list into pages you want in search and pages you do not. Google's help page says it is fine for a URL not to be indexed for the right reasons, such as a duplicate, a noindex tag or a removed page. Only the first group needs work.
- Link to it from pages Google already crawls. Google's link guidance says every page you care about should have a link from at least one other page on your site. Add a contextual link from a related, indexed page.
- Use real, crawlable links with descriptive anchor text. Google says it can generally only crawl a link that is an <a> element with an href attribute.
- List the URL in an up-to-date sitemap. Include the URLs you want in search, keep the lastmod date accurate, and submit the sitemap in Search Console.
- Request indexing for your most important URLs. Use the URL Inspection tool on the handful of pages that matter most, not the whole list.
- Reduce the low-value URLs competing for crawl time. Stop generating duplicate and near-empty URLs, and keep them out of your sitemap and internal links.
- Check the server answers crawlers cleanly. Google holds back when a crawl is expected to overload the site, so we check server logs for slow responses and 429 or 503 errors.
Does internal linking help pages get crawled?
Yes. Links are how Google finds new pages.
Google's link best practices say “Google uses links as a signal when determining the relevancy of pages and to find new pages to crawl.” The same page says links are crawlable when JavaScript inserts them dynamically, as long as the result is a normal <a href> element, and that good anchor text is descriptive, reasonably concise and relevant to both pages.
The practical checklist we use on a discovered-but-not-crawled page:
- Is it linked from at least one indexed page with related content?
- Is the link an <a href> in the HTML, not a script-driven click?
- Does the anchor text say what the page is about, rather than “read more”?
- Do internal links point at the canonical URL, not a parameter or tracking variant?
New blog posts are the usual case: a post that appears only deep in an archive and in the sitemap waits in the queue. Linking it from related, established posts gives Google a path from pages it already visits.
Do sitemaps and request indexing fix it?
They help, but neither is a guarantee. Both are signals that tell Google which URLs you want crawled; neither forces a crawl.
Google's sitemap documentation says to include the URLs you want to see in search results, and that submitting a sitemap “is merely a hint: it doesn't guarantee that Google will download the sitemap or use the sitemap for crawling URLs on the site.” It also says Google ignores <priority> and <changefreq> values, and uses <lastmod> only if it is consistently and verifiably accurate. A single sitemap is limited to 50,000 URLs or 50MB uncompressed; beyond that you split it.
So a sitemap full of redirected or duplicate URLs undermines itself, and stamping today's date on every lastmod makes the field untrustworthy.
Request indexing, in the URL Inspection tool, lets you ask Google to crawl a specific URL. The help page notes a daily limit of inspection requests for each property, and that the results shown come from the most recently indexed version, not the live page. Use it for the few pages that matter most, after the links and sitemap are right, not as a bulk fix.
Once the cause is fixed, start validation in the Page indexing report. Google's help says validation typically takes up to about two weeks, and in some cases much longer.
When should you stop worrying about it?
When every page you would be upset to lose from search is indexed, and what remains in the list is filters, archives and parameter variants. Google's help is explicit that not every URL should be indexed.
Google Search is one half of being found. If your pages also need to be cited by ChatGPT, Claude or Perplexity, those platforms send their own crawlers, which a firewall can block while Googlebot gets through. Our free AI visibility checker reads robots.txt rules for 11 AI crawlers and requests your homepage once with each crawler's user agent. That is the checker's own request, not the real crawler's, and it covers the homepage only, so treat it as a first look rather than proof of access.
If you would rather have indexing reports read, internal links added and sitemaps kept clean every month, that is part of what SEO Autopilot covers: managed SEO and AI search visibility for one site at ₹20,000 a month (about US$230), no setup fee and no minimum term. For more on the AI side of crawl access, see how firewalls block AI crawlers and our guide to LLM SEO.
Frequently Asked Questions
How long does discovered currently not indexed last?
The help page we link gives no timeframe for the status itself. Once you have fixed the cause and started validation, Google says validation typically takes up to about two weeks, and sometimes much longer.
Is discovered currently not indexed bad?
Not always. Google's help says not indexed is not necessarily bad and that you should not expect every URL to be indexed. It matters only if the URLs in the list are pages you want people to find in search.
Should I request indexing for every discovered page?
No. The URL Inspection tool has a daily limit of inspection requests per property. Use it for your most important pages after fixing internal links and your sitemap, and let those fixes do the work for the rest.
What is the difference between discovered and crawled currently not indexed?
Discovered means Google knows the URL but has not fetched it, so the last crawl date is empty. Crawled means Google fetched the page and then did not add it to the index, which points to the evaluation after crawling rather than to crawl scheduling.
Does a sitemap guarantee Google will crawl my page?
No. Google's sitemap documentation calls submitting a sitemap merely a hint that does not guarantee Google will download it or use it for crawling. It still helps, provided it lists only URLs you want indexed and keeps lastmod accurate.