Discovered – Currently Not Indexed: What It Means and How to Fix It

Google has found your URLs but hasn’t crawled them yet. Here is why “Discovered – currently not indexed” happens, how it differs from “Crawled”, and a step-by-step plan to get those pages indexed.
Discovered – Currently Not Indexed: What It Means and How to Fix It, MIVAQ guide cover

If you open the Page indexing report in Google Search Console and see a long list under “Discovered – currently not indexed”, you are looking at pages Google knows about but has not even visited yet. It is a different problem from “Crawled – currently not indexed”, and it needs a different fix. In this guide we explain what the status really means, the most common causes we find on client websites, and the exact process we follow to move those URLs into Google’s index.

This article is part of our complete guide: Why Is My Website Not on Google? The Complete Indexing Guide.

What “Discovered – currently not indexed” actually means

Google’s own documentation describes this status as a page that Google found but has not crawled yet. Usually Google wanted to crawl the URL but expected that doing so would overload the site, so it rescheduled the crawl. In plain English: Google has the address written down, but it hasn’t knocked on the door.

That small detail matters. Because Google has not read the page, the problem is almost never the content itself. It is about how Google prioritises crawling your site: how many URLs you have, how fast your server responds, how well the page is linked, and how important Google thinks the URL is.

Discovered vs. Crawled: why the difference matters

  • Discovered – currently not indexed: Google knows the URL exists (from a sitemap or a link) but has not fetched it. The fix is about crawl priority, server capacity and internal links.
  • Crawled – currently not indexed: Google has fetched and read the page, then decided not to index it. The fix is about quality, uniqueness and importance.

If you treat a “Discovered” problem like a content problem, you can spend weeks rewriting pages that Google has never even read. Diagnose first.

The most common causes

1. The site is new and has very few signals

Brand-new domains with no links pointing to them get a small crawl allowance. Google discovers the sitemap, notes hundreds of URLs and works through them slowly. This is normal for the first weeks, but it can drag on if nothing else changes.

2. Too many low-value URLs competing for attention

WordPress tag archives, date archives, attachment pages, filtered shop URLs, search result pages and paginated archives can multiply a 30-page website into 600 URLs. Google spreads its limited crawling across all of them, and the pages you actually care about wait in the queue.

3. Slow or unstable server responses

When a server responds slowly or returns errors, Google deliberately crawls less so it does not overload the site. Cheap shared hosting, missing caching and heavy plugins are frequent culprits. You can see the effect in Search Console under Settings › Crawl stats, where average response time and host status are shown.

4. Weak internal linking

A URL that is only listed in the sitemap, with no links from the menu, homepage or related pages, looks unimportant. Google tends to crawl well-linked pages first.

5. Large batches of new content published at once

Publishing hundreds of near-identical pages in one go (for example, location pages for every town in a county) often lands most of them in “Discovered”. Google samples a few, and if they look thin or similar, it slows down on the rest.

How to fix it: our step-by-step process

Step 1: Export and group the affected URLs

In Search Console, open Indexing › Pages, click the “Discovered – currently not indexed” row and export the list. Sort the URLs into three groups: pages that should rank (services, products, key articles), pages that are useful but secondary, and pages that never needed to be indexed at all.

Step 2: Remove crawl waste

For the third group, stop Google from wasting time on them:

  • Set thin tag and date archives to noindex in your SEO plugin (Rank Math or Yoast).
  • Redirect WordPress attachment pages to the parent post or the file itself.
  • Stop internal search result pages and faceted filter URLs from being linked or indexed.
  • Remove them from your XML sitemap so the sitemap only lists pages you want indexed.

Step 3: Make the server faster and more reliable

Turn on page caching, compress images, remove unused plugins and check that the hosting plan is not constantly hitting its limits. On a recent WordPress project we combined server caching with image optimisation and a plugin clean-up, similar to the work described in our redesign checklist. Faster responses usually lead to more crawling within a few weeks.

Step 4: Strengthen internal links to priority pages

Link your important pages from the homepage, the main navigation and relevant articles, using descriptive anchor text. A page with five meaningful internal links is far more likely to be crawled than one buried in a sitemap.

Step 5: Submit a clean sitemap and request indexing for key pages

Resubmit the cleaned sitemap in Search Console. Then use the URL Inspection tool on your most important URLs and click Request indexing. Do this for a handful of priority pages rather than hundreds of URLs; the quota is limited and it is not a bulk tool.

Step 6: Publish steadily, not in huge bursts

If you are adding many pages, release them in batches and make each one genuinely useful and distinct. Steady publishing teaches Google that your site regularly has something worth crawling.

Step 7: Earn a few relevant links

A handful of genuine links from relevant websites, directories or partners tells Google the site matters and increases crawl demand. Avoid paid link schemes; they create new problems.

How long does it take?

After cleaning up crawl waste and improving speed, we typically see URLs move from “Discovered” to “Indexed” over two to six weeks, depending on site size and authority. Small sites with a few important pages can move faster once those pages are linked well and submitted.

Real-world example

Several of the indexing projects in our portfolio started with large “Discovered” lists. For websites like M10 News, Green Solar Systems and OneFlytt, the fix was a combination of a clean sitemap, removing indexing blockers and better internal linking, rather than rewriting content. You can read more examples in our case studies.

A quick checklist

  • Export the affected URLs and decide which ones deserve to be indexed.
  • Noindex or remove low-value archive, attachment and filter URLs.
  • Clean the XML sitemap so it lists only indexable pages.
  • Improve server response time and enable caching.
  • Add internal links to priority pages from strong pages.
  • Request indexing for the most important URLs only.
  • Publish new content steadily and keep it unique.
  • Monitor the Page indexing and Crawl stats reports weekly.

If you would rather have this handled for you, our Google indexing fix service covers the audit, the fixes and the monitoring. You may also find our guide to why a website is not showing on Google useful.

Related guides and services

Get expert help

If you would rather spend your time running your business, MIVAQ can handle this for you. We audit the site, fix the root causes, document every change and show you the before-and-after in Search Console, so you know exactly what improved and why. Start with our Google indexing fix service, browse real client results in our case studies, or contact us for a free, no-pressure review of your website.

Frequently asked questions

Is “Discovered – currently not indexed” an error?

No. It is a status, not an error. It means Google has postponed crawling. It becomes a problem when important pages stay in this status for weeks.

Will requesting indexing fix it?

For a few key pages it can speed things up. It will not fix a site-wide crawl problem caused by slow servers or thousands of low-value URLs.

Should I delete pages stuck in this status?

Only if they have no value. Otherwise improve linking and remove crawl waste so Google can reach them.

Does this happen on Wix and Squarespace too?

Yes, although it is less common because those platforms create fewer duplicate URLs. Our Wix and Squarespace SEO service covers both.

Keep reading

How to Start a Shopify Store – MIVAQ complete guide cover
ShopifyWeb
Step-by-step guide to starting a Shopify store in 2026: costs, plans, themes, products, payments, shipping, SEO and a full launch checklist.
Wix & Squarespace SEO – MIVAQ complete guide cover
SEOWeb
The complete 2026 guide to Wix SEO and Squarespace SEO: setup, titles, images, speed, local SEO, schema, redirects and fixing sites not
How to Build a WordPress Website – MIVAQ complete guide cover
WebWordPress
Step-by-step guide to building a WordPress website for your business in 2026: costs, hosting, themes, plugins, SEO, speed, security and a launch

Need help putting this into practice?

We turn ideas like these into working websites, stores and growth plans. Tell us what you are working on.