Discovered Currently Not Indexed: What It Means and How to Fix It
Discovered currently not indexed means Google found a page but has not crawled it yet. Here is what causes it and how to fix it, in order: duplicate URLs, server load, internal links, thin pages, sitemaps and indexing requests.
Discovered Currently Not Indexed: The Short Version
Discovered currently not indexed is a status in Google Search Console that means Google knows a page exists but has not crawled it yet. It is not a penalty. It is a queue.
Google's own definition is short. In the Page indexing report, it says the page "was found by Google, but not crawled yet." It adds that Google usually wanted to crawl the URL, but doing so "was expected to overload the site; therefore Google rescheduled the crawl." That is why the last crawl date for these pages is empty in the report.
For a small business site, a few URLs in this group is normal. A large share of your important pages stuck here is a sign to act. This guide explains the causes and the fixes, in the order we would work through them. We have not run tests on any site for this post. Every check below is one you can run in your own Search Console.
What the Status Does and Does Not Mean
Search Console's Page indexing report sorts URLs into indexed and not indexed, with a reason for each. Two reasons look alike and are often mixed up:
- Discovered, currently not indexed. Google found the URL, usually through a link or a sitemap, but has not fetched it.
- Crawled, currently not indexed. Google fetched the page and chose not to index it. Google says such a page "may or may not be indexed in the future; no need to resubmit this URL for crawling."
The difference matters. With discovered currently not indexed, Google has not seen the content yet, so the page itself has not been judged. The cause is usually about the site as a whole: how fast the server responds, how many URLs compete for attention, and how strongly the page is linked.
It also helps to know that Google does not plan to index everything. The report says plainly: "Don't expect every URL on your site to be indexed." Filtered URLs, tag archives and old test pages can sit in this group for good, and that is fine.
Step 1: Confirm Which Pages Are Affected
Start by checking whether the pages in the list are ones you care about.
- In Search Console, open Indexing, then Pages. Under "Why pages aren't indexed," click the discovered currently not indexed row to see the example URLs.
- Export the list. Mark each URL as keep (a real service, product, location or blog page) or ignore (parameters, filters, internal search results, duplicates).
- For each keep URL, run it through the URL Inspection tool. Google's report says "To find the index status of a specific page, use the URL Inspection tool." The report can lag behind the live index, so a page may already be indexed.
If only junk URLs show as discovered currently not indexed, the job may be to stop creating them, not to get them indexed. If key service or product pages are in the list, keep going.
Step 2: Remove the URLs That Should Not Exist
The most common cause of discovered currently not indexed at scale is a site that creates far more URLs than it has real pages. Google's crawl budget guide advises: "Eliminate duplicate content to focus crawling on unique content rather than unique URLs."
Places to look:
- Filter and sort parameters. Ecommerce sites can turn one collection into thousands of URLs through color, size and sort options. Our Shopify SEO checklist covers how to handle filtered and variant URLs.
- Trailing-slash and case variants. If both /services and /services/ return a working page, pick one and redirect the other.
- Soft 404s. Empty category or "no results" pages that return a 200 status. Google's guide warns that "soft 404 pages will continue to be crawled, and waste your budget."
- Redirect chains. Google says to "Avoid long redirect chains, which have a negative effect on crawling." Point old links straight to the final URL.
Use robots.txt with care. Google notes that "Blocking URLs with robots.txt prevents Google from crawling them," which suits truly useless URL patterns. It also says "Don't use robots.txt to temporarily reallocate crawl budget."
Step 3: Check Whether Your Server Is Slowing Google Down
Google's definition of discovered currently not indexed points straight at server load: the crawl was rescheduled because it was expected to overload the site. Google's crawl budget guide explains that its crawlers set a "crawl capacity limit (also known as hostload)," which limits how much time your server spends handling Google's requests.
If your server answers slowly or returns errors, Google crawls less. Checks you can run:
- In Search Console, open Settings, then Crawl stats. Look at average response time and the share of server errors over the last 90 days.
- Look in the Page indexing report for "Server error (5xx)" rows. Errors there often travel with a crawl backlog.
- Ask your host whether a firewall or bot filter is rate-limiting Googlebot.
Google's Martin Splitt said in a video, as reported by Search Engine Roundtable, that site owners should "Make sure, as well, that your server isn't giving Googlebot signals that it is overwhelmed when it's crawling." Google's guide also advises: "Optimize your server response times and resources to make pages load faster."
Step 4: Link to the Pages You Want Indexed
Google finds new pages mostly through links. Its link guidance says Google uses links "to find new pages to crawl" and that "Every page you care about should have a link from at least one other page on your site."
Pages that only appear in a sitemap, with no links from the rest of the site, often wait longest. Fixes:
- Link each service and location page from your main navigation or a services hub.
- Add links from related blog posts to the service page they support, using plain, descriptive anchor text.
- Use standard <a href> links. Google says it "can only crawl your link if it's an <a> HTML element" with an href. Buttons that only work through JavaScript may not count.
- Check that no important page is linked only from a page that is itself not indexed.
This is one of the fastest fixes for Google not indexing pages on a small site, because it costs nothing and you control it.
Step 5: Raise the Quality of What Google Has Already Seen
Google has not read a page stuck in discovered currently not indexed, but it has read the rest of your site. When much of that is thin or repetitive, Google may give the new pages less priority.
In the same video, Splitt said: "When Google Search notices a pattern of low quality or thin content on pages, they might be removed from the index." He added that if you care about such pages, "you might want to rework the content to be of higher quality." Helen Pollitt makes a similar point in a Search Engine Journal column: Google may judge pages it has not visited by the quality of the pages it has.
What to look for:
- Location pages that are copies with the town name swapped.
- Product pages that reuse the maker's description word for word.
- Tag and archive pages with one or two posts each.
- Old blog posts with a few lines of text.
Merge, rewrite or remove these. A smaller site with stronger pages tends to get crawled more fully than a large site with many weak ones.
Step 6: Use Sitemaps and Request Indexing the Right Way
Once the causes above are fixed, help Google find the discovered currently not indexed pages again.
Sitemaps
Include only the canonical URLs you want indexed. Google says "Google reads your sitemap regularly, so be sure to include all the content that you want Google to crawl." Its sitemap guide also notes that a sitemap "doesn't guarantee that all the items in your sitemap will be crawled and indexed." For a small site of "about 500 pages or fewer" that is well linked, Google says you may not need one at all, though most site platforms create one anyway.
Request indexing
For a handful of key pages, use the URL Inspection tool and click Request indexing. Google's recrawl guide warns that "there's a quota for submitting individual URLs" and that "requesting a recrawl multiple times for the same URL won't get it crawled any faster." Ask once per page, then wait.
Validate the fix
In the Page indexing report, open the reason and click Validate Fix. Google asks you to do this "When you've fixed all instances of an error or warning."
The Fix Order at a Glance
Seven steps, in the order we work through them.
Sort the list
Export the affected URLs and mark each one keep or ignore.
Inspect the keepers
Run each important URL through URL Inspection to confirm its current status.
Cut duplicate URLs
Fix parameters, slash variants, soft 404s and redirect chains.
Check server health
Review Crawl stats for slow responses and server errors, and ask your host about bot limits.
Add internal links
Link each key page from navigation or a hub and from related posts.
Improve thin pages
Merge, rewrite or remove weak pages so the site reads as useful overall.
Resubmit and wait
Update the sitemap, request indexing once for key pages and click Validate Fix.
How Long Discovered Currently Not Indexed Takes to Clear
There is no fixed timeline. Google's recrawl guide says "Crawling can take anywhere from a few days to a few weeks," and that "Requesting a crawl does not guarantee that inclusion in search results will happen instantly or even at all."
Sometimes patience is the whole answer. Splitt said "sometimes it's just a matter of a bit more patience on your end to get this result." A brand new page on a new site can sit in the queue for a while before anything is wrong.
A useful rule: if a key page is still stuck after several weeks, and you have worked through the steps above, look again at internal links and site quality. Those are the two causes that most often remain.
Where Kause Fits In
Kause Marketing Agency is a Maryland SEO agency based in Randallstown, in Baltimore County. Crawl and indexing issues are a core part of our technical SEO work, and our SEO audit reviews the Page indexing report, crawl stats, duplicate URLs and internal links together. For online stores, our ecommerce SEO page covers filtered and variant URLs.
Our Foundation audit is $1,200 and the Deep-Dive audit is $3,500. Monthly SEO starts with Local Starter at $1,500 a month, with a 90-day minimum and then month-to-month. See every plan on our pricing page.
Want a quick read first? The free SEO audit is a 30-minute review call plus a short written snapshot of your top issues, usually within 48 hours.
Indexing Questions
Short answers to what site owners ask about this status.
Discovered currently not indexed means Google found the URL but has not crawled it yet. Google's report says it usually rescheduled the crawl because crawling then was expected to overload the site.
No. It is a crawl queue, not a manual action. Manual actions appear in their own report in Search Console.
With crawled, currently not indexed, Google fetched the page and decided not to index it for now. With discovered, Google has not fetched it at all, so the fixes focus on links, duplicate URLs and server health.
No. Google says repeated requests for the same URL do not speed up crawling, and there is a quota. Request once for key pages, then fix the causes.
There is no set number. A few filtered, tag or test URLs is normal. If your main service, location or product pages are in the list, it is worth working through the fixes.
Get Help With Discovered Currently Not Indexed Pages
Book a free 30-minute review call. We will send a short written snapshot of your top issues, usually within 48 hours, including any pages Google has found but not indexed.