Discovered, currently not indexed: why Google has not crawled the page

Search Console’s Page indexing report groups every URL it knows for your property as Indexed or Not indexed. Each Not indexed URL has a reason. As of 2026, Discovered, currently not indexed means Google knows the URL from a sitemap or a link but has not crawled it yet. It is common on new sites and very large sites.

Google is rationing crawl. It thinks fetching that URL now could overload your server or is not worth it yet. That judgement can change when the URL gains stronger signals: internal links, sitemap priority, and fewer junk alternatives competing for attention.

You do not fix this with a tag on the page. You fix it by making the page easier to discover through links, by pruning low value URLs, and by keeping the sitemap lean.

Crawled, currently not indexed is different. Googlebot fetched the page and chose not to index it for now. That is usually a quality or duplication call. Discovered, currently not indexed was never fetched in the first place.

For Crawled, currently not indexed, you work on content quality, duplication, and links. For Discovered, currently not indexed, you first make sure Google will fetch the page at all. See also our guide to Crawled, currently not indexed for the other path.

• New site with little crawl history, Google starts slow and ramps up if the site stays healthy
• Large site with many URLs, Google paces crawl to match your server and expected value
• Too many low value URLs, such as faceted parameters, tag archives, thin search pages, soft duplicates
• The page is only in the sitemap, with no internal links from pages that do get crawled
• Frequent errors or timeouts, Google lowers crawl rate until it sees stability

One weak page is rarely the whole story. A site with many junk URLs or redirect chains bleeds crawl budget. Clean up the waste, then ask for the pages that matter to be fetched.

Before you change anything, inspect the URL. This confirms that it is in the property, how Google discovered it, and whether crawling and indexing are allowed.

1. 1

   Open URL Inspection in Search Console

   Paste the full URL from your site. It must be within a verified property.

2. 2

   Read the Coverage status

   You will see whether the URL is on Google, and the reason if not. For Discovered, currently not indexed, note the referring page or sitemap listed.

3. 3

   Test live URL

   Fetch the page now. Check the HTTP status, rendered HTML, screenshot, and resources that could not be loaded. Fix server errors and blocked resources first.

4. 4

   Confirm directives

   Make sure robots.txt allows crawl. Make sure meta robots does not say noindex if you want the page indexed. Check the declared canonical and the Google selected canonical.

5. 5

   Request indexing

   Use this after you fix links and access. It queues a crawl. There is a small daily quota per property. It does not guarantee indexing.

If URL Inspection shows Blocked by robots.txt or Excluded by noindex tag, fix those first. Discovered, currently not indexed is not the real issue then, access is.

Google paces crawl on your site. If most URLs are low value, the good ones wait. Prune URLs that you never want indexed and stop generating them where you can.

• Remove faceted or tracking parameters from links. Add proper canonical parameters or avoid linking to parameterised variants from templates.
• Noindex tag archives and internal search results you do not need in Google. Keep category and primary collection pages.
• Consolidate near duplicates. Use rel=canonical on variants like UTM copies or print views. Prefer one clean URL per page.
• Fix Soft 404s. Either return a real 404 or give the page content. Do not let empty templates waste crawl.
• Clear redirect chains. Update internal links so they go direct to the final URL. Keep the sitemap free of redirected URLs.

Run a quick audit of internal links. If your templates add query strings like ?ref= or ?sort=new to every link, that multiplies crawl for no gain. Strip them from core navigation and canonicalise any that remain for users.

Your sitemap is a to do list for discovery, not a command. Treat it as a shortlist. Keep only URLs you want in the index and that return 200 with content.

1. 1

   List only indexable pages

   Exclude noindex, redirects, 404s, login walls, tag noise, and internal search results. Each URL should be canonical to itself.

2. 2

   Keep it fresh

   Update the sitemap when you publish or remove a page. Remove old slugs you redirected. Do not leave dead ends.

3. 3

   Use one canonical URL per page

   If you have http and https, or www and non www, choose one in Search Console and link to it everywhere. Canonicals should match links and sitemap.

4. 4

   Submit and check the Sitemaps report

   Submit at /sitemap.xml. Check for discovered URLs and any errors listed by Search Console. Fix issues and resubmit.

A fixed sitemap for a store might list only /, /collections/shoes, and key product pages in stock. Leave out /search?q=, /tags/blue, and any old /product-old that now redirects.

A sitemap is not enough. Google follows links. Place direct links to the target page from pages that you know get crawled and indexed already.

1. 1

   Find seed pages

   Pick your homepage, /blog/, /pricing, and any guides that already rank. You can see indexed pages in the Page indexing report, filtered to Indexed.

2. 2

   Link in context

   Add a natural link in the body where it helps the reader. Use descriptive anchor text, for example “setup guide” linking to /guides/getting-started.

3. 3

   Update nav or hubs

   If the page is core, add it to the main nav, footer, or a topic hub page. Avoid adding it to every page if it is not core.

4. 4

   Remove detours

   Change old internal links that redirect, so they point straight at the URL you want indexed.

Example: /guides/getting-started is Discovered, currently not indexed. You link it from /docs/overview and /blog/launch-notes. You add it to the footer. Two weeks later it is crawled, and then indexed after the first pass. The sitemap pointed to the same URL throughout.

Do not spam Request indexing. Queue it only after you fix access, links, and sitemap. It puts the URL in a crawl queue, with a small daily quota per property. It does not force indexing.

In the Page indexing report, use Validate fix after you clear a systemic issue, like redirects in the sitemap. Validate fix starts a re check that can take about two weeks per batch. Use it to confirm that your clean up worked, not to push random URLs through.

Give Google time. For a small site with a clean sitemap and fresh links, set a check date two weeks out. For a large site or heavy clean up, set four weeks. Use calendar reminders so this does not drift.

• Page indexing report: watch the count of Discovered, currently not indexed go down. Drill into example URLs to spot patterns.
• URL Inspection: check last crawl date on the target page and the pages you linked from.
• Sitemaps report: confirm that submitted URLs are discovered and that there are no errors.
• Crawl Stats report: check host status and response codes. If you see spikes of 5xx, fix server issues before asking for more crawl.

If a page flips to Crawled, currently not indexed, do not panic. That means it was fetched. Now work on the content and duplication side. Improve the page and its context, then request indexing once after updates ship.

A fixed page returns 200, is in the sitemap, is linked from at least two indexed pages, and is not one of many thin variants. The canonical is self referencing and matches the URL in the sitemap and in internal links. The page loads fast and stable, so Google can render it quickly.

Example before: /blog/?tag=pricing in the sitemap, with no body content, linked only from a tag cloud. Example after: remove it from the sitemap, add a link from /pricing to /guides/pricing-calculator, and keep only /guides/pricing-calculator in the sitemap. Inspect, test live, request indexing once, check back in two weeks.