Page indexing report · Search Console
Crawled – currently not indexed
Google fetched the page, read it, and decided not to add it to the index. It isn’t an error or a penalty, and Google says there’s no need to resubmit the URL.1 Here’s how to tell whether it matters, find the real cause, and change the outcome.
Check the URL first
The checker rules out the technical causes you can see from outside Search Console. It can’t see Google’s judgement of the page. Nothing outside Google can.
In 30 seconds
- Google crawled the page and chose not to index it. Google says it “may or may not be indexed in the future”.1
- The usual reasons: the page duplicates another, adds little that’s new, or Google is cautious about the site as a whole.5
- noindex, robots.txt and crawl budget don’t cause this status. Each has its own row in the report.
- Request indexing doesn’t override the decision. Change the page, then wait.
What the status means
Indexing is a selection, not a formality. Google’s own guide to how Search works says indexing isn’t guaranteed and that not every page Google processes will be indexed.2 The report itself tells site owners not to expect every URL to be indexed.1
The word that matters is crawled. Google reached the page, so your server, robots.txt and links did their job. The decision came after Google read what was on it.
Where it happens
Select a stage to see what Google does there and which report statuses it can produce.
Discover
Google learns that a URL exists, mostly from links on pages it already knows and from XML sitemaps.
What goes wrong: Nothing links to the page and it isn’t in a sitemap, so Google never hears about it.
Report statuses at this stage
- URL is unknown to Google (shown in URL Inspection, not in the report)
Crawl
Googlebot checks robots.txt, then requests the URL. It spaces requests out so it doesn’t overload the server.
What goes wrong: The URL is blocked, returns an error, or the server is slow, so Google backs off and crawls less.
Report statuses at this stage
Render
Google runs the page’s JavaScript in a recent version of Chrome to see the finished page.
What goes wrong: Content only appears after a click or scroll, or the scripts fail, so the rendered page is nearly empty.
Report statuses at this stage
- No status of its own. Problems show up at the next stage as thin pages or soft 404s.
Index
Google decides which version of the page to keep and whether it is worth storing at all.
- Group duplicates. Pages with the same or very similar content go into one group.
- Pick a canonical. One URL represents each group. Canonical tags, redirects and sitemaps are hints, not commands.
- Select for the index. Google decides whether the canonical page is worth keeping. Google says this largely depends on quality.
What goes wrong: The page duplicates another, is marked noindex, or Google decides it adds too little to keep.
Report statuses at this stage
Serve
Indexed pages can appear in search results. Being indexed is not the same as ranking; an indexed page can still get no clicks.
What goes wrong: The page is indexed but doesn’t match what people search for, or other pages answer it better.
Report statuses at this stage
Before the final step, Google groups duplicate pages and picks one URL from each group as the canonical.4 Then comes index selection, which Google’s Gary Illyes describes as depending largely on the page’s quality.7 A page in this status lost at one of those two steps.
Is it a problem?
Usually fine
- RSS feeds, JSON and other non-page URLs
- Paginated, tag and archive pages
- Parameter versions of pages that are indexed
- Pages nobody would search for
- A URL the report hasn’t updated yet
Worth fixing
- Pages you want search traffic for: products, articles, landing pages
- A count that keeps rising over weeks
- A large share of the site in this row
Find the cause
The report doesn’t say why a page was left out. Gary Illyes has said the status covers many different reasons.5 Answer a few questions to narrow it down. Each cause is explained below.
The report is behind
The Page indexing report lags. John Mueller has said URLs listed here can already be indexed, and suggested searching for words from the page to check.8 URL Inspection is the reliable test. A site: search isn’t: it shows only some indexed pages.14
Another page has the same content
Illyes names duplicate elimination first: Google crawls a page, then skips it because a very similar version with stronger signals is already indexed.5 Canonical tags help Google pick the version you want, but Google treats them as a hint, not a rule.4 The fix is to choose one URL and consolidate, or make each page genuinely different.
The page adds too little
There’s no word count or score to hit. The question is whether the page tells searchers something they can’t already find. Discussing generic AI-written pages in 2026, Mueller summed up the reaction they get:
“Anyone could have written this. This tells me nothing.”
John Mueller, Google, Search Off the Record, July 20266
He also said that AI-generated content isn’t bad in itself. The problem is pages that add nothing.
Google is cautious about the whole site
This is the cause most guides miss. Illyes has said the general quality of a site can matter a lot for how many of its pages appear in this report, and that a rising count can mean Google’s view of the site has changed.5 Mueller said in 2026 that when Google’s systems are seriously worried about a site’s quality, they reduce how many of its pages get indexed.6 If a large share of your pages is here, work on the site’s weakest pages, not just the ones in the report.
The page was indexed, then dropped
Indexing isn’t permanent. If the Performance report shows impressions for the page in the past, it made the cut once and lost it later, often because a better page now covers the topic, possibly one of your own.
A bug served the same page on many URLs
Illyes gives this example: a site error that served the exact same page on every URL.5 If many unrelated URLs land in this row at once, load a few of them and check they show the right content.
JavaScript content didn’t render
Less common than many guides suggest. In a study of over 100,000 Googlebot fetches on nextjs.org, every indexable HTML page was fully rendered, with a median delay of 10 seconds.11 Content that only appears after a click or scroll is still a risk, because Google doesn’t interact with the page.12 The checker above flags pages whose HTML is nearly empty before JavaScript runs.
What doesn’t cause it
Many guides list these as causes. For this status, they’re wrong.
| Often blamed | What’s actually true |
|---|---|
| A noindex tag | Pages with noindex are reported as “Excluded by ‘noindex’ tag”, a different row.1 |
| A robots.txt block | A blocked URL can’t be crawled, so it can’t be in a status that starts with “Crawled”. It has its own row.1 |
| Crawl budget | Crawl budget decides whether Google crawls. This page was crawled. Pages waiting to be crawled are “Discovered – currently not indexed”.1 |
| Too many pages (“index bloat”) | Google has said it has no concept of index bloat and doesn’t artificially limit how many pages per site it indexes.13 |
| Low domain authority | Domain authority is a score invented by SEO tool companies. Google doesn’t use it. |
| Too few words | Google has never published a minimum length. A short page that answers something new can be indexed; a long one that repeats others may not be. |
| Not pressing Request indexing enough | Google says requesting the same URL repeatedly won’t get it crawled faster, and a request doesn’t guarantee indexing.3 |
| “site:” doesn’t show it | A site: search only shows some indexed pages. Use URL Inspection to check one URL.14 |
How long it takes
Google gives ranges, not promises:
- Days to weeksfor Google to crawl a page after you change it or request indexing.3
- Up to about 2 weeksfor Search Console to validate a fix, sometimes much longer.1
- 3 to 4 monthsfor Google to recognise a site-wide quality change, by John Mueller’s 2021 estimate.9
Independent data shows a long tail. Hover or tab through the bars for details.
Show as a table
| Time since tracking started | Share indexed |
|---|---|
| 7 days | 14% |
| 30 days | 64.9% |
| 90 days | 76.8% |
| 6 months | 93.2% |
Source: IndexCheckr, about 16 million pages tracked 2021–2025.10 Pages were tracked from when users added them, not from publication, and the users of an index-checking tool likely have more indexing trouble than most sites. 61.9% of tracked pages were never indexed.
Crawled vs discovered – currently not indexed
| Crawled – currently not indexed | Discovered – currently not indexed | |
|---|---|---|
| Has Google fetched it? | Yes | No, not yet |
| Google’s explanation | Crawled but not indexed; may be indexed later | Usually rescheduled because crawling was expected to overload the site1 |
| Usual cause | Duplication, low value, site-wide quality | Server capacity, crawl priority, quality |
| Where to look | The page’s content and the site as a whole | Crawl Stats, server speed, internal links |
Fixing it across many pages
- Open the row in the Page indexing report and export the URLs.
- Switch the report’s filter from “All known pages” to “All submitted pages”. That shows only URLs from your sitemaps: the ones you asked Google to index.
- Group the URLs by pattern: folder, template, parameter. One cause usually explains a whole group.
- For each group, decide: improve, merge and redirect, or leave out on purpose.
- After real changes, click Validate fix in the report. Request indexing for a few key URLs at most.
Questions
Is “Crawled – currently not indexed” bad?
Not by itself. Google says not to expect every URL to be indexed, and feeds, archives and parameter URLs often land here. It matters when pages you want traffic for are in the row, or when the count keeps rising.
How long does it take to get out of this status?
Google says crawling a changed page takes a few days to a few weeks, and validating a fix typically up to about two weeks. Google’s John Mueller has estimated three to four months for Google to recognise site-wide quality changes. Some pages are never indexed.
Should I click Request indexing?
Only once, after you have changed something meaningful. Google says repeated requests won’t get a URL crawled faster and that a request doesn’t guarantee indexing.
Why did validation fail?
Validation fails when some of the URLs in the row are still not indexed after Google rechecks them. If the cause is quality or duplication, Google can recrawl the page and make the same decision again. Change the pages first, then validate.
Which is worse, crawled or discovered – currently not indexed?
Neither is worse in general. Discovered means Google hasn’t fetched the page yet, often because of server capacity or crawl priority. Crawled means Google read the page and chose not to keep it, so the fix is usually about the content, not the server.
Will adding more words fix it?
Only if the words add something new. Google has never published a word-count threshold. Index selection depends on whether the page adds value, so padding a page rarely changes the decision.
Sources
- Google, “Page indexing report”, Search Console Help
- Google, “In-depth guide to how Google Search works”, Search Central, updated December 2025
- Google, “Ask Google to recrawl your URLs”, Search Central, updated December 2025
- Google, “What is URL canonicalization”, Search Central, updated August 2026
- Gary Illyes (Google) interviewed at SERP Conf, May 2024, reported by Search Engine Journal, July 2024
- John Mueller and Martin Splitt (Google), Search Off the Record, July 2026, reported by Search Engine Roundtable
- Gary Illyes (Google), “How Search Works” video series, reported by Search Engine Journal, April 2024
- John Mueller (Google), Search Central office hours, reported by Search Engine Journal, July 2021
- John Mueller (Google), Search Central office hours, reported by Search Engine Journal, April 2021
- IndexCheckr, “Google Indexing Study”, February 2025 (about 16 million pages tracked 2021–2025)
- Vercel and MERJ, “How Google handles JavaScript throughout the indexing process”, July 2024
- Google, “Understand the JavaScript SEO basics”, Search Central, updated March 2026
- John Mueller (Google), Search Off the Record, June 2023, reported by Search Engine Journal
- Gary Illyes (Google), Search Off the Record, June 2023, reported by Search Engine Journal