What does Crawled – currently not indexed mean?
Crawled – currently not indexed means Googlebot fetched the page but Google decided not to add it to its index, at least for now. It is not an error or a penalty: Google says the page may or may not be indexed later and there is no need to resubmit it. If the page matters, the fix is to make it clearly worth indexing (distinct content, a clear canonical, links from your strong pages), not to keep requesting indexing. Its sibling, Discovered – currently not indexed, means Google knows the URL but hasn’t crawled it yet.
If you are asking “why are my pages not indexed?”, the answer for each URL is in the reason column of Search Console’s Page indexing report, and for most rows the reason is by design. Google’s Page indexing report documentation says you should expect only canonical pages to be indexed, that most sites have some unindexed pages, and that all of your important pages should be indexed. That last part is the job.
We make GSC MCP Server, so the bulk-checking section uses its tool names; every other step works in the free Search Console interface. Sources were checked on 30 October 2026.
How to read the Page indexing report
Open Indexing → Pages. The chart splits known URLs into indexed and not indexed, and the Why pages aren’t indexed table lists a reason for every group of excluded URLs. Four details change how you read it:
- The Source column. Each reason is attributed to “Website” or “Google systems”, and Google says you can generally fix only issues whose source is Website. The rest are Google’s decisions, which you can influence but not switch off.
- The sitemap filter. The menu above the chart switches between All known pages, All submitted pages, Unsubmitted pages only and a single sitemap. Start with All submitted pages: those are the URLs you told Google you want indexed, so their problems matter most.
- Examples are a sample. Click a reason to see example URLs and its history. The list is capped at 1,000 rows and isn’t guaranteed to show every affected URL. The export button downloads the chart and table data.
- The data lags. Counts update when Google recrawls affected pages, whether or not you asked for validation. According to Search Engine Roundtable, the report stayed on 11 June data until 3 July 2026; Google’s data anomalies page doesn’t list it. The same site reported in September that John Mueller said Google doesn’t back-fill indexing data. A gap or flat line in June 2026 is a reporting artifact, not your site.
Google’s own advice has shifted towards reading the report for patterns. In the July 2026 Search Off the Record episode on the indexing report, Martin Splitt and John Mueller describe it as a tool for spotting unexpected changes and trends, not an inventory to clear. A steep rise in Page with redirect after a migration is the report confirming your change; the same rise on a quiet week is worth investigating.
Every Page indexing status explained
The reasons you will see most often, and what, if anything, to do about each:
| Status | What it means | Usually | What to do |
|---|---|---|---|
| Crawled – currently not indexed | Fetched, then left out of the index for now | Worth a look if the page matters | Improve, merge or remove the page; add internal links from strong pages |
| Discovered – currently not indexed | Known but not yet crawled; Google postponed the crawl, often to avoid overloading the site | Normal for new URLs; act if it persists or grows | Internal links, accurate sitemaps, faster server, fewer duplicate URLs |
| Duplicate without user-selected canonical | A duplicate with no declared canonical; Google indexed another URL instead | Normal | Declare a canonical if Google picked the wrong one; make the page distinct if it isn’t a duplicate |
| Duplicate, Google chose different canonical than user | Your canonical tag was overruled | Check which URL Google chose | Align redirects, canonicals, internal links and sitemaps on one URL |
| Alternate page with proper canonical tag | Correctly points to a canonical that is indexed | Normal | Nothing |
| Excluded by ‘noindex’ tag | A noindex rule in the robots meta tag or the X-Robots-Tag header | Normal if intended | Remove the rule if the page should rank |
| Blocked by robots.txt | Google may not crawl the URL | Normal if intended | Remove the rule if the page should rank; to keep a page out, allow crawling and use noindex |
| Soft 404 | Returns 200 but looks like an error, an empty page or a “no results” page | Needs action | Return 404 or 410 for gone pages, redirect moved ones, add real content to real ones |
| Page with redirect | The URL redirects; the target may be indexed | Normal | Point internal links and sitemaps at the final URL |
| Not found (404) | The URL returned 404 | Normal for removed pages | Fix only 404s you link to or list in a sitemap; 301 pages that moved |
| Server error (5xx) | The server returned a 500-level error when crawled | Act if it is sustained or growing | Check Crawl Stats host status, server logs, CDN and firewall rules |
Rarer reasons include Redirect error (a loop, a bad URL or a chain longer than the 10 hops Google follows), 401, 403 and other 4xx errors. Indexed, though blocked by robots.txt, and Page indexed without content are warnings about URLs that are indexed. The Help Center titles a few reasons differently, such as “URL marked ‘noindex’”, but they are the same statuses.
Which statuses are normal and which need action
A status is only a problem when it applies to a URL you want in Google. Ask three questions of each reason:
- Do I want this exact URL in search results? Filter URLs, tag archives, internal search pages, old campaign pages and parameter variants usually don’t belong there.
- Is it the canonical version? If another URL with the same content is indexed, searchers can still find it.
- Is it a pattern? A reason that is growing, or that clusters on one template such as product pages, deserves attention. A flat line of the same small count usually doesn’t.
By that test, alternates, redirects, intended noindex and robots.txt rules, and 404s for removed content are normal. Soft 404s, sustained 5xx errors, unexpected noindex or robots.txt rules, and important pages stuck in Crawled or Discovered – currently not indexed need action.
A diagnosis order for pages Google isn’t indexing
Work through the cheap checks first and stop at the first one that explains the status.
- Confirm the page matters. Is it in your sitemap, in your navigation, or earning money?
- Look for the pattern. Export the examples and group them by path. “All /tag/ pages” and “30 of 400 blog posts” are different problems.
- Inspect two or three examples. Paste each into the search bar at the top of Search Console to open the URL Inspection tool, then read Last crawl, Crawl allowed?, Page fetch, Indexing allowed?, and the user-declared and Google-selected canonicals.
- Rule out blockers. robots.txt rules, a stray noindex, a non-200 status, a login wall, or a CDN bot check that Googlebot sees and you don’t.
- Check the canonical. If Google chose another URL, this is a duplication question, not an indexing one.
- Check what Google renders. Run Test live URL and view the screenshot and HTML. If the main content is missing, the problem is rendering, not quality.
- Judge the value. Is the page substantially different from your other pages and from what already ranks?
- Check discovery. Is it linked from pages Google crawls often, and listed in a sitemap with an accurate
lastmod? - Check crawl capacity on large sites, in the Crawl Stats report.
The live test can’t predict which URL Google will treat as canonical; that only shows in the indexed result. Developers can run these checks next to the code with our guide to technical SEO in Cursor and VS Code.
How to fix Crawled – currently not indexed
Google crawled the page, so access is rarely the issue. The question is why it didn’t seem worth indexing. The usual answers:
Near-duplicate or thin templates
Location pages that differ only by city name, product variants with identical descriptions, tag pages with two posts, and paginated archives often land here. Either make each page substantially different, or consolidate: merge the useful parts into one URL and 301 the rest. If two of your pages chase the same queries, the keyword cannibalisation guide helps you choose which one survives.
Pages that add nothing new
Mueller’s description of generic content in that podcast was blunt: “Anyone could have written this. This tells me nothing.” Original data, first-hand experience and a clear answer near the top give Google a reason to index a page. Rewording what already ranks does not.
Site-wide quality doubts
Asked whether these statuses are often a quality sign, Mueller said only sometimes. But when Google has strong concerns about a site, it crawls and indexes less of it, so thousands of URLs in these two statuses with no technical cause point to the whole site. He added that content buried under ads, interstitials or filler counts against a page, however good the text.
Content Google can’t see
If the main content loads only after client-side JavaScript, sits behind a consent wall, or appears after a bot check, Google may have indexed a near-empty shell and judged it accordingly. The live test screenshot shows what Google saw.
Weak internal linking
A page linked only from a sitemap or a deep archive looks unimportant. Link to it from relevant pages that already earn traffic. Our internal linking guide shows how to find the best source pages in Search Console.
For pages you don’t need in Google, the honest fix is noindex or removal. If older pages are fading rather than never indexed, the content decay audit is the better workflow.
How to fix Discovered – currently not indexed
Here Google hasn’t crawled the URL yet, so the last crawl date is empty. Google’s explanation is that it wanted to crawl but expected to overload the site, so it rescheduled. The fix depends on site size.
Small and new sites
Google says it can take a week or so to start crawling and indexing a new site. After that, a lingering Discovered status on a small site is rarely about server capacity: the URLs look unimportant (orphaned, or reachable only from a sitemap) or Google doubts the site as a whole. Link to them from your home page or hub pages, and keep the sitemap to canonical URLs you want indexed.
Large sites
Google’s crawl budget guide is written for sites with about a million unique pages, or 10,000 that change daily, and for sites where a large share of URLs are Discovered – currently not indexed. It describes two levers:
- Crawl capacity. Google crawls more when response times stay stable or improve, and slows down when it sees 5xx or 429 responses. Check Settings → Crawl stats (root-level properties only) for host status over 90 days and the share of bad responses. “Hostload exceeded” in URL Inspection means your site is at maximum capacity for Google’s crawling.
- Crawl demand. Faceted navigation, sort and session parameters, and soft 404 pages inflate the URL inventory Google spends its crawl on. Cut them down and important URLs get crawled sooner; the ecommerce Search Console guide covers faceted navigation in more detail.
Google ignores priority and changefreq in sitemaps, but uses lastmod when it is consistently accurate, so update it only for meaningful changes.
Run list_sitemaps for example.com on Google and Bing. For each sitemap, show when it was last submitted and last downloaded, its errors and warnings, and how many URLs it lists. Flag any sitemap Google hasn’t downloaded in the last 14 days, and any sitemap index whose child sitemaps report errors.
Neither Google nor Bing reports how many sitemap URLs are indexed, so this tells you whether sitemaps are being read, not whether their pages are indexed. For that, use the report’s sitemap filter or inspect the URLs.
Fixing duplicate and canonical statuses
Alternate page with proper canonical tag is a success message. Duplicate without user-selected canonical is fine when Google picked the URL you would have picked. Duplicate, Google chose different canonical than user is the one to check.
Google’s canonicalisation documentation ranks the signals: redirects are strong, rel="canonical" is strong, and sitemap inclusion is weak. Google overrules your tag when other signals disagree, so make them agree: link internally to the canonical, list only canonical URLs in sitemaps, keep trailing slashes and protocol consistent, and don’t use robots.txt or noindex to pick a canonical.
Two cases from the podcast are worth knowing. Google choosing another URL on your own site, such as the non-www version everyone links to, happens all the time and the content stays findable. But if a CDN or host serves an “Are you a bot?” page with a 200 status, Google may index that page and even pick another site’s identical page as your canonical. A Google-selected canonical on another domain is the clue. For code-level causes, see the canonical mismatches section of our developer guide.
Check hundreds of URLs with the URL Inspection API
The URL Inspection API returns the same indexed-version data as the URL Inspection tool, and Google’s usage limits allow 2,000 inspections per property per day and 600 per minute. It can’t run a live test or request indexing. GSC MCP Server exposes it as inspect_url, so Claude, ChatGPT or Cursor can run the inspections and sort the results. To script it yourself, our Search Console API guide covers the raw calls.
The workflow
- Collect URLs. Export a reason’s examples from the Page indexing report (up to 1,000), paste URLs from your sitemap file, or pull top pages with
get_search_pages. - Skip URLs that are clearly indexed. A URL that earned impressions recently was in the index, so spend inspections on the rest.
- Inspect in batches.
multicallruns up to 10inspect_urlcalls in one request. - Group the results by template and coverage state to find the pattern.
Here are 120 URLs from our product sitemap. First, use query_search_analytics with dimension page for the last 28 days (paging with startRow if needed) and drop every URL that has impressions. Then inspect the remaining URLs with inspect_url, 10 at a time with multicall. Give me a table of URL, verdict, coverage state, last crawl, page fetch state, user canonical and Google canonical, grouped by coverage state.
What each field tells you
| Field | What it tells you |
|---|---|
verdict | PASS if the URL is indexed; otherwise NEUTRAL or FAIL |
coverageState | The same wording as the Page indexing report, such as “Crawled – currently not indexed” |
lastCrawlTime | Absent if Google never crawled the URL successfully; recheck it after a fix |
pageFetchState | Successful, soft 404, not found, server error, blocked |
indexingState and robotsTxtState | Whether a noindex rule (meta tag or header) or robots.txt blocks the page |
userCanonical and googleCanonical | Your declared canonical and the one Google chose |
sitemap and referringUrls | How Google found the URL; neither present suggests an orphan page |
Take the inspection results above and group the URLs by first path segment. For each group, show how many are indexed, crawled but not indexed, discovered but not indexed, or duplicates. Then list every URL whose Google canonical differs from its user canonical, and say whether the Google canonical is on another host.
Budget your inspections
Every URL is one inspection against Google’s daily quota and one tool call against your plan, even inside multicall, so 300 URLs use 300 calls. Our Free plan’s 30 calls a month covers a small sample; Pro allows 10,000 and Agency 50,000 (see pricing). For whole-site coverage, rely on the report’s counts and inspect representative URLs per template. The server is read-only: requesting indexing, submitting sitemaps and starting validation happen in Search Console itself.
Validate fix: how it works and how long it takes
Once you have fixed every URL under a reason, open that reason and click Validate fix. Google then recrawls the affected URLs and tracks them. According to the Page indexing report help page:
- Timing: validation typically takes up to about two weeks, sometimes much longer. Don’t click the button again while it runs.
- States: Not started, Started, Looking good, Passed, Failed or N/A. Individual URLs show Pending, Passed, Failed or Other.
- Failure: validation fails if a certain threshold of pages still has the issue. Use See details to find them, fix them, then click Start new validation.
- Speed: Google suggests validating while the report is filtered to a sitemap that contains only your key pages, which can complete faster.
Validation suits problems you can fix: a noindex removed, a robots.txt rule lifted, a template returning 404s or 5xx. For Crawled and Discovered – currently not indexed, Splitt and Mueller agreed in the podcast that the fix button sets the wrong expectation, because there is no technical switch to flip. Improve the pages and let the recrawl show the result. For a few important URLs you have changed, use Request indexing in URL Inspection; Google says indexing then typically takes a day or so but can take much longer.
On 14 October we fixed the noindex rule on these 40 category pages. Inspect each one with inspect_url and show which now have a last crawl after 14 October, which are indexed, and which still report a noindex rule or another coverage state.
When it’s fine to ignore Page indexing issues
Leave these alone:
- URLs you deliberately noindexed or blocked.
- Duplicates and alternates whose canonical is indexed, including Google choosing a different URL on your own site.
- Page with redirect after a planned redirect or migration; the site migration monitoring guide covers what normal looks like after a move.
- 404s for removed content that nothing links to.
- Short 5xx blips. Mueller said Google tends to ride out an error that lasts up to about a day and retries; systems react to longer ones.
- Crawled – currently not indexed on low-value URLs such as tag archives, internal search results and thin pagination.
Act quickly on these:
- Any important page (in your sitemap, in navigation, earning revenue) that isn’t indexed.
- A sudden jump in any reason that you didn’t cause, especially 403, 404 or 5xx, which often means bot protection or a deploy is blocking Googlebot.
- Soft 404s on pages that should have content.
- A Google-selected canonical on another domain.
- A sitewide rise in Crawled or Discovered – currently not indexed with no technical cause.
If indexing changes line up with lost traffic, switch to the organic traffic drop diagnosis. Otherwise, a monthly look at the trend lines plus a short batch of inspections on new templates is enough for most sites. To run those from your assistant, follow the setup guide for Claude, ChatGPT and Cursor.
Frequently asked questions
How long does it take Google to index a page that says Crawled – currently not indexed?
There is no fixed time. Google says the page may or may not be indexed in the future, and that you don’t need to resubmit it. If you improve the page substantially, nothing changes until Google recrawls it, and Google notes that a revisit can take months for some pages. Check the last crawl date with URL Inspection before you judge whether a change worked.
Should I click Request indexing for pages that are crawled but not indexed?
Only after a real change, and only for a handful of important URLs. Requesting indexing on an unchanged page asks Google to look again at something it has already decided not to index. There is a daily limit on requests, a request does not guarantee indexing, and you can’t request indexing for a page that fails the live test.
Is Crawled – currently not indexed a penalty?
No. Penalties appear in the Manual actions report, not the Page indexing report. Crawled – currently not indexed is an ordinary indexing decision. Google’s John Mueller has said it is sometimes, not always, a sign of a quality issue; it matters most when many important pages share the status with no technical cause.
What is the difference between Discovered and Crawled – currently not indexed?
Discovered – currently not indexed means Google knows the URL exists but has not crawled it yet, so there is no last crawl date. Crawled – currently not indexed means Google fetched the page and chose not to index it. The first points to discovery and crawl capacity; the second to whether the page is worth indexing.
How long does Validate fix take in Search Console?
Google says validation typically takes up to about two weeks but can take much longer. Don’t click the button again while it runs. If it fails, open See details to find the URLs that still have the issue, fix them, and click Start new validation.
Will adding the URL to my sitemap fix Crawled – currently not indexed?
No. Google has already found and crawled the page and chose not to index it, so listing it in a sitemap tells Google nothing new. Keep important URLs in your sitemap, but the fix is making the page worth indexing: distinct content, a clear canonical and links from your strong pages.