# Discovered, currently not indexed: why Google has not crawled the page You see Discovered, currently not indexed in Search Console. Google knows the URL but has not fetched it. Here is how to tell if the page is worth indexing, how to earn a crawl, and what to change on your site so this reason clears. Updated 2026-09-14 · Source: https://porteur.ai/guides/discovered-currently-not-indexed ## What Discovered, currently not indexed means 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. ## How it differs from Crawled, currently not indexed 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. ## Why this happens on your site - 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. > Rule: only list URLs you want indexed in the sitemap. Leave out redirects, noindex pages, tag noise, and internal search results. ## Check the URL with URL Inspection 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. **Open URL Inspection in Search Console** Paste the full URL from your site. It must be within a verified property. 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. **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. **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. **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. ## Cut junk URLs so the good pages get fetched 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. > Warning: do not block a URL in robots.txt if you want it indexed. Blocking prevents crawl. Google might index the URL without content, which helps no one. ## Fix the sitemap: only the pages that deserve indexing 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. **List only indexable pages** Exclude noindex, redirects, 404s, login walls, tag noise, and internal search results. Each URL should be canonical to itself. 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. **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. **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. ## Add internal links from pages Google already crawls 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. **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. **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. **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. **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. ## Use Request indexing and Validate fix at the right time 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. ## Set a date, then track crawl and indexation 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. ## What a fixed page looks like 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. ## Questions ### What does Discovered, currently not indexed mean in Search Console? Google knows the URL from a link or a sitemap but has not fetched it yet. It is pacing crawl, or it expects low value. This is common on new sites and on large sites. Earn the crawl with internal links and a clean sitemap, and prune junk URLs that waste attention. ### How is Discovered, currently not indexed different from Crawled, currently not indexed? Discovered was never fetched. Crawled was fetched and set aside. For Discovered, you fix access and discovery: links, sitemap, and waste. For Crawled, you improve the page’s quality, duplication, and signals, and you still keep links and sitemap tidy. ### Will Request indexing fix Discovered, currently not indexed? It can help queue a crawl, but it is not a guarantee. Use it after you add internal links, fix directives, and tidy the sitemap. There is a small daily quota per property, so use it sparingly on pages that matter. ### Should I block low value URLs in robots.txt to save crawl budget? Block if you never want those URLs crawled. Do not block pages you want indexed. Google can index blocked URLs without content if they are linked, which is not useful. Prefer removing links to junk URLs, adding noindex where suitable, and consolidating duplicates with canonicals. ### How long does it take to clear this status? Expect one to two weeks for small clean sites once you add links and fix the sitemap. Large sites or bigger clean ups can take longer. Use Validate fix on systemic issues, and track progress in the Page indexing and Sitemaps reports. ### How do I check if the page is indexed now? In URL Inspection, check “URL is on Google”. You can also search site:yourdomain.com and the full URL, but Search Console is the source of truth. The tool shows last crawl date and whether Google selected a different canonical. ## Read next - [Crawled, currently not indexed: what it means and what to do](https://porteur.ai/guides/crawled-currently-not-indexed): What “Crawled, currently not indexed” means in Search Console, how to tell why it happened on your site, and what to change that gets pages indexed. - [How to use the URL Inspection tool in Search Console](https://porteur.ai/guides/url-inspection-tool): Read each panel, run Test live URL, and know when to request indexing. Fix new pages, dropped pages, and canonicals Google ignores. - [The Sitemaps report: what Success, Has errors and Couldn’t fetch mean](https://porteur.ai/guides/search-console-sitemaps-report): How to submit your sitemap URL, read Success, Has errors and Couldn’t fetch, and fix invalid XML, 404s, cross‑host URLs and missing child sitemaps. - [Internal linking for a small site: which pages link to which](https://porteur.ai/guides/internal-linking-for-seo): Decide which pages rank. Build hubs, write clear anchors, fix orphans, and crawl your site to map links you control. - [Orphan pages: finding the pages nothing links to](https://porteur.ai/guides/orphan-pages): Find orphan pages on your site, why they happen, how to compare crawl, sitemap and Search Console, and what to do: link, merge, redirect or remove. - [Crawl budget](https://porteur.ai/glossary/crawl-budget): Crawl budget is how much Googlebot crawls your site. It matters on sites with thousands of URLs. Here is how to check it and avoid wasting it. - [Pagination](https://porteur.ai/glossary/pagination): How to set up pagination for SEO after 2019: self-canonicals, real links, view-all for short lists, and infinite scroll with crawlable pages. Paste your URL and get a free check that reads your site, the searches around it and the rivals on them in about thirty seconds, and shows three findings whole before you connect anything. Free check: https://porteur.ai/