Crawled – Currently Not Indexed: What It Means and How to Fix It

"Crawled – currently not indexed" means Googlebot visited and read the page, then decided not to add it to Google's index. Nothing is technically blocking it; Google judged the page not worth storing right now, or received something different from what you see in your browser. The fix is to find out which of those two it is, then change the page or the site, not to keep clicking "Request indexing".

My guide on why a website is not showing on Google covers every indexing status in brief. This article goes deep on this one.

What Google's definition actually says

Google defines the status as: "The page was crawled by Google but not indexed. It may or may not be indexed in the future." That wording comes from the Page Indexing report documentation (Google Search Console Help, 2026). Google adds that there is "no need to resubmit this URL for crawling."

Two other Google statements explain why the status exists:

• Indexing is selective. Google's How Search Works guide (Google Search Central, 2025) states: "Indexing isn't guaranteed; not every page that Google processes will be indexed." It names low-quality content and website design that makes indexing difficult as common causes.
• Duplicates get clustered. The same guide explains that Google groups pages with similar content and picks one canonical to show. Near-copies of an existing page lose that contest.

Crawled vs discovered: what is the difference?

"Discovered – currently not indexed" means Google knows the URL exists but has not fetched it yet, while "Crawled – currently not indexed" means Google fetched it and declined. The Page Indexing documentation explains that Discovered URLs usually wait because crawling them "was expected to overload the site", so Google rescheduled.

The two statuses point to different problems:

Google's crawl budget guide (Google Search Central, 2025) states that crawl capacity goes up when a site responds quickly and goes down when it returns server errors. A large Discovered count is a server and architecture problem first, which is why my guide on how a slow website hurts SEO matters here.

When "crawled – currently not indexed" is normal

Leave the status alone on URLs that never deserved a place in search. Every site of more than a few dozen pages has some, and chasing them wastes time.

These URL types are safe to ignore:

• Feeds, such as /feed/ and /comments/feed/ on WordPress.
• Paginated archives, such as /blog/page/7/.
• Parameter URLs, such as ?sort=price, ?utm_source= or ?replytocom=.
• Thin tag and author archives that list the same posts as category pages.
• Internal search results, such as /?s=shoes.
• Attachment and media pages that hold only an image.

Templated location or product pages built from thin data are not safe to ignore: they show up here in bulk. My guide on how to use Python for programmatic SEO covers the data test and quality gate that keep generated pages indexed.

Filter the report's example list by URL pattern. A status that only covers these types needs no fix, and noindexing or stopping internal links to them keeps crawling focused on real pages. Act when the list contains pages you want to rank: service pages, product pages, location pages or blog posts.

How to diagnose it, in order

Work through these 6 checks in sequence. The early checks are faster and rule out technical causes that look like quality problems.

1. Run a URL Inspection live test

Open URL Inspection, paste an affected URL and click "Test live URL". Confirm the page returns HTTP 200, is "available to Google", and is not blocked by robots.txt, noindex or a login. A failed live test means a technical cause, not a quality judgement.

2. Check the rendered HTML and screenshot

Click "View tested page" and read the HTML tab, then the screenshot. Confirm the main content, headings and internal links exist in the rendered HTML. A page built with client-side JavaScript sometimes renders as an empty shell, a loading spinner or a cookie wall to Googlebot, and Google then sees a page with nothing worth indexing.

3. Compare duplication and canonicals

Check "User-declared canonical" against "Google-selected canonical" in the inspection result. Then search Google for a distinctive sentence from the page in quotes. Find the page your URL competes with, such as a near-identical location page, a manufacturer's product description or an older post on the same topic.

4. Judge the content against indexed competitors

Search the page's main query and open the top 5 indexed results. List what they include that your page lacks: specific prices, original photos, steps, data, first-hand detail or answers to follow-up questions. A 300-word page that restates what 10 indexed pages already say gives Google no reason to store an eleventh copy.

5. Check internal links and orphan pages

Crawl the site with Screaming Frog and count the internal links pointing to each affected URL. Pages with zero or one internal link signal low importance. Compare the crawl against your XML sitemap: URLs in the sitemap but missing from the crawl are orphans that Google reaches only through the sitemap.

6. Look at the site-wide picture

Divide the number of "Crawled – currently not indexed" URLs by your total indexed pages. Google's ranking systems guide (Google Search Central, 2025) states that "site-wide signals and classifiers are also used and contribute to our understanding of pages." A site where 60% of URLs are thin, auto-generated or duplicated drags down the good 40%, and the fix becomes pruning, not polishing one page.

The multi-stack angle: server and code faults that look like quality problems

Many "quality" cases are actually Googlebot receiving a broken, slow or different page. This is the insight a content-only checklist misses, and it is where my work across SEO, programming and security overlaps most.

Check for these 5 technical faults before rewriting any content:

• Soft errors. A page that returns HTTP 200 but shows "No products found", an empty template or an error message gets treated as a soft 404. Google's HTTP and network errors guide (Google Search Central, 2025) states that content suggesting "an empty page or an error message" triggers a soft 404, and that 5xx and 429 errors make Google slow down crawling and ignore the content from those URLs.
• Slow time to first byte. A server that takes 2-3 seconds to respond to Googlebot lowers crawl capacity and leaves heavy pages half-rendered in testing.
• Blocked resources. A robots.txt rule blocking /wp-includes/, /_next/static/ or an API domain stops Googlebot loading the JavaScript or data that builds the page.
• Bot protection. A firewall, CDN challenge or rate limit that serves Googlebot a challenge page instead of the content.
• Cloaked spam from a hack. Injected code that serves spam only to Googlebot makes your clean page look like junk to Google. Compare the live-test HTML with your browser's source. My guide on the Japanese keyword hack shows how this cloaking works.

I have written production code since 2016, including Next.js, PHP and WordPress, and done security research since 2011. A client-rendered product page and a hacked one both look fine in a browser and both show up as "crawled – currently not indexed".

Fixes ranked by impact

Apply the fixes in this order, from the highest impact to the lowest:

1. Repair technical delivery. Server-render the main content, return real 404 or 410 codes for empty pages, unblock CSS and JavaScript, whitelist verified Googlebot and remove any malware.
2. Merge or remove duplicates. Consolidate near-identical pages into one stronger URL with a 301 redirect, and point canonicals, sitemaps and internal links at the survivor.
3. Prune low-value URLs site-wide. Noindex or delete thin tag archives, parameter variants and auto-generated pages so the remaining pages carry the site's quality signal.
4. Add original value to pages that deserve to rank. Add details competitors lack, such as prices, process steps, original images, data and expert answers.
5. Strengthen internal links. Link each important page from 3-5 relevant, already-indexed pages, using anchor text that names the page's topic.
6. Keep the XML sitemap clean. List only canonical, indexable, 200-status URLs, with an accurate lastmod date.

A technical SEO consultant earns their fee on steps 1-3, because those live in templates, server rules and the database rather than in the editor.

Why "Request indexing" keeps failing

Requesting indexing again does not change the page Google already judged, so the decision repeats. Google's recrawl guide (Google Search Central, 2025) states that "requesting a recrawl multiple times for the same URL won't get it crawled any faster", that individual submissions have a quota, and that a request "does not guarantee that inclusion in search results will happen instantly or even at all."

A page sometimes appears in the index for a few days after a request, then drops out again. That pattern confirms the page passes the technical checks but fails the value test. Change the page or the site first, then make one request.

How to validate the fix and how long it takes

Validate the fix in the Page Indexing report once the changes are live across every affected URL. Open the "Crawled – currently not indexed" reason, click "Validate fix", and Google rechecks the listed URLs.

Track the result in 3 places:

• Validation status in the report. Google's documentation states that validation "typically takes up to about two weeks, but in some cases can take much longer."
• URL Inspection on 5-10 priority pages, checking for "URL is on Google".
• Performance report impressions for the fixed pages, which rise once they enter the index.

Expect technical fixes to clear within 2-6 weeks of recrawling, and content or site-wide quality fixes to take 1-3 months, because Google has to recrawl and reassess many pages. Those ranges come from experience-based practice, not published Google data. My guide on how long SEO takes explains the wider timelines once pages are indexed.

Frequently asked questions

Is "crawled – currently not indexed" a penalty?

"Crawled – currently not indexed" is not a penalty. It is Google's decision not to store a page right now; penalties appear separately in the Manual actions report in Search Console.

How do I fix "crawled – currently not indexed" in WordPress?

Fix it in WordPress by noindexing tag, author and attachment archives in your SEO plugin, merging thin or duplicate posts, and checking that caching or security plugins serve Googlebot the full page. Then strengthen internal links to the posts you want indexed.

Does "crawled – currently not indexed" fix itself?

Some URLs move into the index without changes when Google recrawls them later, as its definition says the page "may or may not be indexed in the future." Pages that stay in the status for more than a few months need a technical or content change.

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

"Discovered – currently not indexed" means Google found the URL but has not fetched it, usually because of crawl capacity or weak internal links. "Crawled – currently not indexed" means Google fetched the page and chose not to index it, usually because of value, duplication or rendering problems.

How many "crawled – currently not indexed" pages are too many?

A count is too high when it includes pages you want to rank or covers a large share of the site; as a rule of thumb from practice, not Google data, I investigate once it passes 20-30% of total URLs. A handful of feeds, parameters and archives in the list is normal.