Guide

How to fix 'Crawled - currently not indexed' in Google Search Console

'Crawled - currently not indexed' means Google read your page and left it out of search. This guide shows how to find the cause for each page with ChatGPT or Claude and your own Search Console data, what to fix, and when to request indexing.

Last updated

What 'Crawled - currently not indexed' means

Search Console shows this status in the Page indexing report, under "Why pages aren't indexed". Google fetched the page and decided not to add it to the index. A page that is not in the index gets no impressions and no clicks.

It is not a crawl error. Google could read the page. Common reasons are a page that adds little beyond other pages, a near copy of another page on your site, few or no internal links to it, or a new site that Google has not learned to trust yet. Google does not say which reason applies, so you check each one.

'Discovered - currently not indexed' is a different status. There, Google knows the URL but has not fetched it yet. The steps below work for both.

What URL Inspection tells you

URL Inspection is the Search Console check for one page. Use this table to turn what it shows into a fix.

Inspection showsWhat it meansWhat to do
Crawled - currently not indexed, fetch successful, indexing allowedGoogle read the page and chose not to add it, for now.Make the page more useful than similar pages, and link to it from pages that are indexed.
Crawled - currently not indexed, and no referring pagesGoogle reports no pages that link to it. Its list is a sample, so check your own pages too.Add links from related pages and from a hub or category page.
Discovered - currently not indexed, no crawl recordedGoogle knows the URL but put off the crawl, often because it expected the crawl to overload your server.Check server response times and cut low-value URLs, such as endless filter pages. Check that Google reads your sitemap and that internal links point to the page.
Excluded by 'noindex' tagThe page tells Google not to index it.Remove the noindex tag if you want the page in search.
Duplicate, Google chose different canonical than userGoogle indexed a different URL in place of this one.Check the page's own canonical tag and the links to it first. If the two pages really are near copies, merge them or make each one clearly different.
Blocked by robots.txt, or a failed page fetchGoogle could not read the page.Fix the robots.txt rule or the server error first.

Why check it in ChatGPT or Claude

In Search Console you inspect one URL at a time and read each result by hand. An AI assistant can inspect up to 20 URLs in one request, group them by cause and check whether another of your pages already ranks for the same topic.

QuerySail is a hosted Google Search Console MCP server. MCP, the Model Context Protocol, lets an AI app call outside tools when a question needs them. QuerySail gives your assistant five tools, including URL inspection, search performance and sitemaps.

Connect Search Console

  1. Create a QuerySail account. The trial needs no card.
  2. Open Account → Connections, select Connect Search Console and approve read-only access on Google's consent screen.
  3. Add the endpoint below to your AI app as a custom connector, and sign in with your QuerySail account when it asks.
https://mcp.querysail.com/gsc/mcp

The steps for each AI app are in how to connect Search Console to ChatGPT and Claude.

Seven prompts to find and fix the cause

The prompts use the sample site Sample Outdoors. Run them in order in one chat, so each step can use the results of the steps before it. Replace the property and URLs with your own.

1. Find your property

Which Search Console properties can you access?

Tool: list_properties

Note the exact property ID for your site, for example sc-domain:sample-outdoors.example. The next prompts use it.

2. Inspect the pages that are not indexed

For sc-domain:sample-outdoors.example, inspect these URLs. For each one, tell me if it is on Google, its coverage state, when Google last crawled it, the canonical Google chose, and which sitemaps and pages refer to it. https://sample-outdoors.example/guides/tent-footprint https://sample-outdoors.example/guides/stove-fuel-types https://sample-outdoors.example/gear/bivy-sack

Tool: inspect_urls

Copy up to 20 URLs from the Page indexing report in Search Console, under 'Crawled - currently not indexed', or paste your newest pages. Each call takes up to 20 URLs. The answer shows each page's state as Google last saw it. It is not a live test.

3. Sort the pages by cause

Group the inspected pages by coverage state. Within the 'Crawled - currently not indexed' group, flag any page with no referring pages or with a Google canonical that differs from the declared one.

No tool call. Your assistant works with the results it already has.

Your assistant works with the inspection results it already has. Use the table above to match each group to a fix. Noindex, robots.txt and fetch problems have coverage states of their own, so fix those first. 'Crawled - currently not indexed' pages with no flags are the ones Google judged not worth adding yet.

4. Find the pages Google prefers

For the same property, over the last 3 months, which pages get impressions for queries that contain 'tent footprint' or 'stove fuel'? Show clicks, impressions and average position by page.

Tool: get_performance

If another of your pages already ranks for the topic, Google may see the unindexed page as a near copy. Merge the two, or rewrite the weaker one so it answers a different question. If no page of yours gets impressions for the topic, compare your page with the results that rank and add what they cover.

5. Check that Google reads your sitemap

List the sitemaps for sc-domain:sample-outdoors.example. When did Google last read each one, and are there errors or warnings?

Tool: list_sitemaps

A sitemap that Google has not read for weeks, or that has errors, slows down discovery. This matters most for 'Discovered - currently not indexed' pages. The URL counts are listed URLs, not indexed URLs.

6. Fix the page, then request indexing once

Write a short to-do list for each page that is not indexed, based on its cause. Put the pages with the most potential search traffic first.

No tool call. Your assistant works with the results it already has.

Make the change first. Add content, merge a duplicate, add internal links or remove a noindex tag. Then open the page in Search Console's URL Inspection and select Request indexing, once. Repeat requests do not move a page up the queue. QuerySail cannot request indexing for you.

7. Check again in two to four weeks

Inspect the same URLs again. Which ones are on Google now? For the pages that are indexed, how many impressions have they had since they were added?

Tool: inspect_urls, get_performance

Google can take days or weeks to crawl a page again. A page that moves to 'Submitted and indexed' and starts to get impressions is fixed. A page that stays excluded after a real change may need a bigger rewrite, or it may not be worth keeping as a separate page.

Example answer

Made-up example. We invented these results to show the shape of an answer. They do not come from a real site or a QuerySail customer.

Inspection results for three Sample Outdoors pages:

URLOn GoogleCoverage stateLast crawlReferring pages
/guides/tent-footprintNoCrawled - currently not indexed2026-11-02None reported
/guides/stove-fuel-typesNoCrawled - currently not indexed2026-10-29/guides/
/gear/bivy-sackNoDiscovered - currently not indexedNoneNone

The summary your assistant writes from those results could read like this:

Both guides allow indexing, and neither is blocked by robots.txt. Google reports no referring pages for /guides/tent-footprint, only the sitemap. Link to it from /guides/ and from the tent pages. /guides/stove-fuel-types is linked, but /blog/camping-stove already gets impressions for "stove fuel" queries at an average position of 9.4, so the two pages may overlap. Merge them, or focus the guide on fuel types only. Google has not crawled /gear/bivy-sack yet. The sitemap was last read on November 14 with no errors, so add internal links to it and wait. Request indexing for the first two pages after you change them.

The data shows each page's state, not Google's reasons. Treat the overlap between the two stove pages as a likely cause to test, not a fact.

Limits to know

When to leave a page out of the index

Not every page needs to be in Google. Tag pages, filtered lists, thin archive pages and old duplicates often show this status, and that is fine. If a page has no search demand and no unique content, add a noindex tag, merge it into a stronger page or remove it from your sitemap. Then spend the effort on pages that people search for.

Try it on your own site

QuerySail costs $8 a month after a 7-day free trial with no card. If two of your pages compete for the same searches, read how to find keyword cannibalization. If an indexed page is losing clicks, read how to find content decay.

Questions, answered

Something else? See support.

What does 'Crawled - currently not indexed' mean?

Google fetched the page but did not add it to its index, so the page cannot show in search results. Google's own help says the page may or may not be indexed in the future. It is a decision about the page, not a technical error.

What is the difference between crawled and discovered but not indexed?

'Discovered - currently not indexed' means Google knows the URL but has not fetched it yet. 'Crawled - currently not indexed' means Google fetched it and chose not to index it. Google's help says the first usually happens when a crawl was expected to overload the site. The second is usually about the page itself.

Will Google index the page on its own?

Sometimes. Google crawls pages again and can change its decision, especially for new sites. If the page stays excluded for weeks, change the page or its internal links instead of waiting.

Should I request indexing?

Google's help for this status says there is no need to resubmit the URL. If you made a real change to the page, request indexing once so Google sees the new version sooner. Repeat requests do not move a page up Google's queue.

Can ChatGPT or Claude check which pages are not indexed?

Yes, when the assistant can read your Search Console data. With QuerySail connected, your assistant runs URL Inspection on up to 20 URLs per call and reports each page's coverage state, last crawl, canonical, and the sitemaps and pages that refer to it.

Can QuerySail list every page in the Page indexing report?

No. Google's API inspects one URL at a time and does not return the full Page indexing report. Copy URLs from the report in Search Console, or use your sitemap, and give them to your assistant.

Can QuerySail request indexing for me?

No. QuerySail reads your Search Console data but cannot change it. Request indexing in Search Console's URL Inspection tool after you fix the page.

Does this cost extra?

No. URL inspection is part of the $8 per month plan, which also covers Google Analytics. The 7-day free trial needs no card.