"Crawled – currently not indexed": what it means and what actually fixes it

"Crawled – currently not indexed" means Google fetched the page, read it, and chose not to keep it. Nothing is broken. No setting is blocking it. It is a judgement about the page, and the fix is almost always to change the page, not to ask Google again.

That is less comfortable than a checkbox, but it is also more useful, because it tells you exactly where to look.

What Google actually says

Google's own description, in its Page indexing report help, is short: the page was crawled but not indexed, it "may or may not be indexed in the future", and there is no need to resubmit it for crawling.

Three things follow from that wording.

• It is not an error. The page loaded, Google could read it, and nothing told it to stay away.
• It is not permanent. Google may come back and index it later, particularly if the page changes.
• Resubmitting is not the fix. Google already has the page. Asking it to fetch the same thing again usually gets the same answer.

How it differs from the statuses next to it

It sits in the same report as several other reasons, and they are easy to mix up.

• "Discovered – currently not indexed" means Google knows the address but has not fetched it yet. Google's help page says this is typically because crawling it then was expected to overload the site, so the crawl was rescheduled. Different stage, different problem.
• "Excluded by noindex tag" and "Blocked by robots.txt" are your own instructions being followed. Those are settings, and settings can be switched off.
• "Crawled – currently not indexed" is the only one of these where Google made the call itself.

So before anything else, confirm you are looking at the right one. Open Search Console, go to the Pages report, click the reason, and look at the example addresses Google lists under it.

First, rule out the boring explanations

Take one of the listed addresses and put it into the URL Inspection box at the top of Search Console, then run the live test. You are checking that the page Google sees today is the page you think it is.

• Does it load properly, without an error?
• Has Google picked a different address as the canonical? If so, it is treating this page as a copy of that one. Canonical tags explained →
• Is it a page you actually want in Google? Search results pages, filtered product lists, tag archives, thank-you pages and print versions often land in this bucket, and that is fine.

Our free indexability checker does the same outside view without needing Search Console. If it finds no block, you are dealing with a quality decision, which is the rest of this article.

What actually fixes it

Google does not tell you why a particular page was left out, so nobody can tell you for certain either. What you can do is look at the page the way a stranger would and ask whether it deserves a place.

The page is thin

A heading, a photo and a sentence or two. Product pages with no description, location pages with only the town name changed, blog posts written to hit a word count. The fix is to add what a customer actually needs to know: prices, what is included, who it is for, how it works, what happens next.

What counts as thin, and what to do about it →

The page duplicates another one

If two pages on your site say substantially the same thing, Google has little reason to index both. Common on sites with a page per town or per small variation of a service. You have three honest options: make each page genuinely different, merge them into one stronger page and redirect the old address to it, or point a canonical tag from the copy to the original.

Nothing links to it

A page that only appears in your sitemap, with no links from your own pages, looks unimportant. Link to it from somewhere relevant on your site, such as your services page, a related post or your navigation.

There are a lot of low-value pages around it

If your site has hundreds of near-empty tag pages or automatically generated variations, they compete with the pages you care about. Removing or noindexing pages that serve no visitor is often more useful than adding more.

After you have changed the page

Once the page is genuinely better, it is reasonable to ask Google to look again. In URL Inspection, run the live test and, if it shows no errors, click Request indexing.

Be realistic about what that does. Google's URL Inspection help says there is a daily limit on requests and that submitting one does not guarantee the page will be indexed. It puts the page in a queue. It does not overrule the judgement. Save it for pages that matter, and keep your sitemap current for the rest.

If you change the page title while you are at it, the free search preview tool shows how the new title and description are likely to look in results.

When to leave it alone

Not every page in this bucket is a problem. If the list is mostly addresses you would not want a customer to land on from Google, Google has made a sensible decision for you. Spend your time on the pages that would earn you a call or a sale if someone found them.

And if it is your homepage, or most of your site, the question is wider than one page. Why a website is not showing up on Google works through the site-wide causes in order.

The short version

1. Confirm the status in the Pages report, and that it is not "Discovered" or a noindex.
2. Live-test one example in URL Inspection and check the canonical Google chose.
3. Decide whether the page deserves to be in Google at all.
4. If it does, make it more substantial, merge it with its near-twin, or link to it properly.
5. Then request indexing once, and give it time.

Checked against Google's own Search Console help pages on 13 October 2026. Menus move; if yours looks different, Google's guides to the Page indexing report and the URL Inspection tool have the current wording.

If you want to rule out the technical causes across your whole site at once, run a free audit below. It checks noindex tags, robots.txt, canonicals and thin pages, and tells you which apply.