Blog / Technical SEO /
Fixing ‘Discovered – currently not indexed’
You publish a page. A week later you check Search Console, and there it is, listed under “Discovered – currently not indexed”. A month later it’s still there, along with a few hundred others.
It sounds like Google has looked at your page and rejected it. It hasn’t. It hasn’t looked at all yet.
That difference matters, because it changes what you should do about it.
What the status means
“Discovered – currently not indexed” means Google knows the URL exists (from your sitemap, an internal link or a link from another site) but hasn’t crawled it yet. Google’s own explanation is that it wanted to crawl the URL, but it expected the crawl to overload the site, so it rescheduled.
Compare that with its neighbour, “Crawled – currently not indexed”. That one means Google did fetch the page and decided not to index it, at least for now. That’s usually a quality or duplication question. “Discovered” is earlier in the process: a crawling and priority question.
I went through every status in the Search Console page indexing report explained. This post is just about “Discovered”.
First: should you worry?
Often, no. Some URLs in this list are normal:
- pages published in the last few days
- filtered or sorted URLs you don’t want indexed anyway
- tag pages, paginated archives and other low-value pages
- old URLs that Google found in a link somewhere
So before fixing anything, open the report, click into the status and export the example URLs. Sort them into two piles:
- Pages you want indexed: products, collections, posts, service pages.
- Pages you don’t care about: filters, parameters, archives, junk.
If pile one is small or empty, there’s nothing to fix. If it has important pages that have been stuck for weeks, read on.
Why important pages get stuck
There are usually three reasons, and they often overlap.
1. The site is slow to respond
Google adjusts how fast it crawls based on how your server copes. If the server is slow or returns errors, Google crawls less, and more URLs wait in the queue.
Check: Search Console → Settings → Crawl stats. Look at average response time and the host status. A rising response time or availability problems are a clear signal.
Fix: better hosting or caching, removing heavy plugins or apps, using a CDN. Page speed on a budget has the cheapest wins first.
2. Too many URLs for the site’s size
If your site generates thousands of URLs (filter combinations, tags, parameters, calendar pages), Google has to decide which to crawl. Important pages compete with junk for attention.
Check: how many URLs are in the “Discovered” list compared with the number of pages you actually want indexed. If it’s ten times bigger, you have a URL problem.
Fix:
- stop low-value URLs being linked and discovered: noindex tag archives, keep filter URLs out of the sitemap, and avoid linking to endless parameter combinations
- block crawl traps (like infinite calendar pages or sorting parameters) in robots.txt if they truly have no value
- clean your sitemap so it only lists pages you want indexed (XML sitemaps on WordPress)
Crawl budget: does a small site need to care? explains when this applies. For most small sites, it’s the URL clutter that matters, not crawl budget in the big-site sense.
3. Google doesn’t think the pages are important enough yet
This is the most common one on small and new sites. If a page is only listed in the sitemap, with no internal links pointing at it, Google has little reason to rush.
Google also learns from the pages it has crawled. If a lot of similar pages on the site turned out to be thin or duplicated, it may give the rest of that type a lower priority.
Fix:
- Link to the page from relevant, already-indexed pages. Internal links are the strongest signal you control. A simple internal linking system explains how I do it.
- Link from the homepage or main navigation for truly important pages.
- Improve the pages of that type. If you have 300 nearly identical product or location pages, the fix is making them genuinely useful, or having fewer of them. Thin content covers that.
What about “Request indexing”?
The URL Inspection tool’s Request indexing button can help for a handful of important pages, such as a new key page or a page you’ve just fixed. It asks Google to crawl it sooner.
It doesn’t fix the underlying problem, and there’s a daily limit. If hundreds of pages are stuck, requesting them one by one won’t help. Fix the cause instead.
A step-by-step routine
- Export the “Discovered – currently not indexed” URLs.
- Sort them into “want indexed” and “don’t care”.
- For “don’t care”: stop them being discovered where you can (sitemap, internal links, noindex, robots.txt for crawl traps).
- For “want indexed”: check each one has internal links from indexed pages and appears in the sitemap.
- Check Crawl stats for slow responses or server errors, and fix hosting issues.
- Request indexing for the five or ten most important pages.
- Wait a few weeks, then click Validate fix in the report, or simply check whether the numbers move.
How long does it take?
It depends on the site. For a small site with a few stuck pages, adding internal links often gets them crawled within days or a couple of weeks. For a large site with a URL clutter problem, it can take months for Google to work through the backlog after you’ve cleaned up.
If pages move from “Discovered” to “Crawled – currently not indexed”, that’s progress of a sort: Google has looked at them. Now the question is quality, not crawling.
Related reading
- The Search Console page indexing report explained
- Crawl budget: does a small site need to care?
- Internal linking on WordPress: a simple system
- Thin content: how to find it and what to do about it
Export your “Discovered – currently not indexed” list now and count how many of those URLs you actually want in Google. Is it a crawling problem or a clutter problem?