You open the Pages report in Search Console and a block of URLs sits under Discovered – currently not indexed. Nothing is technically broken: no 404s, no noindex, no robots.txt block. Google simply knows these pages exist and has not got round to fetching them.
This guide treats the status as a symptom. For each likely cause you get the evidence that confirms or rules it out, then the fix. At the end there is a short action plan for the next one to two weeks and a way to check whether it worked.
What the status literally means
Google finds URLs through links, sitemaps and other sources and puts them in a queue to be crawled. “Discovered – currently not indexed” means the URL is in that queue but has not been fetched yet. Google has not seen the content, so it has not made any judgement about its quality. Open one of the URLs in the URL Inspection tool and you will usually see the “Last crawl” field empty or shown as N/A. That empty field is the clearest sign you are dealing with a scheduling problem, not a content problem.
Google’s own explanation in the Page indexing report help is that the crawl was postponed, typically because crawling the site at that moment looked likely to overload it. In practice it also shows up when Google sees no strong reason to prioritise a URL. Either way, the job is to make the URLs easier and more worthwhile to crawl.
| Discovered – currently not indexed | Crawled – currently not indexed | |
|---|---|---|
| Has Google fetched the page? | No | Yes |
| “Last crawl” in URL Inspection | Empty / N/A | Has a date |
| Has Google judged the content? | Not yet | Yes, and chose not to index it for now |
| Typical causes | Crawl capacity, server load, low priority, weak discovery signals | Thin, duplicate or low-value content; weak signals of importance |
| Where to focus | Server health, crawl waste, internal links | Content quality, uniqueness, canonicals |
If your URLs have already moved to the second column, read the Crawled – currently not indexed guide instead: the fixes are different.
When it is normal and resolves on its own
A freshly published page, a newly submitted sitemap or a batch of new product pages will often sit in this state for days, sometimes a few weeks, and then get crawled without you doing anything. A handful of URLs here on a healthy site is not a problem. Start worrying when the count keeps growing, when important pages stay here for weeks, or when most of a new section never leaves it.
Cause 1: crawl capacity, slow responses and 5xx errors
Google adjusts how fast it crawls to how well your server copes. Slow responses, timeouts and server errors make it back off, and new URLs wait longer.
How to tell
- Open Settings > Crawl stats in Search Console. Look at the host status section and the response breakdown: any recent server errors, DNS or connectivity problems?
- Check the average response time chart. A rising trend, or spikes that line up with the period the backlog grew, points at the server.
- In the Pages report, look for “Server error (5xx)” alongside the discovered URLs.
- If you can read server logs, check how Googlebot requests are answered and how long they take.
What to do
- Fix the source of 5xx errors and timeouts first: hosting limits, database queries, plugins, rate limiting or a firewall that blocks or throttles Googlebot.
- Cache HTML where you can and cut slow server-side work on templates that serve many URLs.
- Once errors stop, Google tends to increase crawling again gradually. Do not expect an instant jump.
Cause 2: too many low-value or parameter URLs competing for crawl
Crawl budget is mostly a concern for large or fast-changing sites, but any site can generate far more URLs than it has real pages. Filters, sort orders, session or tracking parameters, internal search results and endless calendar or tag pages all compete with the pages you actually want crawled.
How to tell
- Export the discovered URLs from the Pages report and sort them. Lots of
?sort=,?filter=,?page=or similar variants is a strong signal. - In Crawl stats, look at the example URLs Googlebot fetched. Are they the pages you care about or parameter variations?
- Compare the number of URLs Google knows about with the number of pages you would actually want indexed.
What to do
- Stop generating crawlable links to useless variants, for example by not linking every filter combination with a plain
<a href>. - Use robots.txt to block crawling of URL patterns that should never be fetched, such as internal search results. Remember robots.txt controls crawling, not indexing.
- Point duplicates to the main version with rel=canonical as described in Google’s guide to consolidating duplicate URLs. It is a hint, but it helps.
- Keep your sitemap clean: only canonical, indexable URLs that return 200.
Cause 3: weak internal linking and orphan pages
A URL that appears only in the sitemap, with no internal links pointing to it, tells Google very little about its importance. Pages buried many clicks deep behind pagination are in a similar position.
How to tell
- Crawl your site with a desktop crawler and compare the URLs it finds with your sitemap. Sitemap URLs the crawler never reached are orphans.
- Check click depth for the stuck URLs. Pages that are only reachable deep in paginated lists are common in this status.
- Make sure links are real
<a href>elements in the HTML, not buttons or JavaScript click handlers.
What to do
- Link to the stuck pages from strong, frequently crawled pages: the homepage, category hubs, popular articles.
- Use descriptive anchor text and avoid nofollow on internal links.
- Reduce depth with hub pages and related-content blocks. The internal linking guide covers this step by step.
Cause 4: the page is seen as low priority
Google decides what to crawl next partly by how valuable a URL is likely to be. If a section of the site has historically produced thin or near-duplicate pages, new URLs that look similar can be pushed back in the queue.
How to tell
- The stuck URLs share a template or pattern: tag pages, auto-generated location pages, near-identical product variants.
- Similar pages already crawled from the same section show up as “Crawled – currently not indexed” or as duplicates.
- The pages have no external links and few internal ones.
What to do
- Improve or consolidate the template: merge thin variants, add unique content, remove pages that serve no searcher.
- Mark pages you do not want in search with noindex, as explained in Google’s guide to blocking indexing, or remove them, so the remaining ones look stronger as a set.
- Earn genuine links to the pages that matter. Do not buy links or join link schemes.
Cause 5: the site is very new
A new domain has no crawl history and few links, so Google crawls it cautiously. Publishing hundreds of pages at launch often means most of them wait in this status for a while.
How to tell
- The property was created recently and the site has few or no backlinks.
- Crawl stats show low but healthy activity: no errors, just not many requests.
What to do
- Submit a clean sitemap (see the sitemap submission guide) and make sure your most important pages are linked from the homepage.
- Publish steadily rather than all at once, and focus first on the pages that deserve to rank.
- Be patient. On a new site, this status usually shrinks as Google builds trust in the domain.
A 7–14 day action plan
- 01
Day 1: export and group
Export the URLs from Indexing > Pages > “Discovered – currently not indexed”. Group them by pattern: real pages, parameter variants, tags, pagination.
- 02
Day 1–2: check server health
Review Crawl stats for errors and response time. If there are 5xx errors or timeouts, fix those before anything else.
- 03
Day 2–4: cut crawl waste
Remove links to useless variants, block hopeless URL patterns in robots.txt, add canonicals, and clean the sitemap so it lists only canonical, indexable 200 URLs.
- 04
Day 3–5: link the pages that matter
Add internal links from strong pages to the URLs you want indexed and reduce their click depth.
- 05
Day 5: request crawling for priority URLs
Use “Request indexing” in URL Inspection for a few key URLs (it has a daily quota and repeating it does not help). For larger batches, a crawl request service such as WeRankLab’s URL indexing tool can get them fetched; it does not guarantee indexing.
- 06
Day 5–7: resubmit the sitemap
Resubmit the cleaned sitemap in Sitemaps and check that it is read without errors.
- 07
Day 7–14: watch and validate
Check URL Inspection on sample URLs for a “Last crawl” date, and start validation in the Pages report.
How to validate the fix in Search Console
Success comes in two stages. First the URLs get crawled: in URL Inspection the “Last crawl” field gets a date. Then Google decides whether to index them. A URL can move from “Discovered” to “Crawled – currently not indexed”, which means the scheduling problem is solved and the question is now one of quality.
- In Indexing > Pages, open the “Discovered – currently not indexed” reason and click Validate fix once your changes are live.
- Validation runs over days to weeks. Keep an eye on the count and on the URLs that move to other reasons.
- Spot-check important URLs in URL Inspection rather than relying only on the chart, which lags behind by a few days.
- If URLs land in “Crawled – currently not indexed”, switch to the fixes in that guide.
Checking many URLs at once
URL Inspection works one URL at a time. If you need to know which of a few hundred URLs are now indexed, a bulk index checker is faster.
If nothing changes after a couple of weeks, go back to the evidence. A persistent backlog almost always traces back to one of the causes above, and most often to more than one at the same time. The page not indexed overview can help if the URLs show up under other reasons as well.