Is Crawled — currently not indexed a penalty?

No. Penalties and manual actions are a separate system with their own Search Console report. This status is routine triage — every large site has pages in it, and a healthy site can have thousands. It becomes a problem when the pages you actually need to rank are in it, or when its growth tracks your publishing rate.

Should I fix my rendering to get out of this status?

Only if the check shows Google evaluated a thinner page than users see — a CSR verdict or a hybrid where the substance is client-side. If your content is in the raw HTML, Google saw everything and declined anyway, and rendering work will change nothing. That single distinction is what saves weeks of misdirected engineering.

Why does requesting indexing not work for these pages?

URL Inspection's request prompts a recrawl; it does not overrule the evaluation. If the page re-presents the same signals, it lands back in the same status — which is why requests seem to work briefly and then revert. Change the page or its duplication picture first, then request, and the request has something new to carry.

The pages are indexed on Bing but not Google — why?

Different engines set the indexing bar differently, and Google's evaluation is comparatively aggressive about near-duplicates and thin templates. A page indexed elsewhere but held out of Google is usually sitting right at that quality or duplication threshold. Treat Google's stricter judgment as the target, since it's where the traffic is.

Should I noindex or delete pages stuck in this status?

For pages that never needed to rank — filters, tags, thin utility pages — yes: noindex them and remove them from the sitemap, which cleans up the report and concentrates crawl attention. For pages you want ranking, no: improve or consolidate them instead. Deleting content that has value because a report shows a status is backwards.

HomeFixCrawled, not indexed

Google saw your page and said no.

Short answer

Crawled — currently not indexed means Google fetched your page, evaluated the content, and chose not to index it. Because the content was seen, this is usually a quality, duplication, or soft-404 decision — not a rendering failure. One check rules rendering out; the real fixes are consolidation, stronger content, and better internal linking.

This page is going to argue with you a little. Most guides on this status recommend technical fixes because technical fixes feel actionable. But the status itself tells you the technical layer mostly worked: crawling succeeded, and in the common case rendering did too. What failed is the audition.

Is this actually your problem?

!Search Console's Pages report shows URLs under “Crawled — currently not indexed”

!The affected pages are product variants, tag/filter pages, thin location pages, or templated content

!The count grows as you publish more pages of the same type

!URL Inspection shows a successful crawl with a recent date — and no index entry

!Requesting indexing works briefly or not at all, and pages drift back

!The pages look fine to you in a browser — which is exactly why the status is confusing

If your status is Discovered — currently not indexed, that is a different animal: Google knows the URL but never fetched it, and the diagnosis runs through crawling, not evaluation. That case has its own page.

What this status actually means

Google's pipeline is discover → crawl → (usually) render → evaluate → index. This status places your page past the crawl and into the evaluation, where it was judged not worth adding — or not worth adding again, if Google believes it already has this content at another URL. Indexing is not a right that pages earn by existing; it's a resource Google allocates, and this status is the allocation saying no.

The three verdicts hiding behind the one label: duplicate("we indexed a version of this already — possibly on your own site"), thin("this page doesn't justify an index entry on its own"), and soft 404("this returned 200 but looks like a dead end"). All three are content and architecture problems. None of them is fixed by changing how the page renders.

Rule rendering out in one check

So why run a rendering check at all? Because there is exactly one way rendering sneaks into this status — content that loads client-side and failed during Google's render, making the evaluated page thinner than the one you see — and one check eliminates it in ten seconds. Then you can do the harder work without a nagging "but maybe it's technical" in the back of your mind.

See the page the way Google evaluated it

https://

Reading the result

On this page the verdict is read almost backwards — green does not mean you're fine, it means the problem is elsewhere:

Result	What it means for this status
SSR	Your content is in the raw HTML — Google evaluated the full page and still declined it. Rendering is cleared. The cause is quality, duplication, or soft-404 signals, and steps two through six are your entire path.
HYBRID	Part of your content arrives only after JavaScript. Check WHICH part: if the main content is server-served and only widgets are client-side, treat this as green. If the substance is in the client-only portion, the evaluated page may have been thinner than you think — the minority rendering case applies.
CSR	The raw HTML is an empty shell and everything depends on Google's render succeeding. Now rendering IS plausibly involved — a slow or failed render would leave Google evaluating a nearly blank page. Fix rendering first, then re-run the quality audit on what remains in this status.

Image slot

Screenshot: a green SSR result for a not-indexed page \u2014 the proof that rendering isn't the cause.

The most useful green result on the site: it tells you to stop debugging rendering and start auditing content.

How to fix it

Six steps. One rules out the technical layer; five do the real work.

Rule rendering out in one check

Run the comparison below. If the raw HTML already carries your content — or the rendered version does — Google saw it too, and rendering is not your problem. Only if the rendered version is thin or empty do you have the minority case where a rendering fix applies. Settle this first so you stop suspecting it.

Check whether the page is a duplicate in Google's eyes

Near-identical product variants, paginated archives, filtered category URLs, thin location pages, and boilerplate-heavy templates all collapse into 'we already have this.' Search site:yourdomain.com for the page's core phrase — if three of your own URLs say substantially the same thing, Google indexed its pick and parked the rest here.

Audit the page against a hard quality question

Would a stranger arriving from search find this page worth the click on its own — without the rest of your site around it? Pages that exist to fill out a template, target a keyword permutation, or hold two hundred words of filler are exactly what this status is built to filter. Be honest here; this step is where most of these pages actually fail.

Look for soft-404 and empty-state signals

Out-of-stock products with no alternatives, 'no results found' listing pages, expired posts, and placeholder pages read as soft 404s even with a 200 status. Google declines to index pages that look like dead ends. Either give these pages real content, redirect them somewhere useful, or let them 404/410 honestly.

Strengthen internal links to pages that deserve indexing

A page reachable only from a sitemap or a page-9 archive link looks unimportant, and importance is part of the indexing decision. Link the pages you actually care about from your homepage, hub pages, or top articles. If a page isn't worth an internal link from anywhere prominent, ask whether it's worth indexing at all.

Consolidate or prune what's left, then wait a full recrawl cycle

Merge overlapping pages into one strong URL with redirects, noindex the utility pages that never needed to rank, and improve the survivors. Then request indexing on your best candidates and give it weeks. Pages leave this status on Google's schedule when the underlying signals change — there is no button that forces it.

The one case where it IS rendering

For completeness, the narrow technical path: a page whose main content loads client-side from an API can render fine for you and poorly for Google — the render times out, the API call fails from Google's infrastructure, or an error boundary swallows the page. Google then honestly evaluates a thin page and honestly declines it. The tells: a CSR or content-light HYBRID verdict above, plus Search Console's "View crawled page" showing less content than your browser does. The fix in that case is the standard one — get the substance into the server response — covered in depth on the React indexing page and the Googlebot page.

How long recovery takes

Slower than you want, and honestly so — this status changes when Google's opinion of the page changes, which happens on recrawl, not on request.

When	What to expect
Week 1	Consolidation ships: merges, redirects, noindex on utility pages, internal links added. Request indexing on your strongest handful of candidates only — spraying requests across hundreds of URLs does nothing.
Weeks 2–4	Improved pages start moving as they're recrawled. Expect the strongest, best-linked pages to flip first. Redirected duplicates drop out of the report.
Weeks 4–8	The long tail resolves. Some pages will simply stay in this status — that is Google holding its opinion, and the remaining options are further consolidation or accepting that those pages won't index.
Ongoing	Watch the ratio of indexed to crawled-not-indexed as you publish. If every new batch of pages feeds this status, the template itself is producing pages below the indexing bar — fix the template, not the URLs.

Common questions

Sometimes, for genuinely good pages that were queued behind capacity — those can index on a later recrawl without changes. But pages held here for quality or duplication reasons stay until the underlying signal changes. If a URL has sat in this status through multiple recrawls over a couple of months, treat it as a decision rather than a delay.