Discovered - Currently Not Indexed: What It Means and Fixes
Search Console says some pages are "Discovered - currently not indexed" — Google knows the addresses exist but has not visited them yet, usually because it decided they could wait.
Common signs of this issue
- Search Console's Pages report lists "Discovered - currently not indexed" under "Why pages aren't indexed".
- Clicking the reason shows example URLs with no last crawl date at all.
- Inspecting one of those pages says "URL is not on Google" and the crawl section says the page has not been crawled.
- The affected pages are often newer ones, or pages deep in the site such as blog posts, product pages, or tag and category archives.
- The count went up after you published a lot of pages at once or added a big batch of products.
- The site has been slow, overloaded, or showing errors recently.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Open Search Console, then Indexing, then Pages, click Discovered - currently not indexed, and read the example URLs. Decide which are pages a customer would actually search for and which are clutter like tag pages, feed URLs, filtered shop links or search results.
- For one important page in the list, use URL Inspection and click Test live URL. If the live test succeeds, Google can reach the page — it just has not prioritised it. If the live test fails, you have found a technical problem to pass to your developer.
- Check how that page is linked from the rest of your site. Can you reach it from the menu, the homepage, or a related page in two or three clicks? A page that exists only in the sitemap gives Google little reason to hurry.
- Look at the overall size of the site versus what it offers. If a ten-page business site has generated hundreds of thin archive, tag or parameter URLs, Google may be spreading its attention across junk. Ask your developer whether those can be set to noindex or removed from the sitemap.
- In Search Console, open Settings, then Crawl stats and look at the average response time and the host status. Slow responses or server errors make Google crawl less, and that is a hosting conversation rather than a content one.
- Check your sitemap only lists real, live pages you want indexed — not redirected addresses, deleted pages, or test pages. A cleaner sitemap is a clearer signal.
- After strengthening links to your key pages, request indexing for a handful of the most important ones using URL Inspection. Then leave it for a couple of weeks before judging the result.
What this usually means
Discovered - currently not indexed means Google has learned about the URL — from your sitemap or a link — but has not fetched it yet. Google's own explanation is that it wanted to crawl the page but expected that doing so might overload the site, so it rescheduled. In practice it is a priority decision: Google has a queue for your site and these pages are near the back.
On small sites the usual reasons are weak internal linking (the page is orphaned or buried), a server that responds slowly so Google crawls gently, or a flood of low-value URLs that dilutes attention from the pages that matter. On larger shops and blogs it is often simply volume — Google crawls a site at the pace it thinks the site deserves, and new pages wait their turn.
This is different from Crawled - currently not indexed, where Google did visit and decided not to include the page. Discovered pages have not been judged on quality yet. That makes the status often more fixable: better links, a faster server and a tidier sitemap tend to move these pages into the crawl. If only unimportant URLs are in the list, there is nothing you need to do.
What not to do
- Don't worry about URLs in this list that nobody would search for. Tag archives, feeds and filtered pages are fine to leave out.
- Don't click Request indexing on dozens of pages every day. There is a daily quota, and it will not change how Google prioritises the whole site.
- Don't buy indexing tools that promise to push URLs through Google's Indexing API. That API is meant only for job posting and livestream pages.
- Don't publish hundreds of pages at once with little content on each. Large batches of thin pages are a common way to end up with this status.
- Don't click Validate fix until you have actually changed something like links, speed or the sitemap.
- Don't block the pages in robots.txt to make the status go away. That hides the pages from Google entirely and creates a different problem.
When to get help
If your money pages — services, locations, top products — are sitting in Discovered - currently not indexed for more than a few weeks, it is reasonable to get help. Someone experienced can check crawl stats, server response times and how your site links internally, and tell you whether the fix is technical (hosting speed, a sitemap full of junk URLs, a crawl trap generating endless addresses) or structural (key pages too deep in the site). That is worth knowing before you spend money on more content or a hosting upgrade you may not need.
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Frequently asked questions
What does Discovered - currently not indexed mean?
Google knows the page exists but has not crawled it yet. It has put the page in its queue and decided to come back later, often because it is pacing itself on your site or does not see the page as a priority.
Is Discovered - currently not indexed bad?
Not necessarily. Many sites have unimportant URLs in this list and that is fine. It only matters if pages you want customers to find are stuck there for weeks.
How long do pages stay in Discovered - currently not indexed?
There is no fixed time. Some pages move within days, others wait weeks. Pages that are well linked from the rest of your site and served quickly tend to be crawled sooner.
What is the difference between Discovered and Crawled - currently not indexed?
Discovered means Google has not visited the page yet. Crawled means it visited and chose not to index it. Discovered usually points to crawl priority or server speed; Crawled usually points to page quality or duplication.
Can slow hosting cause Discovered - currently not indexed?
Yes. Google slows its crawling when a server responds slowly or returns errors. The Crawl stats report in Search Console Settings shows response times and any host problems.
Should I resubmit my sitemap to fix it?
Resubmitting an unchanged sitemap does little. Cleaning it so it only lists live pages you want indexed, then letting Google reread it, is more useful.