Discovered – Currently Not Indexed: Causes and How to Fix It

By Hridoy Ahmed | Last updated: November 2026 | 10 min read

Short answer: “Discovered – currently not indexed” means Google knows your URL exists but has not crawled it yet, so the page cannot appear in search. Typical causes are a slow or overloaded server, weak internal links, thin or near-duplicate pages, and a site with too many low-value URLs. Fix the signals on your best pages first, then request indexing for those pages only.

In this guide

What the status means

You see this status in Search Console under Indexing, then Pages. Google found the URL, usually through your sitemap or a link, and put it on a to-do list. Google has not fetched the page yet. Because Google never read the page, it has no opinion about the content at this stage. That detail separates this status from its look-alike.

Discovered – currently not indexed Crawled – currently not indexed
Did Google fetch the page? No Yes
What Google knows The URL only The content too
Main question Why did Google wait? Why did Google reject it?
Typical fix Server health, priority signals, fewer junk URLs Content quality, uniqueness, intent

If your problem is the second status, read my guide on Crawled – currently not indexed.

When it is normal and when it is a problem

Google does not promise to index every URL it finds. A site with a few pages in this status is usually fine, especially when those pages are filters, internal search results, tag archives or tracking-parameter URLs. You do not want those indexed anyway.

It becomes a problem when your important pages sit in this status for weeks, such as service pages, products or your best articles. A sudden jump in the count after a site change, a migration or a plugin update also deserves a look.

Google has described three broad reasons for this status: the page quality it expects, timing, and server capacity. Google’s help page itself mentions that crawling the URL could overload the site, so it rescheduled the crawl. Use those three reasons as a checklist.

The 3-bucket triage

Do not treat every URL on the list the same way. Sort them into three buckets first. This saves hours.

Step 1: Group the URLs by template

Export the list from Search Console. Add a column for the URL pattern, for example /blog/, /tag/, /product/ or ?s=. Count how many URLs fall under each pattern. If one pattern holds most of the list, you have a template problem, not a page problem. That single insight often shows the answer in ten minutes.

Step 2: Place each group in a bucket

Bucket A: Site problem. Google holds back crawling because it doubts your server or sees too many low-value URLs.

  • Open Settings, then Crawl stats, in Search Console. Look at average response time and server errors.
  • Check whether your host throttles bots, uses a firewall rule that slows crawlers or returns occasional 5xx errors.
  • Count how many junk URLs you expose: filters, parameters, tag archives, attachment pages, paginated archives.

Bucket B: Page problem. The URL gives Google little reason to hurry.

  • The page has no internal links, or only one link from a deep archive page. See my guide on internal linking.
  • The page repeats the same template with a few changed words.
  • The page has almost no unique text.
  • The page canonical points somewhere else. See canonical tags.

Bucket C: Priority problem. Your site is healthy, but Google has little reason to prioritize new URLs. This fits new sites with few links and sites that publish many pages at once.

A 14-day fix plan

  1. Day 1: Decide which URLs matter. Mark each URL as “must index”, “maybe” or “should not index”. Do not spend effort on the third group.
  2. Day 1-2: Clean the sitemap. Your XML sitemap should list only canonical, indexable, valuable pages. Remove redirects, noindex pages and parameter URLs. Read how to create an XML sitemap.
  3. Day 2-3: Fix server health. Check hosting resources, caching and plugin load. A slow server makes Google crawl less. See how to reduce TTFB on WordPress.
  4. Day 3-5: Add internal links. Link each “must index” page from at least two relevant, already indexed pages, using descriptive anchor text. Add the pages to a hub or related-guides block.
  5. Day 5-8: Improve thin pages. Add real, unique information: examples, steps, data from your own work, answers to follow-up questions. Merge pages that say the same thing. Use keyword mapping to find overlaps.
  6. Day 8-9: Block junk. Use noindex for tag archives, filters and internal search pages where it makes sense. Use robots.txt carefully, because a blocked URL cannot show its noindex tag.
  7. Day 9-10: Request indexing for a few pages. Use URL Inspection on your five to ten most important URLs. This is a nudge, not a command.
  8. Day 10-14: Earn one or two real signals. A relevant link, a mention or a share from a site that matters can help Google see that the page deserves a visit.

Want a second pair of eyes on your whole site? My technical SEO service starts with this kind of crawl and indexation check.

What does not work

  • Pressing Request Indexing on hundreds of URLs. Google limits the tool, and it does not fix the cause.
  • Resubmitting the sitemap every day. A sitemap tells Google about URLs, not that they deserve indexing.
  • Using the Indexing API for normal pages. Google built it for specific page types. See how to get indexed faster.
  • Publishing more pages of the same kind. More thin pages deepen the problem.
  • Buying links to force a crawl. This risks a spam action and does not fix quality.

How to measure progress

Track a small sample, not the whole list. Pick 20 URLs in the “must index” group and record their status each week in a sheet. Add three columns: internal links to the page, date you changed it and status after Google’s next crawl. The Page indexing report can lag, so check the URL Inspection tool for the live status of a single URL.

Give changes time. Google may need days to weeks to crawl and reassess a page, and bigger sites can take longer.

FAQ

Does “Discovered – currently not indexed” hurt my SEO?

It hurts only when important pages stay in it. Pages that you do not want indexed cause no harm.

How long does it take to leave this status?

It can take days or weeks after you fix the cause. Google does not give a fixed time.

Should I delete pages with this status?

Delete or merge pages only when they add nothing. If a page matters, improve and link to it instead.

Is it a crawl budget problem?

Sometimes, mostly on large sites. Small sites usually have a quality, linking or server issue. Read about crawl budget.

Can I fix it with a plugin?

A plugin can help with sitemaps and noindex rules. It cannot replace useful content and good internal links.

Important pages stuck in “discovered”? I check your server, sitemap, links and content by hand. See my SEO and technical SEO service.

About the author: Hridoy Ahmed is an SEO specialist and WordPress security expert based in Dhaka, Bangladesh. He has 8+ years of experience and works with clients worldwide.

Related guides

Leave a Comment

Your email address will not be published. Required fields are marked *