Discovered, currently not indexed: what it means and how to fix it
By James Burfield, SEO Consultant at SEOBurf. Updated 21 October 2026.
“Discovered, currently not indexed” is Google’s label for a page it says it knows about, usually from the sitemap or a link, and says it hasn’t crawled yet. Google’s own explanation is timing: it wanted to crawl the URL but expected that to overload the site, so it put the crawl off. On a small site Googlebot rarely visits, overload is an unlikely reason. On the site we tested, Request indexing is what got pages crawled, one at a time. What changes the site as a whole is links: from your own pages that Google already crawls, and from other sites.
What Google says it means
In the Page indexing report, Google describes the state as The page was found by Google, but not crawled yet
(Search Console Help). It adds that this usually happens because crawling at that moment was expected to overload the site, so the crawl was rescheduled, and that this is why the page’s last crawl date is blank.
Two things follow. Google has the URL already, so submitting it again tells Google nothing new. And by Google’s description it hasn’t read the page, so it hasn’t judged the content either.
What it usually means on a small site
This part is our reading of the evidence; Google doesn’t say it. Google’s explanation is about capacity: how much crawling a server can take. That fits a large site with a slow server. It fits a small site badly, because a small site is nowhere near the limit.
mastersofseo.com is James Burfield’s SEO research site. On 25 September 2026, IndexedMe checked all 87 pages in its sitemap. 4 were indexed. The other 83 were “Discovered” or “URL is unknown to Google”, and Google had no record of a crawl for any of them. Over the 90 days before that, Search Console’s Crawl stats report showed 92 crawl requests for the whole site, about one a day. A server that sees one crawl a day isn’t at risk of overload.
What the site lacked was standing. Ahrefs put its Domain Rating at 0.8 that month (a third-party estimate; Google publishes no such score). When Google spends so little on a site, the likeliest explanation is that it doesn’t yet see enough reason to spend more: few links from other sites, and few internal links pointing at the deeper pages.
The same pattern showed across our other sites. On 17 October 2026 we sampled 1,790 URLs from the sitemaps of 22 sites we run. 971 of them (54%) had no crawl date in Google’s records, against 718 indexed. On 9 of the 22 sites, more than half the sample lacked a crawl date.
What happened when we asked Google to crawl them
On 27 September, 9 of the not-crawled pages on mastersofseo.com were put through Search Console’s Request indexing button by hand, about as many as Google allows in a day. On 11 October 2026, 16 days after the first scan, IndexedMe checked all 88 pages again:
- All 9 requested pages were indexed. Google’s records show each was crawled on 27 September, the day of the request.
- Of the unindexed pages nobody requested, none had a crawl date in Google’s records. All 75 were still “Discovered” or “unknown”.
That’s 9 pages on one site, so treat it as what happened there. It’s a clean result all the same: every requested page was crawled the day it was asked for, and over 16 days Google’s records show no crawl for the other 74 unindexed pages. Our reading is that a request moves one page to the front of Google’s queue. It does nothing for the site’s standing, so the pages you don’t request stay where they were.
How to see which pages are affected
- In Search Console, open Indexing → Pages and look under “Why pages aren’t indexed” for “Discovered - currently not indexed”. Click it for example URLs.
- For one page, paste the URL into the inspection bar at the top of Search Console. “Last crawl” will be empty.
- For every page at once, IndexedMe asks Google about each URL in your sitemap and groups the results by reason, up to Google’s 2,000 checks a day per property.
Checking server logs for Googlebot visits
We checked the server access log for mastersofseo.com from 27 July 2026 onwards. We kept only requests with a Googlebot user agent where the IP address was inside the ranges Google publishes and the server answered with status 200. The log showed Googlebot had fetched 16 of the 83 pages with no crawl date at the 25 September scan. The earliest fetch was on 24 August 2026.
After we requested indexing for 9 pages, the log showed Google’s inspection tool fetching each. Google’s records show each crawled 2 to 18 minutes later. For the other 74 unindexed pages, Google had no record of a crawl by 11 October. The log showed Googlebot fetched 3 of those 74 between 25 September and 11 October, but Google still kept no record. We don’t know why Google kept no record of those fetches. Our reading is that a blank crawl date tells you what Google recorded, and only your own server log tells you whether Googlebot came.
If you have server logs, you can check for Googlebot visits yourself. Google publishes a page titled Verify requests from Google crawlers and fetchers. The fixes stay the same and are in the next section.
What fixes it, in order
Requests move single pages. These are the levers for the site as a whole.
- Link to the pages from pages Google already crawls. Your homepage and your indexed pages are where Googlebot does go. A page reachable only through the sitemap is a page you’ve told Google about without vouching for it. Add it to navigation, hub pages or related links on indexed pages.
- Earn links from other sites. This is the slow part, and on a site with almost none, it’s the part that changes the most. Real mentions, guest work, directories that matter in your field.
- Cut the URLs you don’t need in Google. Thin tag and archive pages, parameter versions, near-empty pages. Fewer low-value URLs means the crawls Google does spend land on pages worth indexing. Noindex them or take them out of the sitemap.
- If the site is large, check the server. This is the case Google’s own explanation fits. In Settings → Crawl stats, look at host status and average response time. Slow responses and server errors make Google crawl less.
- Request indexing for your most important pages, a batch a day. See below.
Should you press Request indexing?
Yes, for the pages that matter most. On mastersofseo.com it’s what got pages crawled (above). Two limits shape how you use it. Google says a request doesn’t guarantee indexing (URL Inspection tool help). And there’s a daily cap: Google doesn’t publish the number, and on mastersofseo.com it ran out at about 10 requests a day. So request your most important pages first, a batch a day, and work on links for the rest.
Resubmitting your sitemap is a different thing and does little here. Google already has these URLs; the sitemap tells it nothing new.
No tool can press the button for you, IndexedMe included: Google offers no API for it. It’s in Search Console, on each URL’s inspection page.
Discovered and “URL is unknown to Google” are the same answer
Ask Google about one of these pages twice and it can say “Discovered” once and “URL is unknown to Google” the next time. On mastersofseo.com, across three scans on 25 September 2026, 79 of the 83 not-crawled pages said “unknown” at least once and only 23 said it every time. Treat both as one outcome. The full numbers are in the guide to URL is unknown to Google.
Corrected 21 October 2026: we checked our server log and this page now states what Google’s records show.
Questions
What does Discovered, currently not indexed mean?
Google says it knows the URL exists, usually from your sitemap or a link, and hasn't crawled it yet. Google's help page says it typically postponed the crawl because crawling then was expected to overload the site. Google's help says this is why the last crawl date is empty. On mastersofseo.com, Googlebot had fetched 16 of the 83 pages with no crawl date on 25 September.
Is Discovered, currently not indexed a problem?
For a page or two on a new site, it can just be a queue. When it's most of the site and nothing moves for weeks, the likeliest reason is that Google doesn't yet rate the site highly enough to spend crawls on it. Those pages can't rank until they're crawled and indexed.
Will requesting indexing fix Discovered, currently not indexed?
It can, page by page. On mastersofseo.com, Google's records show all 9 pages requested on 27 September 2026 were crawled that day and indexed. The 74 unindexed pages nobody requested had no crawl date in Google's records by 11 October. Google says a request doesn't guarantee indexing, and caps how many you can make a day, so use them on your most important pages.
How long does Discovered, currently not indexed last?
Google gives no number for this state. Its help pages say a known URL can wait up to a few weeks before Google crawls it. Over the 16 days we watched, none of the 74 unindexed pages nobody requested had a crawl date in Google's records, so don't count on it clearing by itself.
What's the difference between Discovered and Crawled, currently not indexed?
Google describes “Discovered” as meaning it hasn't fetched the page. Crawled means it fetched and read the page, then decided not to keep it. The first is about the site's standing and links; the second is a judgement on the page itself, so the fixes are different.
See which of your pages this applies to
IndexedMe checks every page in your sitemap with Google’s URL Inspection API, read-only, and sorts the ones Google left out by reason. It can’t make Google index anything; it tells you why and what to fix.