Discovered Currently Not Indexed: How to Fix It

You publish a new service page, wait two weeks, and it still doesn’t show up on Google. Then you open Search Console and see the status “Discovered – currently not indexed” next to it. Google knows the page exists, but it hasn’t even visited it yet.

Discovered currently not indexed is one of the most common statuses in Search Console, and it’s usually fixable. This guide explains what the status means, when you should worry and the exact steps I take to get pages crawled.

Quick answer: Discovered currently not indexed means Google found the URL but postponed crawling it. On small sites it’s often temporary. If it lasts for weeks or affects many pages, strengthen internal links to the page, clean your sitemap, remove low-value URLs from the crawl path and check your server speed.

What Discovered Currently Not Indexed Means

According to Google’s Page indexing report documentation, this status means the page was found but not crawled yet. Google says that typically, it wanted to crawl the URL, but this was expected to overload the site, so it rescheduled the crawl.

In practice, there are two reasons Google puts a page in this queue:

Crawl capacity: your server is slow or returns errors, so Google crawls less to avoid overloading it.
Crawl demand: Google doesn’t think the page is important enough to crawl soon, often because few pages link to it or the site has many similar, low-value URLs.

People often confuse it with a similar status. Here’s the difference:

Status	Has Google crawled it?	What it usually points to
Discovered – currently not indexed	No	Crawl priority, internal links, server capacity
Crawled – currently not indexed	Yes	Content quality or duplication

Is It Actually a Problem?

Not always. Before you change anything, check which situation you’re in:

Situation	What to do
A few new pages, published in the last two weeks	Wait. Crawling can take days or weeks.
An important page stuck for over a month	Add internal links and request indexing.
Hundreds of tag, filter or parameter URLs	Remove them from the crawl path. That’s a good outcome.
Most of your site’s pages	Look for site-wide issues: server speed, sitemap, duplicate content.

Google’s own crawl budget guide says crawl budget mainly matters for very large sites, but it also names sites with a large share of URLs marked as discovered currently not indexed. So if most of your site is stuck, treat it seriously, even if the site is small.

Common Causes

The page is an orphan, with no internal links pointing to it.
The XML sitemap lists redirects, 404s or noindex pages, so Google trusts it less.
WordPress creates many thin URLs, like tag pages, attachment pages and internal search results.
Filters and URL parameters create thousands of near-identical pages.
The server is slow or returns 5xx errors.
Long redirect chains waste Google’s crawl time.
Many pages are thin or near-duplicates, so Google lowers crawl demand for the whole site.

How to Fix Discovered Currently Not Indexed Step by Step

1. Export the Affected URLs and Group Them

In Search Console, open Indexing, then Pages, and click the status to see examples. Export the list and group the URLs by type: blog posts, service pages, tags, parameters. The pattern usually tells you the cause within a few minutes.

2. Remove Low-Value URLs From the Crawl Path

If most affected URLs are pages you don’t need in Google, stop sending Google to them. Remove internal links to them, drop them from the sitemap and, for true crawl traps like filter parameters, block them in robots.txt. On WordPress, an SEO plugin can turn off attachment pages and remove thin archives from the sitemap.

One caution: a noindex tag only works after Google crawls the page, so it won’t clear this status quickly. It’s still the right choice for pages you want Google to drop over time.

3. Clean Your XML Sitemap

Your sitemap should list only canonical pages that return a 200 status and are meant to be indexed. Remove redirects, 404s and noindex pages. Keep the lastmod date accurate, because Google recommends it for sites that update content.

4. Add Internal Links to Important Pages

This is usually the first fix to try. Link to the stuck page from your home page, main menu, related service pages or popular blog posts. Use descriptive anchor text, not “click here”. A page linked from strong pages looks more important to Google.

5. Make the Page Worth Crawling

If the stuck pages are thin, near-duplicate or auto-generated, Google has little reason to prioritize them. Merge similar pages, add useful original content and remove pages that serve no one.

6. Check Server Speed and Crawl Stats

Open Settings, then Crawl stats in Search Console. Look at host status, response codes and average response time. Google notes that sites with fewer than a thousand pages usually don’t need this report, but it’s still worth a quick look if many pages are stuck. Frequent 5xx errors or slow responses mean you should talk to your host or upgrade hosting.

7. Request Indexing for a Few Key Pages

After you fix the cause, use the URL Inspection tool and click Request indexing for your most important pages. Google says there’s a quota for individual URL requests, and requesting the same URL again won’t make it faster. For many URLs, rely on your sitemap instead.

Quick Checklist

Affected URLs exported and grouped by type
Unneeded tag, attachment, search and parameter URLs removed from the crawl path
Sitemap lists only indexable 200 pages
Every important page has several internal links from relevant pages
Thin and duplicate pages merged or removed
Crawl Stats show healthy host status and response times
Indexing requested for key pages after the fix

If you’d like help, my technical SEO audit covers indexing, sitemaps, internal links and server issues in one report.

Frequently Asked Questions

How long does it take to fix discovered currently not indexed?

It depends on the cause. After you add internal links and clean your sitemap, important pages are often crawled within days or a few weeks. Google says crawling can take anywhere from a few days to a few weeks. Site-wide problems, like slow hosting or thousands of thin URLs, usually take longer to recover.

Should I click Validate Fix for this status?

You can, but it doesn’t make Google crawl faster. Validation simply tells Google to recheck the listed URLs and reports progress over time. Fix the real cause first, like weak internal links or a messy sitemap, and then start validation. Otherwise the validation is likely to fail and you’ll need to run it again.

Is discovered currently not indexed bad for SEO?

It’s bad only when the affected URLs are pages you want to rank. Those pages can’t appear in Google until they’re crawled and indexed. If the list contains tag pages, filter URLs or old attachments, it can actually be a good sign that Google is ignoring pages you don’t need.

Does requesting indexing fix the problem?

It can help for a few important pages, but it’s not a long-term fix. Google limits how many URLs you can submit, and repeated requests for the same page don’t speed things up. If the cause is weak internal linking, slow hosting or low-value URLs, the problem will return until you fix that cause.

Why does a new website have so many discovered pages?

New sites have little authority and few external links, so Google crawls them carefully at first. WordPress also creates tag, category and attachment URLs automatically, which fills the queue. Publish useful pages, link them well, keep the sitemap clean and give Google some time to build trust.

Final Thoughts

Discovered currently not indexed is Google telling you it hasn’t prioritized a page yet. Most of the time, the fix is simple: make important pages easy to find, stop wasting Google’s time on pages that don’t matter and keep your server healthy.

If Search Console keeps showing this status on pages that should rank, send me your site URL and I’ll tell you what I’d check first. You can also see how I handle ongoing technical work in my monthly SEO service.