Discovered – currently not indexed

Google found the URL — in your sitemap, or through a link — put it on the list, and has not gone to fetch it.

Nothing has been read. No judgement has been made about the page, because nothing has been seen. This is a queue, and your URL is in it.

That distinction matters because it changes every fix. If you landed here after reading advice about thin content and duplicate pages, that advice is for the other status.

Status	What Google did	What it is telling you
Discovered – currently not indexed	Nothing yet — the URL is queued	It has not decided the page is worth fetching
Crawled – currently not indexed	Fetched and read it	It decided the page does not earn a place

If yours says Crawled, read that guide instead — the causes and the cures have nothing in common.

Why Google skips the queue

Google crawls as much of a site as it thinks is worth the trouble, and no more. Two things set that budget, and both are usually within your control.

Your server is slow, or wobbles under crawling

Googlebot watches how your site responds and backs off when it looks like crawling is hurting you. A server that answers in 800ms, or that returns the odd 5xx under load, gets crawled conservatively. That is Google being polite, and it is the most common cause on small sites that nobody thinks to check.

Look at Settings → Crawl stats in Search Console. If average response time is climbing or there are host-status problems, fix that before touching anything else. It is the one change that lifts every URL at once.

The site has more URLs than it has value

Faceted navigation, internal search results, session parameters, endless tag archives, paginated series that go to page 90. Every one of those is a URL Google may discover, and they compete for the same budget as the pages you care about.

A site with 400 real pages and 40,000 crawlable permutations is not being throttled unfairly. It is being crawled proportionally to how much of it looks worth reading.

Nothing points at the page except your sitemap

A sitemap says “this URL exists”. An internal link from a page Google already crawls regularly says “this URL matters, and here is the path”. The second is a far stronger signal, and pages that only ever appear in a sitemap sit in the queue longest.

What actually moves it

In order of how reliably it works:

1. Fix response time and errors. Crawl rate follows server health more directly than anything else on this list.
2. Link to the page from somewhere Google visits often. A link on a page that already ranks is worth more than any resubmission.
3. Cut the URL count. noindex or block the parameter junk, drop the empty archives, stop generating pages nothing links to. Fewer URLs means a higher share of the budget for each one that remains.
4. Keep the sitemap honest. Only canonical, indexable URLs. A sitemap full of redirects, 404s and noindex pages teaches Google that your sitemap is not worth trusting.
5. Wait. For a small site with a healthy server, this status often clears on its own within a few weeks.

What does not move it

• Requesting indexing over and over. The daily quota runs out fast and the URL was already queued. You are adding a queued URL to a queue.
• Resubmitting the sitemap. Google already has the URL. That is what “discovered” means.
• Indexing services. If the reason Google will not spend crawl budget on your site is that the site looks low value, buying links from a network makes the underlying judgement worse, not better.

When it is not really your problem

Two cases where the honest answer is that there is nothing to fix:

A brand new site. Google has no history with the domain and no reason to crawl deeply yet. Publishing consistently and earning a few real links does more than any technical change.

A very large site. Past a certain size, some proportion of URLs sitting in this status permanently is the normal state of affairs, not a defect. The question stops being “why is this page not crawled” and becomes “are the right pages being crawled” — which is a prioritisation exercise, not a bug hunt.

Checking whether it changed

Search Console updates this report on its own schedule, and it samples. You will not see a change the day it happens, and for a list of any size you cannot sit in URL Inspection checking one at a time.

The faster read is the direct one: take the list of affected URLs and ask, in bulk, whether each is findable in Google now. Do that once when you make the change and again a few weeks later, and the difference between the two runs tells you whether the fix worked — which is the question Search Console answers slowly and indirectly.

That comparison is also the only way to catch the case worth catching: the fix that worked for 30 of your URLs and did nothing for the other 300.

To take the first reading now, our free index checker answers ten URLs with no account — enough for a sample of the affected list before you commit to checking all of it.