Discovered - currently not indexed: why it happens and how to fix it

What "Discovered - currently not indexed" means

Google found the URL, through your sitemap or a link, and put it in its queue. It has not visited it yet. Because Google has not read the page, this is not a judgment of your content. It is a question of when Google gets to it, and whether it thinks the visit is worth it.

When to wait and when to act

The wait time is a rule of thumb from experience, not a Google number. Google does not publish one.

4 causes and their fixes

1. Too many URLs that do not need crawling. Filter and sort parameters, endless calendar pages, tag pages, session IDs. Each one is a URL Google may queue.

• Stop linking to these URLs where you can (for example, filters that use form controls instead of plain links).
• Keep them out of your sitemap.
• For large sites, Google's crawl budget guide explains how to manage which URLs get crawled, including using robots.txt for URLs you never want crawled.

2. A slow or struggling server. Google says 5xx and 429 errors make its crawlers slow down (Google, HTTP status codes and network errors, updated February 2026). In Search Console, open Settings > Crawl stats and look at response times and host status. Fix errors and slow responses first.

3. Weak internal links. A page linked only from the sitemap looks unimportant. Link to it from the homepage, a category or hub page, or related posts.

4. A sitemap full of URLs you do not want indexed. If your sitemap lists redirects, 404s, noindexed pages or thin pages, it tells Google little about what matters. Keep only canonical pages you want indexed. Then check the sitemap status in Indexing > Sitemaps.

By platform

• WordPress: many sites have thin tag, author and date archives. Set the ones you do not need to noindex in Yoast or Rank Math and keep them out of the sitemap.
• Shopify: filtered collection URLs can multiply. Shopify's default robots.txt already blocks some of them; check yours before editing robots.txt.liquid.
• Webflow: check CMS collections you never meant to publish as pages, and turn off their template pages or exclude them from the sitemap.
• Wix: check dynamic pages that were created for test data.

Example (fictional): brightsmile-dental.com, 60 real pages, shows 1,400 URLs as Discovered. Nearly all are calendar URLs from a booking widget (/book?date=...). The owner removes the calendar links from crawlable HTML and keeps them out of the sitemap. The 5 real service pages in the row get links from the homepage.

Discovered vs crawled - currently not indexed

Read the full guide to Crawled - currently not indexed.

Does Request Indexing help?

For a few key pages, yes, it can move them up. Google says there is "a daily limit" to requests and that a request "does not guarantee that the page will appear in the Google Index" (Google, URL Inspection tool help). It will not fix thousands of URLs. For those, fix the causes above and resubmit your sitemap.

The free 13-page Page indexing fix guide covers all 17 reasons, with a triage tree, per-CMS steps and a printable tracker.