Crawled - Currently Not Indexed: How to Fix It (2026)

"Crawled - currently not indexed" is the Search Console status that worries small business owners the most, because it sounds like Google looked at the page and said no. That is roughly what happened. The good news is that it is usually fixable, and the fix is rarely "request indexing again."

I run a small web business, and my own site had 20 pages in this bucket in October 2026. Below is how I read the report, what Google itself says about it, and the order I fix things in for clients.

What the status actually means

Google's Page indexing report help page defines it in one line: the page was crawled by Google but not indexed. It may or may not be indexed in the future, and there is no need to resubmit the URL for crawling (Google Search Console Help).

So Googlebot fetched the page, read it, and decided not to add it to the index for now. Nothing is technically broken. Google simply did not think the page was worth showing yet.

Crawled vs discovered: not the same problem

The two statuses look alike but point to different fixes:

• Crawled - currently not indexed: Google fetched the page and chose not to index it. This is usually a quality or duplication signal.
• Discovered - currently not indexed: Google knows the URL exists but has not crawled it yet. Google's help page says it typically wanted to crawl the URL but expected the crawl to overload the site, so it rescheduled. That is why the last crawl date is empty.

If most of your problem URLs are "Discovered," look at server speed, crawl stats and internal links first. If they are "Crawled," look at the pages themselves.

Why Google crawls a page and still skips it

In my experience, the URLs in this bucket usually fall into one of these groups:

• Thin or templated pages. Location or industry pages that swap one word and keep the same text. Tag and archive pages. Old blog posts of 300 to 500 words that say what a hundred other posts already say.
• Near duplicates. Two posts on the same topic, or the same page reachable at several URLs (with and without a trailing slash, with tracking parameters, http and https).
• Weak internal links. The page is only in the sitemap, and no menu, service page or post links to it. Google reads that as "the owner doesn't think this matters either."
• New pages on a site with little authority. On a young site with few links from other sites, Google indexes slowly and keeps a short list. Some of these pages get indexed later without any change.
• Pages that render badly for Googlebot. Rare, but worth ruling out if the content loads with JavaScript after the first paint.

How I fix it, in order

1. Export the list and sort it

In Search Console, open Indexing, then Pages, click the "Crawled - currently not indexed" row and export the URLs. Then sort every URL into one of four buckets: keep and improve, merge into a stronger page, redirect, or leave out on purpose.

This is the step most people skip. Not every URL deserves to be indexed. Feeds, paginated archives and old test pages can sit in this report forever without hurting anything.

2. Merge and redirect the weak duplicates

When two or three posts cover the same topic, I keep the best one, fold the useful parts of the others into it, and 301 redirect the old URLs to it. On my own site I went from 43 blog posts to 19 in October 2026 this way. Nothing was deleted from the database; 24 old URLs now redirect to the post or service page that replaced them.

3. Make the keepers genuinely better

For every page you want indexed, ask whether it answers the search better than what already ranks. That usually means real specifics: prices, steps, screenshots, examples from your own work, and an answer in the first few lines. Rewriting the intro and adding two paragraphs rarely moves anything.

4. Add internal links from pages Google already trusts

Link to each keeper from at least one page that is already indexed and gets impressions, such as a service page, your homepage or a popular post. Use descriptive anchor text, not "click here." For a small site, this is often the single cheapest fix.

5. Clean up the sitemap

Your sitemap should list only the canonical, indexable URLs you actually want in Google. Remove redirected, noindexed and parameter URLs. Then resubmit it in Search Console.

6. Check how Google sees the page

Use URL Inspection on one or two of the affected URLs, run a live test and look at the rendered screenshot and HTML. If the main content is missing there, you have a rendering problem, not a quality problem.

7. Request indexing once, then validate

After the changes, request indexing for the most important improved pages, one time each. Then open the issue in the Page indexing report and click Validate fix. Google's help page notes that validation can finish faster if you submit a sitemap of only your most important pages and filter the report by it.

What not to do

• Don't spam the "Request indexing" button. Google's help page says there is no need to resubmit these URLs. Repeated requests without changes do nothing.
• Don't pay for "instant indexing" tools. If Google decided a page isn't worth indexing, forcing a crawl doesn't change its mind.
• Don't panic about every URL. If your important service pages and best posts are indexed, a pile of thin archives in this report is not an emergency.
• Don't publish more of the same. Ten more thin posts usually make the bucket bigger, not smaller.

How long it takes

There is no fixed timeline. On small sites I expect merged and redirected URLs to drop out of the report over the following weeks, and improved pages to be recrawled when Google gets to them. I check the report again two and four weeks after the changes. If an improved page is still not indexed after a couple of months, I treat that as a sign it still isn't different enough, or that the site needs links from other sites.

When to get help

If the list is short, you can do all of this yourself in an afternoon with the steps above. If it is long, mixed with redirects and canonicals, or your service pages are the ones stuck, that is the kind of cleanup I do.

I offer a free Search Console review: a one-page written list of what is blocking your pages, sorted by priority, within 2 business days. If you want the fixes done for you, the SEO fix sprint is $750 one-time and covers indexing issues, redirects, canonicals, the sitemap, titles and internal links. If the site is WordPress and also slow, see the WordPress Speed Fix.

FAQ

Is "Crawled - currently not indexed" an error?

Not technically. It means Google crawled the page and chose not to index it for now. Google says the page may or may not be indexed in the future and there is no need to resubmit it.

Should I click "Request indexing" for every URL in the report?

No. Improve, merge or redirect the pages first. Then request indexing once for the important pages and use Validate fix in the Page indexing report.

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

Crawled means Google fetched the page and decided not to index it, which usually points to content or duplication. Discovered means Google knows the URL but has not crawled it yet, often because it expected the crawl to overload the site.

Can too many low-quality pages hurt the rest of my site?

They can make it harder for Google to see which pages matter. Merging thin pages into stronger ones, redirecting the old URLs and linking to your best pages gives Google a clearer picture.

How much does it cost to fix indexing problems?

If you do it yourself, it costs time. If you want it done for you, my SEO fix sprint is $750 one-time, and the review that comes before it is free.