Updated October 20, 2026

Get GSC Index for Chrome

Home › Extensions › GSC Index › Guides › Discovered – currently not indexed

Discovered – Currently Not Indexed: Why It Happens and What to Do

By the Pick Ads team · Tested on Chrome · Published October 20, 2026 · Updated October 20, 2026

Answer: "Discovered - currently not indexed" means Google knows the URL but hasn't crawled it yet. Google says it usually postponed the crawl because crawling then could have overloaded your site. For a few new pages, waiting is often enough. If many URLs are affected, fix server speed, duplicate URLs, and internal links before you request anything.

Quick steps

  1. Check whether the URLs are new or have been stuck for weeks.
  2. Look at server health and the number of low-value URLs.
  3. Link the important pages from pages that are already indexed.
  4. Request indexing for a small, prioritized set.

What the status means

Google's help center defines "Discovered - currently not indexed" this way: the page was found but not crawled yet. Typically Google wanted to crawl the URL, expected that crawling would overload the site, and rescheduled it. That's why the last crawl date is empty (Page indexing report – Search Console Help).

Discovered - currently not indexedCrawled - currently not indexed
Has Google fetched the page?NoYes
Last crawl date in URL InspectionEmptyHas a date
What Google is waiting onCrawl schedulingAn indexing decision about the page
Main leversServer capacity, URL inventory, internal linksContent value, duplication, internal links
Can the live test check this status?NoNo

Is it a problem?

Usually not, when the URLs are new and few, or are pages you don't need in Google, such as filters, sort orders, or internal search results. Google says a new site or page can take about a week to start being crawled, and that crawling can take up to a few weeks once a URL is known (Page indexing report).

Yes, it's worth acting on when important pages stay in this status for weeks, or when a large share of your site sits here. Google says sites in that second situation are part of the audience for its crawl budget guide (Optimize your crawl budget).

Causes

How Google schedules crawls is not fully public. The causes below match what Google documents about crawl capacity and crawl demand.

CauseHow to checkFix
New site or new sectionPublish dates. Is the site only a few weeks old?Wait about a week or two. Link the new pages from your homepage or hub pages.
Many URLs at once (large launch, faceted URLs, parameters)Count URLs in the sitemap vs pages that really matterConsolidate duplicates. Keep only canonical URLs in the sitemap.
Weak internal linksIs the URL linked only from the sitemap or a deep archive?Add descriptive <a href> links from relevant indexed pages (Link best practices)
Slow or erroring serverCrawl Stats host status. "Hostload exceeded" in URL Inspection.Improve response times. Fix 5xx and 429 responses. Add server capacity.
Low perceived valueLots of thin or near-identical pagesImprove or merge them. Google factors user value and content uniqueness into crawl resources.

Diagnose (10 minutes)

  1. Filter the report by sitemap. Are the affected URLs ones you submitted?
  2. Sample five URLs in URL Inspection. Confirm that Last crawl is empty and note the Referring page (URL Inspection tool).
  3. Run Test live URL on one of them. A pass means Google can fetch it now. Google states the live test doesn't check this status.
  4. Check server health. Look for 5xx or 429 errors and slow responses. Google lowers its crawl rate when it sees them.
  5. Count low-value URLs. If duplicates, filters, or soft 404s make up much of your inventory, they compete for crawling.

Fix order

  1. Fix server capacity and errors. Google's crawl capacity limit goes down when the site slows down or returns 5xx or 429 errors.
  2. Shrink the URL inventory. Consolidate duplicates. Return 404 or 410 for removed pages. Remove soft 404s.
  3. Strengthen internal links to the pages that matter.
  4. Clean the sitemap. Keep canonical URLs only, with accurate lastmod values (Build and submit a sitemap). See request indexing for a sitemap.
  5. Request indexing for a short priority list.

Does Request indexing help?

Sometimes, for a few important URLs. Google says there's a quota for individual URLs, that requesting the same URL again won't make it faster, and that a request doesn't guarantee inclusion. Google also says crawling can take from a few days to a few weeks (Ask Google to recrawl your URLs). If the cause is server capacity or too many URLs, requests won't fix it.

With GSC Index: after fixing the causes, put your highest-priority URLs in a list and request them over several days. Free covers 5 indexing requests on this browser. Premium ($9.99/month or $99.90/year) keeps the queue running across days, and Search Console's daily limit still stops each run. Google's quota doesn't change and indexing isn't guaranteed.

Wait or act?

SituationWaitAct
A few new URLs on a healthy siteYes, about one to two weeks (how long indexing takes)Add internal links
Important URLs stuck for several weeks–Check links and the server, then request a priority list once
A large share of the site in this status–Work on crawl budget: inventory, duplicates, server
URLs you don't need indexedIgnore themConsider removing them from the sitemap

The "wait" timings come from Google's documented ranges. The thresholds for acting are our recommendation, not Google's. Last verified: 2026-10-20

FAQ

Is this a crawl budget problem? Sometimes. Google's crawl budget guide is written for very large or fast-changing sites, and for sites with a large share of URLs in this status. For a small site with a few new pages, it's usually just scheduling. Check server health and duplicate URLs before assuming a crawl budget issue.

How many URLs trigger it? There's no number. Google describes rough site sizes for its crawl budget advice: over a million pages, or over 10,000 pages that change daily. It says these are not exact thresholds. Any URL can show this status while it waits to be crawled.

Should I use the sitemap? Yes. List only canonical URLs you want indexed, and keep lastmod accurate. Google uses lastmod only when it's consistently reliable. A sitemap is a hint, not a guarantee, so pair it with internal links from pages Google already indexes.

How long is normal? Google doesn't give a fixed time. Its documentation says new sites can take about a week, and crawling known URLs can take up to a few weeks. If important pages are still waiting after several weeks, check server health, duplicates, and internal links.

Add GSC Index to Chrome - Free

Sources

Last verified: 2026-10-20


AnchorTarget
Crawled - currently not indexed / Crawled – currently not indexedGI-01 {GSCI}crawled-currently-not-indexed
how long indexing takes / How long does Google take to index a page?GI-03 {GSCI}how-long-does-google-take-to-index-a-page
request indexing for a sitemap{GSCI}request-indexing-for-a-sitemap
Bulk actions in Google Search ConsoleSC-00 /extensions/search-console-tools
GSC Indexproduct page

Open items

  1. [VERIFY] Chrome version and dates. [VERIFY] the "Test live URL" label.
  2. [SCREENSHOT] Report row and URL Inspection with an empty Last crawl.
  3. GSC Index limits and price per getpickads.com, 2026-10-20.
  4. Style decided: en dash in title and H1; plain hyphen when quoting Google's label.
  5. GI-01, GI-03 and SC-00 must be live before publishing.

Checklist cho Ngọc

  • Placeholder còn lại: 5 (4 [VERIFY], 1 [SCREENSHOT]).
  • Cần kiểm trên sản phẩm thật: nhãn "Test live URL", ảnh chụp URL Inspection có Last crawl trống.
  • Link nội bộ cần xác nhận: GI-01, GI-03, SC-00 (chưa live); request-indexing-for-a-sitemap đã live.