Crawled vs Discovered — currently not indexed

Updated 2026-08-07

Two different problems with nearly identical names. One is a crawl-capacity issue, the other is a quality judgement — and they need opposite responses.

These two statuses in the Page indexing report look like variants of the same thing. They are not, and treating them the same way wastes a lot of effort. The difference is one word: whether Google has actually fetched the page.

Discovered — currently not indexed

Google knows the URL exists and has not fetched it yet. Found in a sitemap or a link, queued, not crawled.

This is a capacity problem, not a judgement. The usual causes:

• Your server is slow or unstable. Google reduces crawl rate when it detects strain. This is the most common cause on shared hosting, and the fix is hosting, not content.
• Too many URLs for the site's crawl allocation. Frequently faceted navigation, calendar pages, or paginated archives generating combinations nobody needs.
• The site is new. New domains get very little crawl budget. Sometimes the answer is a month of patience.

What helps: fix server response times, cut the number of low-value crawlable URLs, and link the pages you care about from somewhere Google crawls often. What does not help: resubmitting the sitemap repeatedly.

Crawled — currently not indexed

Google fetched the page, looked at it, and decided against indexing it. That is a quality or duplication judgement, and it is the harder of the two.

Common reasons, roughly in order:

• Thin or templated content. Programmatically generated pages where only a name or a city changes are the classic case.
• Near-duplicate of another page of yours. Google has picked one and is holding the rest.
• Nothing new on the web. A page covering a topic already covered better elsewhere, adding no information.
• Effectively orphaned. In the sitemap, linked from nowhere. A page nothing links to reads as a page you do not value.
• Sitewide quality drag. If a large share of your URLs are thin, indexing gets harder for all of them. This is the uncomfortable one, and the answer is usually deletion.

What helps: make the page substantially better or merge it into a page that is; link to it properly from relevant pages; and remove or noindex the pages you cannot justify. Cutting a thousand thin URLs frequently improves indexing of the rest.

Neither status is an error and neither needs "fixing" as a count. Plenty of URLs belong in these buckets — tag archives, filtered views, pagination. Check whether the URLs listed are pages you actually want indexed before treating the number as a problem.

Working through it

1. Open the affected URLs and sort out what they actually are. If they are mostly junk, the real fix is stopping their generation.
2. Run URL Inspection on a page you genuinely want indexed. It will tell you the canonical Google picked, which often explains the whole thing.
3. Request indexing for a handful of genuinely important pages. It works at that scale and is useless at any larger one.
4. Give it weeks. Both statuses can resolve on their own, and re-requesting daily changes nothing.

One thing to rule out first: if the pages once had traffic and stopped, this may be a symptom rather than the cause — work through why did my clicks drop instead.