In short
Discovered – currently not indexed: Google knows the URL but has not fetched it yet. Usually the cause is crawl capacity, server speed or weak internal linking. Crawled – currently not indexed: Google fetched the page and decided not to index it for now. Usually the cause is the value or uniqueness of the content. Fix the cause first; requesting indexing on its own changes nothing.
What the two statuses mean
Every URL goes through the same pipeline: Google discovers it (from links or a sitemap), puts it in a crawl queue, crawls it, renders and evaluates the content, and only then decides whether to index it. The two statuses tell you at which point the URL stopped.
Discovered – currently not indexed
Google has found the URL, usually through an internal link or a sitemap, but has not fetched the page yet. The Last crawl field for these URLs is empty. Typical reasons: the site has more URLs than Google is willing to crawl right now, or the server responds slowly, so Google reduces its request rate.
Crawled – currently not indexed
Google has fetched the page and read it, but decided not to add it to the index for now. In most cases this is a judgement about the page's value compared with other pages on your site or on the web, not a technical error.
| Discovered – not indexed | Crawled – not indexed | |
|---|---|---|
| Stage reached | Known URL, waiting in the crawl queue | Fetched and evaluated |
| Last crawl date | Empty | Filled in |
| Nature of the problem | Crawling: capacity, priority, architecture | Quality: value, uniqueness, rendering |
| Main causes | Slow or failing server, too many low-value URLs, few internal links | Thin pages, near-duplicates, empty pages, failed JavaScript rendering |
| Check first | Crawl Stats report, internal links to the URL | URL Inspection: rendered HTML and Google-selected canonical |
| First fix | Faster server, prune URL spaces, link from strong pages | Improve, differentiate or merge the content |
What Google officially says
Google's own wording is short, so it is worth knowing exactly what is and is not said.
“The page was crawled by Google but not indexed. It may or may not be indexed in the future; no need to resubmit this URL for crawling.”
Google Search Console Help, Page indexing report — Crawled – currently not indexed“The page was found by Google, but not crawled yet.”
Google Search Console Help — Discovered – currently not indexed. Google explains that typically it wanted to crawl the URL, but this “was expected to overload the site”, so the crawl was rescheduled. That is why the last crawl date is empty.“Don't expect every URL on your site to be indexed.”
Google Search Console Help, Page indexing reportThree more official points matter for the fix:
- After a fix you can press Validate fix. “Validation typically takes up to about two weeks”, sometimes longer.
- “Indexing is never instant, even when you submit a crawl request directly.”
- The live test in URL Inspection “doesn't test all the issues covered by the Page indexing report”, so a passing live test does not prove the page will be indexed.
Google's crawl budget guide also names a large share of Discovered URLs as a typical crawl budget symptom. Crawl budget work, however, is aimed mainly at “Large sites (1 million+ unique pages) with content that changes moderately often” or sites with “10,000+ unique pages” and daily changes. Google calls these “not exact thresholds”. On a small site, Discovered URLs usually point to linking or server problems, not to crawl budget.
Why it happens: Discovered – currently not indexed
The URL is known but not fetched. That points to crawling: how much Google can crawl and what it considers worth crawling first.
Slow or failing server Discovered
“Google wants to crawl your site without overwhelming your servers.” If responses are slow or return 5xx errors, Googlebot backs off and new URLs wait in the queue.
Too many low-value URLs Discovered
Faceted filters, sorting and tracking parameters, session IDs, tag and archive pages, endless calendar pages. “Without guidance from you, Google tries to crawl all or most of the URLs that it knows about on your site”, so these URLs compete with the pages that matter.
Weak internal linking Discovered
A URL that exists only in the sitemap, with no links from pages Google already crawls, gets a low priority. A sitemap is a hint, not an instruction to crawl.
New site or section with low popularity Discovered
“URLs that are more popular on the Internet tend to be crawled more often.” A fresh section with no links pointing to it gets crawled slowly.
Sitemaps full of the wrong URLs Discovered
Redirected, non-canonical or noindex URLs in a sitemap send mixed signals and use up crawling on pages you do not want indexed.
Why it happens: Crawled – currently not indexed
Google has seen the page. In most cases the decision is about the content, so look at the page the way a reader would.
Thin or low-value content Crawled
A product page with only a name and a price, or a short post that answers nothing. Length alone is not the issue: the page simply gives too little that is useful.
Near-duplicate pages Crawled
Product variants that differ only by colour or size, location pages where only the city name changes, printer-friendly versions. Google keeps one version and leaves the rest out.
Nothing new compared with indexed pages Crawled
Two listing pages with the same products and the same descriptions, or an archive post that repeats a current one. One of them is enough for search.
Scaled content without added value Crawled
Pages produced in bulk, whether by templates or AI, that add no data, experience or insight of their own. How the text was made matters less than whether it is useful.
Pages that are empty in practice Crawled
An empty category or a “no results” page that returns 200 OK. Google treats it as having no content worth indexing (often reported as a soft 404).
Main content depends on JavaScript that failed Crawled
If the text only appears after scripts run and rendering fails, Google sees a nearly empty page.
The page is very new Crawled
Sometimes Google simply has not finished evaluating a fresh page. Give it time before rewriting it.
How to diagnose it step by step
Work with groups of URLs, not single pages. A pattern tells you the cause much faster than one example.
| Reason | Source 1 | Validation | Trend | Pages |
|---|---|---|---|---|
| Discovered – currently not indexed 2 | Google systems | Not started | 3,921 | |
| Crawled – currently not indexed | Google systems | Not started 3 | 1,284 | |
| Alternate page with proper canonical tag | Website | Not started | 642 | |
| Page with redirect | Website | Not started | 310 | |
| Not found (404) | Website | Not started | 88 |
- 1Source: Google systems means the decision was Google's, not caused by your tags such as noindex or canonical.
- 2Click a row to open example URLs, export them and group them by folder, template or parameter.
- 3After fixing the cause, open the row and press Validate fix. Validation typically takes up to about two weeks.
- Export the examples. In the Page indexing report open each of the two statuses and export the example URLs.
- Group by pattern. Folder, page template, URL parameter, publication date. Is it all
/tag/pages? All?color=variants? All posts from one month? - Decide whether the group should be indexed at all. If not, there is nothing to fix. Just keep these URLs out of sitemaps and internal links (see “When you should not worry”).
- Inspect a sample. Use URL Inspection on a few URLs from each group: last crawl, Google-selected canonical, rendered HTML. Is the main content actually there?
- Check server health. Settings → Crawl stats: host status, response times, share of 5xx responses.
- Count internal links. How many crawlable pages link to these URLs? Zero or one link is a strong signal for Discovered.
- Compare with indexed siblings. For Crawled, put the page next to a similar indexed page. Is it thinner? Almost the same?
- Check the sitemap. It should list only canonical URLs that return 200, with accurate
lastmod.
How to fix it
Fixes for Discovered – currently not indexed
- Make the server fast and stable. Fix 5xx errors and timeouts first; then work on response time (hosting, caching, CDN, slow database queries).
- Close off low-value URL spaces. Use robots.txt to stop crawling of filters and parameters that waste crawling, or noindex for pages that may be crawled but should not be indexed. Do not combine both on the same URL: a URL blocked in robots.txt is never fetched, so Google cannot see its noindex. Remove these URLs from sitemaps.
- Link from strong pages. Add links to the important URLs from the home page, category pages, hubs and well-visited articles. Internal links are the most reliable way to tell Google what matters.
- Keep sitemaps clean. Only canonical URLs that return 200, with a
lastmodthat changes only when the content changes. - Build popularity for new sections. Mentions and links from other sites, plus links from your own established pages.
Fixes for Crawled – currently not indexed
- Improve or merge thin pages. Add what the reader actually needs: data, specifications, comparisons, examples. If a page cannot stand on its own, merge it into a stronger page and redirect it with a 301.
- Make every page clearly different. Pages on close topics need different angles, data and answers, not just different headings.
- Consolidate duplicates. Point variants to the main version with
rel="canonical", or merge them. - Remove what should not exist. Return a real 404 or 410, or add noindex, for empty and useless pages.
- Put the main content in the HTML. Use server-side rendering or static generation for important content, and check the rendered HTML in URL Inspection.
- Then ask Google to look again. Request indexing for a few key URLs and press Validate fix for the whole group. Do this once, after the fix, not instead of it.
Do not noindex pages you want to rank “to clean up the report”. The number in the report will go down, but the pages will also be gone from search for good.
Find the causes on your own site
OurSEO Tools crawls up to 1,000 pages and checks indexability, canonicals, status codes, response time, internal links, duplicates and thin content: the usual reasons behind both statuses.
When you should not worry
A “not indexed” URL is not automatically a problem. These are usually fine to leave out of the index:
- Pagination
/blog/page/7/when the posts themselves are indexed - Filters and sorting
?color=red&sort=priceunless you built them as landing pages - Internal search
/search?q=…results are not meant for Google - Old tag and archive pagesthat bring no traffic
- Brand-new pagesin their first days or weeks
- A small share on a big sitea few dozen URLs out of tens of thousands
It becomes a problem when important pages are on the list: products, categories, services, articles you want to rank, or when the numbers grow week after week.
Common mistakes and myths
- ✕“Request indexing will fix it.”It only puts the URL back in the queue. If the cause stays, the status stays. Repeated requests do not help.
- ✕“A sitemap guarantees indexing.”A sitemap helps discovery. Google still decides what to crawl and index.
- ✕“It's a penalty.”No. It is not a manual action; Google is selecting what to index. Manual actions have their own report.
- ✕“Every page must be indexed.”Google says directly: “Don't expect every URL on your site to be indexed.”
- ✕“Adding more words will fix it.”Usefulness and uniqueness matter, not word count. A short page with unique information can be indexed; a long duplicate may not be.
FAQ
What is the difference between Discovered and Crawled – not indexed?
Discovered: Google knows the URL but has not fetched it. Crawled: Google fetched and evaluated the page and decided not to index it for now.
Why are my pages “Discovered – currently not indexed”?
Most often because of a slow or failing server, too many low-value URLs competing for crawling, or weak internal linking. On very large sites crawl budget plays a role too.
Why are my pages “Crawled – currently not indexed”?
Google read the page and found it thin, a near-duplicate or less useful than other pages. Sometimes the main content did not render because of JavaScript.
Should I request indexing for these URLs?
Only for a few key URLs and only after you have fixed the cause. Google notes that “Indexing is never instant, even when you submit a crawl request directly.”
How long does Validate fix take?
According to Google, “Validation typically takes up to about two weeks”, and it can take longer.
Sources
- Google Search Console Help — Page indexing report
- Google Search Central — Large site owner's guide to managing your crawl budget
Quotes checked against the official pages on 29 October 2026.