Crawled - Currently Not Indexed: Causes and Fixes

TL;DR

The status sits in Search Console's Page indexing report: Googlebot fetched the URL, found no noindex or robots block, then left it out of the index.
Google's help page says these URLs may or may not be indexed later and do not need to be resubmitted, so Request indexing on an unchanged page rarely helps.
'Discovered - currently not indexed' stops before the crawl; 'Crawled' stops after it, so crawl budget fixes rarely apply.
Typical causes are thin pages, near-duplicates, weak internal links, conflicting canonicals and content that only appears after JavaScript rendering.

"Crawled - currently not indexed" is a Google Search Console status meaning Googlebot fetched the page but Google decided not to add it to the index, at least for now. It is a quality and prioritisation decision rather than a technical error, so the fix is usually to make the page more worth indexing, merge it into a stronger page, or accept that it should stay out.

The status lives in the Page indexing report, under the "Why pages aren't indexed" table. Anyone who searches for crawled currently not indexed usually arrives with a long list of URLs and one question: is this a problem, and if so, what actually moves a page from this bucket into the index? This guide answers that, covering what the status means, how it differs from its sibling status, the usual causes, how to diagnose a single URL, what fixes work and which ones waste time.

What "Crawled - currently not indexed" means in Search Console

Google's indexing pipeline has separate stages. A URL is first discovered (through links, sitemaps or redirects), then crawled (Googlebot requests it and receives a response), then processed and rendered, and finally Google decides whether to store it in the index so it can appear in results. "Crawled - currently not indexed" tells you the first stages succeeded. Google received the page, there was no blocking robots.txt rule, no noindex directive, and no server error. Then it chose not to index it.

Google's own help documentation describes the state in plain terms: 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. That last point matters, because it tells you the problem is not that Google missed the page. It saw the page and made a call.

Two things follow from that. First, a URL in this bucket is not "broken" in the way a 404 or a 5xx is broken. Second, the cure sits mostly with the page and the site, not with any button in Search Console.

How it differs from "Discovered - currently not indexed"

The two statuses look alike in the report but sit at different points in the pipeline, and they point to different fixes.

Discovered - currently not indexed: Google knows the URL exists but has not crawled it yet. Google's documentation notes that this often happens when crawling the URL at that moment was expected to overload the site, so the crawl was rescheduled. The bottleneck is crawling.
Crawled - currently not indexed: Google has already crawled the URL. The bottleneck is the indexing decision.

For large sites, "Discovered" can be connected to crawl capacity and crawl demand, which Relevant Audience covers separately in its crawl budget guide. "Crawled" is rarely a crawl budget issue, because the crawl already happened. Treating it as one, for example by tweaking crawl settings or server capacity, normally changes nothing.

The quick comparison below summarises where each status sits and what to work on first.

How it differs from "Discovered - currently not indexed"
Status	Where the pipeline stopped	Where to look first
Discovered - currently not indexed	Before crawling: URL known, not yet fetched	Server capacity, URL volume, internal links, sitemap hygiene
Crawled - currently not indexed	After crawling: fetched, not stored in the index	Content value, duplication, canonical signals, internal linking
Excluded by "noindex" tag	After crawling: page told Google not to index it	Whether the noindex is intentional
Duplicate, Google chose different canonical than user	After crawling: indexed under another URL	Canonical tags, redirects, near-duplicate content

Common causes of Crawled - currently not indexed

Google does not publish a per-URL reason, so the causes below are the well-established patterns that explain most cases. Several can apply to the same page.

Thin or low-value content

Pages with very little unique text, auto-generated pages, empty category or tag archives, search result pages and placeholder pages often end up here. If the page answers nothing that is not already answered better elsewhere on the site or the web, Google has little reason to spend index space on it.

Duplicate or near-duplicate pages

Product variants that differ only by colour, location pages built from one template with the city name swapped, printer-friendly versions, URLs with tracking or sorting parameters, and paginated series can all look like copies of each other. When Google sees many near-identical pages, it tends to index one and leave the rest out. Sometimes that shows up as a canonical status; sometimes as crawled but not indexed.

Weak internal linking

A page that is reachable only from the XML sitemap, or buried many clicks deep with no contextual links pointing at it, sends a signal that the site itself does not consider it important. Internal links help Google understand which pages matter and how they relate to each other.

Mixed canonical signals

If a page's canonical tag points elsewhere, while the sitemap lists it and internal links point to it, Google gets contradictory hints. The result can be that neither URL is handled the way you intended.

Rendering problems

On JavaScript-heavy sites, the HTML Googlebot first receives may contain almost no content, with the main text loaded later by scripts. If rendering fails or the important content never appears in the rendered HTML, Google evaluates a nearly empty page.

Non-page URLs

Feed URLs, API endpoints, file URLs and other resources that are not meant to be search results often appear in this bucket. These are normally fine to leave alone.

Site-wide quality signals

Google evaluates pages partly in the context of the whole site. So a large, sudden rise in this status is worth a site-level review as well as a page-level one.

How to diagnose a URL with URL Inspection

The Page indexing report gives you a sample of affected URLs, not a full audit. The URL Inspection tool is where you check an individual page. A practical sequence:

Confirm the current state. Paste the URL into the inspection bar at the top of Search Console. Report data can lag behind reality, so a URL listed in the report may already be indexed. If the inspection says the URL is on Google, there is nothing to fix.
Read the Page indexing details. Check the last crawl date, whether crawling and indexing were allowed, the user-declared canonical and the Google-selected canonical. If Google picked a different canonical, you are dealing with duplication rather than a pure quality decision.
Run "Test live URL". This fetches the current version of the page. Open the tested page view to see the rendered HTML and screenshot, and confirm the main content is actually present after rendering.
Look at how the URL was found. The inspection result can show referring pages and sitemaps. If no internal page links to it, that is a clue.
Compare with the pages Google did index. Put the excluded URL next to similar URLs that are indexed. What do the indexed pages have that this one lacks: more unique text, more internal links, real search demand, a clearer purpose?
Check for a pattern. Export the sample from the report and group URLs by folder, template or parameter. A pattern (all tag pages, all filter URLs, all pages from one template) usually means one fix covers hundreds of URLs.

Fixes that work, and fixes that do not

Start by sorting excluded URLs into two groups: pages that should be indexed, and pages that should not. Many URLs in this bucket belong in the second group, and the right action for them is to leave them out cleanly.

For pages that should be indexed

Improve the page itself. Add unique, useful content that matches what a searcher wants: specifics, steps, comparisons, original data, clear answers. Rewriting the same thin text with different words does not count.
Consolidate near-duplicates. Merge several weak pages into one stronger page, then 301-redirect the old URLs or point canonicals at the main version.
Strengthen internal links. Link to the page from relevant, already-indexed pages with descriptive anchor text, and make sure it is reachable through normal navigation as well as the sitemap.
Align canonical signals. The canonical tag, sitemap entry, internal links and hreflang annotations should all point to the same preferred URL.
Fix rendering. Make sure the main content is present in the rendered HTML, ideally in the server response itself.

For pages that should not be indexed

Add a noindex tag, or canonicalise them to the main version, or remove them from the sitemap and internal links if they serve no purpose.
Delete pages with no users and no purpose, returning a 404 or 410, or redirect them if a close equivalent exists.
Leave feeds and other non-page resources alone.

What does not work

Repeatedly clicking "Request indexing". It asks Google to recrawl, but the page was already crawled. Without a change to the page, the decision usually stays the same, and the feature has a daily quota.
Resubmitting the sitemap. Google already knows the URL. Resubmitting changes nothing about its value.
Cosmetic edits. Changing a date or a few words does not change how useful the page is.
Buying links to the page. This creates spam risk without fixing the underlying reason.

When to ignore Crawled - currently not indexed

A non-zero count is normal. Every site of any size has URLs Google crawls and chooses not to index. You can usually ignore the status when:

The listed URLs are feeds, parameter variants, internal search pages, pagination or other URLs you never wanted in results.
The count is stable over time and your important pages are indexed.
URL Inspection shows the listed page is in fact indexed now, which means the report has not caught up yet.

It deserves attention when the URLs are pages you depend on (service pages, product pages, articles you wrote to rank), when the count rises sharply after a migration, template change or content launch, or when a whole section of the site appears in the list.

How the validation flow works

Once you have fixed a pattern, you can open the status in the Page indexing report and click "Validate fix" where the option is offered. Google then recrawls the affected URLs over time and reports progress as started, passed or failed. Google's help page says validation typically takes up to about two weeks, sometimes much longer, and asks you not to click Validate fix again until the current validation has passed or failed.

Two practical notes. Validate only after the fix is live across the whole pattern, otherwise the validation is likely to fail on the URLs you have not fixed. And remember that a passed validation means Google rechecked the URLs, not that every one of them will be indexed. For pages you decided to keep out of the index, there is nothing to validate.

To measure progress, track the indexed count for the affected folder or template in the Page indexing report, and use URL Inspection on a handful of representative URLs every week or two. If you want a broader picture, compare impressions for the section in the Performance report before and after the change.

What this means for Thai websites

On a bilingual Thai and English site, candidates to check include thin machine-translated versions of English pages, Thai pages that only translate the title while keeping English body text, and city or province pages built from one template. Where the Thai and English versions exist, hreflang tags and canonicals should agree, with each language version canonical to itself and both listed as alternates.

If a Thai e-commerce site generates many URLs from filters, sorting and product variants, deciding which of those deserve to be indexed, and handling the rest with canonicals, noindex or parameter-free internal linking, usually reduces the noise in this bucket and lets Google focus on pages that carry demand. For larger catalogues, an ecommerce SEO review of category and filter templates tends to have more impact than fixing URLs one by one.

A structured SEO audit is the most efficient way to separate pages that should be indexed from pages that should not, because it groups excluded URLs by template and cause instead of treating each one in isolation.

FAQ about crawled currently not indexed

Is "Crawled - currently not indexed" a penalty?

No, it is not a penalty or a manual action. It means Google crawled the page and chose not to index it for now, which is a normal prioritisation decision. Manual actions appear in their own report in Search Console.

Should I click "Request indexing" for these URLs?

Only after you have meaningfully changed the page. Requesting indexing for an unchanged page asks Google to recrawl something it has already evaluated, and the outcome is usually the same.

How long does it take for a fixed page to be indexed?

There is no fixed timeline. Google recrawls pages on its own schedule, and Google's help page says validation typically takes up to about two weeks but can take much longer.

Can a page move out of this status on its own?

Yes, Google's documentation says such pages may or may not be indexed in the future. Pages sometimes get indexed later as the site gains links or the page gains relevance, but for important pages it is better to improve them than to wait.

Does this status affect the rest of my site's rankings?

The excluded pages themselves cannot rank because they are not indexed. A large share of low-value pages can also affect how Google perceives the site overall, which is why a growing count deserves a site-level look.

Get a clear indexing plan

If important pages are stuck as crawled but not indexed, Relevant Audience can review the affected templates, separate the URLs that should rank from the ones that should not, and plan the content and linking changes that give the right pages a reason to be indexed. See our technical SEO audit service, our wider SEO services in Thailand, or our content marketing team for pages that need stronger content.