Discovered – currently not indexed: what it means and how to fix it

“Discovered – currently not indexed” means Google knows a URL exists but hasn’t crawled it yet, so the page isn’t in the index and can’t rank. Google found the link, put the page in its queue, and decided not to fetch it for now.

It’s one of the most common statuses in the Page indexing report in Google Search Console, and one of the most misread. People assume Google looked at the page and rejected it. It didn’t. It never got that far.

A handful of URLs sitting in this bucket for a few days is normal. Hundreds or thousands sitting there for months is a signal that Google doesn’t think your site is worth crawling more of, or that your server can’t cope with more requests. Both are fixable.

What the status actually tells you

The status tells you Google has the URL but has chosen to wait before crawling it. Google’s own explanation is that it wanted to crawl the page but expected that doing so would overload the site, so it rescheduled the crawl. That’s why the “last crawled” date in the report is empty for these URLs.

In practice, server load is only part of the story. Google sets a crawl budget for each site based on two things: how much crawling your server can handle, and how much Google wants to crawl your content. If Google has seen a lot of thin, duplicate or low-value URLs on your site before, it lowers that demand and new URLs wait longer.

It helps to compare it with its neighbour in the report.

Both are covered in more depth in our guide to what indexability means, which explains the difference between a page Google can reach and a page Google will keep.

Common causes of discovered but not indexed pages

Most cases come down to one of five causes. Usually more than one applies.

• Too many URLs for the site’s authority. A new or small site publishing thousands of pages at once (product variants, tag pages, programmatic location pages) will see most of them wait.
• Low-value URLs eating the budget. Faceted navigation, filter parameters, internal search results and session IDs create near-infinite URLs. Google crawls those instead of the pages you care about.
• Weak internal linking. A page linked only from the XML sitemap, or buried five clicks deep, looks unimportant. Google prioritises pages your own site treats as important.
• Slow or struggling servers. If your server responds slowly or returns 5xx errors, Google backs off to avoid causing problems.
• Quality signals from the rest of the site. If Google has crawled a lot of thin pages from you before, it expects more of the same and lowers its crawl demand.

How to fix discovered currently not indexed

Fix the cause at site level first, then deal with individual URLs. Requesting indexing on a thousand URLs one by one won’t help if the reason they’re waiting hasn’t changed.

1. Export the affected URLs and look for patterns. Open the Page indexing report, click the status, export the examples and group them by folder or template. If 80% are filter URLs or tag archives, you’ve found your problem.
2. Decide which URLs deserve to be indexed. Not every URL should be. For pages with no search value, add a noindex tag, consolidate them with a canonical, or stop generating them. Use robots.txt rules to stop Google wasting requests on parameter and internal search URLs.
3. Strengthen internal links to the pages that matter. Link to them from relevant, already indexed pages, from category pages and from your navigation where it makes sense. Orphan pages are the most common reason a good page sits in this status.
4. Check server response times. Look at the Crawl stats report in Search Console. If average response time is high or host status shows problems, talk to your host or developer. A faster server lets Google crawl more without strain.
5. Improve or merge thin content. Pages with a few lines of text, or near-copies of each other, drag down how Google rates the whole site. Merge them into fewer, stronger pages.
6. Keep your XML sitemap clean. Include only canonical, indexable URLs that return a 200 status. A sitemap full of redirects and noindexed pages sends mixed signals.
7. Request indexing for priority pages. Once the above is done, use the URL Inspection tool for your most important URLs. There’s a daily limit, so save it for pages that matter.

A full site crawl is the quickest way to find orphan pages, parameter URLs and thin templates in one pass, because it shows you the site the way a search engine sees it.

How long it takes to clear

Expect weeks, not days. After you remove low-value URLs and improve internal linking, Google has to recrawl the site and adjust how much it wants to crawl. Small sites with a handful of affected pages often see them indexed within a couple of weeks. Large sites with tens of thousands of affected URLs can take months.

Watch the trend rather than individual URLs. If the number in “Discovered – currently not indexed” is falling and your indexed page count is rising, the fixes are working. Server log files are the most reliable way to confirm Googlebot has started visiting the pages again; our guide to log file analysis explains how.

When to leave it alone

Leave it alone when the URLs in the list are ones you don’t want indexed anyway. Search Console reports on every URL Google has found, including old parameter URLs, feeds and duplicates. If the affected pages are filter combinations or old test pages, their absence from the index is fine.

Also leave it alone for brand new pages. A post published yesterday can sit in this status for a few days before Google crawls it. That’s the queue working as intended.

If important pages are stuck and you can’t see why, our technical SEO team runs indexation audits that trace exactly where crawl budget is going. Book a free strategy session and we’ll look at your Page indexing report with you.

Related reading: our guides to technical SEO and JavaScript SEO.

Common questions