How to fix ‘Crawled - currently not indexed’

‘Crawled - currently not indexed’ means Google fetched a URL but didn’t add it to the index at the time shown in Google Search Console (GSC).

You can often fix the cause, but there isn’t one repair that works for every page, so first check whether the warning is still current. Then decide whether the page should appear in Google at all and, if it should, work through the checks below in order.

The main rule is simple:

Find out what’s wrong before you change the page.

What does ‘Crawled - currently not indexed’ mean?

Think of Google as a large library. Crawling is like opening a book to see what’s inside, while indexing is like placing that book on a shelf so people can find it. Google can open a page without choosing to put it on the shelf.

The Page indexing report groups pages by the reason they weren’t indexed, and this message means Google visited the page but didn’t add it to its searchable collection at that time.

The message doesn’t tell you why, because the page may be new, very similar to another page, blocked by a setting or hard for Google to read. Google may also believe the page adds little value on its own.

Not every excluded page is a problem. A checkout page, filtered list or duplicate version may be better left out of search. Your first job is to decide whether the page belongs there.

Check two things before you edit the page

1. Is the page still missing from Google?

The main Page indexing report shows groups of pages, so it may not reflect a recent change straight away. URL Inspection is the Search Console tool that lets you check one address at a time.

Open URL Inspection and enter an important example URL. Record:

• Whether Google now says the page is indexed.
• The date Google last visited it.
• The version Google saw on that visit.
• Whether Google was allowed to index it.
• Which URL Google chose as the main version.

A live test can show whether Google can open the current page, although Google’s URL Inspection guidance explains that a successful test doesn’t promise indexing.

If the page is now indexed, the grouped report may simply be behind, so record that delay and don’t make a change. If the page is still missing, move to the next question.

2. Should this page appear as its own search result?

Some pages have a clear job in search, such as a service page for ‘emergency plumber in Bristol’ that answers a distinct need. A sorted copy of the same page may not.

Type of page	Likely outcome
A useful service, product or guide with its own purpose	It will usually need its own place in Google.
A filtered, sorted or tracking URL	It will usually point back to a main page or stay out of the index.
A near-copy created by a website template or feed	It will usually be combined with a main version.
A page only for signed-in users	It will usually stay out of search on purpose.
A page with no clear reason to exist	Review the page before trying to force it into Google.

This step can save a great deal of wasted work because there’s no value in adding more text to a page that shouldn’t be a search result.

Use this five-step check

Work from facts you can see towards the parts that need judgement, then stop when you find a clear cause.

Step 1: confirm the current state

Choose a few pages that share the warning and, if many are affected, pick examples from each type, such as products, services, locations or blog posts.

Check each page in URL Inspection and note whether it’s indexed now, when Google last visited it and whether the report describes an old version. This tells you whether you have a current problem or an old report.

One example may mislead you, so if 2,000 product pages have the same warning, choose a small but varied sample. Ten well-chosen pages can reveal a pattern more clearly than one large export.

Step 2: decide whether the page belongs in Google

Ask what search need the page serves and whether someone would find a useful answer that they wouldn’t get from another page on the site.

Next, check the site’s own instructions:

• Does the page load at the expected address?
• Does it contain a noindex tag? (It’s an instruction that asks search engines not to show the page.)
• What’s the canonical URL? (A canonical is the address the site names as the main version when several pages are alike.)
• Is the page listed in the XML sitemap? (It’s the file that gives search engines a list of important URLs.)
• Do useful pages on the site link to it?

A canonical is a clue, not a command, so Google may still choose another version if it thinks that page is a better main copy. Google’s guide to how Search works also makes clear that indexing isn’t guaranteed.

If your links, sitemap and canonical point to different addresses, make them agree before you ask Google to check the page again.

Step 3: check what Google could see

A page can look fine to you but still reach Google with missing content when it relies on scripts that fail or load too late.

Compare:

• The page shown in a normal browser.
• The screenshot and HTML shown in URL Inspection.
• The page title, main copy and canonical URL in both versions.
• Any failed files or scripts that the page needs to show its main content.

HTML is the code that holds the content and structure of a page, while a rendered page is the finished version after the browser has run that code. If the normal page contains a product description but Google’s version is blank, you have found a real technical problem.

The five-gate rendering method explains the deeper checks if the two versions don’t match, and a developer may need to help when scripts or server settings are involved.

If Google can see the full page, move on because the cause is more likely to involve duplicate pages, weak page purpose or mixed signals.

Step 4: compare the page with similar pages

The answer often becomes clearer when you put the excluded pages beside similar pages that Google has indexed.

Ask:

• Do the excluded pages contain less useful or unique information?
• Do several pages answer the same search question?
• Are important pages linked from service, product or topic hubs?
• Did the warning appear after a site template or navigation change?
• Would the page still help someone who landed on it from Google?

Don’t turn this into a word-count test, because a short service page can be useful if it gives a clear offer, location, price or next step. A long page can still be weak if most of it repeats text from elsewhere.

Write one clear explanation for the pattern, such as: ‘Most excluded location pages repeat the same service copy and have no links from the main location hub.’ That statement gives you something useful to test.

Step 5: change one likely cause and review it

Make the smallest change that fits the evidence, because the right action depends on what you found.

What you find	What to do
URL Inspection says the page is already indexed	Record the reporting delay and make no page change.
The page shouldn’t be a separate search result	Merge it, redirect it or keep it out of the index on purpose.
Links and canonical tags point to different pages	Choose the main page and make those signals agree.
Google’s version is missing important content	Fix the first server, script or page-loading problem.
Several pages do the same job	Improve the useful page and merge or remove the weaker copies.
The page is useful, different and recently updated	Request indexing once, then give Google time to return.

Google says a new crawl can take a few days or a few weeks, and its guidance also says that requesting another crawl doesn’t guarantee indexing. Sending the same unchanged page again won’t speed things up.

Record what you changed and when, then check the same small sample after Google returns. If you change five things at once, you won’t know which one helped.

Use the pattern to choose your next check

What you notice	What it may mean
Only very new pages are affected	Google may not have processed the latest version yet.
Most pages from one template are affected	The shared design, content or page settings may be the cause.
Filter and tracking URLs fill the report	These versions may not need their own place in search.
Pages look complete to you but blank to Google	A script or other page resource may be failing.
Similar pages move in and out of the index	Google may not see enough difference between them.
The warning began after a site move	Check redirects, links and main-page signals from the move.

If the problem began after a site move, work through the site migration checks first because the warning may be a result of an earlier redirect or linking problem.

A checklist you can use for each page

Work from top to bottom and keep a note of what you saw beside each answer.

Crawled but not indexed: page check

I checked whether the page is indexed now and noted the last crawl date. I decided whether this page should be its own search result. The URL opens the correct page without an error or unwanted redirect. The noindex and canonical settings match the result I want. Google's saved or tested version contains the important page content. I compared the page with similar pages that Google has indexed. I wrote down one likely cause before choosing a change. I recorded the change, date and time for the next review.

The checklist can’t promise that Google will index a page, but it’ll keep your checks in a clear order and stop unrelated changes being mixed together.

Avoid these four common mistakes

Don’t request indexing again without a change

The request asks Google to return, but it doesn’t order Google to index the page. If the page and evidence haven’t changed, another request adds nothing new.

Don’t rewrite every excluded page

The content may be part of the problem, but this warning doesn’t prove it, so check the page settings and the version Google saw before paying for a rewrite.

Don’t add noindex just to tidy the report

Use noindex when you truly want a page kept out of search, not to hide an unexplained problem on a page that should appear.

Don’t treat the indexed-page total as a score

A healthy site can have many URLs that don’t belong in search, because what matters is whether the right service, product and information pages appear.

When should you ask for technical help?

You may be able to handle reporting delays, page-purpose decisions and basic content checks yourself. Ask a developer or search specialist for help if:

• Google receives a blank or broken version of the page.
• Redirects send visitors or Google to the wrong place.
• Canonical tags change across many pages or point to the wrong URL.
• A site move affected a large section of the website.
• You can’t tell which page should be the main version.

Give the specialist the example URLs, last crawl dates, screenshots and the pattern you found, which saves time and makes it easier for them to explain the next action.

What can this evidence prove?

Search Console can show the version Google last visited and the status it gave the page, while a comparison can show whether Google received the same content that you see. A group of similar pages can also reveal a useful pattern.

These checks can’t reveal every part of Google’s decision, so if a page appears after an edit, that doesn’t prove the edit was the only cause. Google may also have returned at a different time or changed how it handled the site.

Be clear about how sure you are:

• You can be confident when the same fault appears again, such as a noindex tag or missing page content.
• You have a useful lead when the same pattern appears across many similar pages.
• You have a weak clue when one page changes after several edits were made together.

Start with the first clear cause

To fix ‘Crawled - currently not indexed’, check whether the warning is still current and whether the page belongs in Google, then check the settings, compare Google’s version with your own and look for a pattern across similar pages.

Change the first cause that the evidence supports. If the checks move beyond your knowledge, pass the notes to a developer or search specialist rather than guessing.