SanskarTiwari.io
Free Guide

How to Fix “Crawled – Currently Not Indexed”

by Sanskar Tiwari · @sanskarr.tiwari

Google crawled 13,200 of my pages and refused to index them. This is the real Search Console report from magicslides.app, what the message actually means, and the exact fixes that took it from 75,000 to 13,200 in three months.

The whole thing in one line: “Crawled – currently not indexed” is Google saying we looked at this page and it didn't qualify. Not that you're behind a competitor. That the page isn't worth a slot. Fix the page or remove it — nothing else moves this number.

Want it as a PDF (and future guides)? Drop your email — I'll send it over. No spam.

The report most people never open

Search Console → Indexing → Pages. Here is mine, today. 3,590 indexed. 103,000 not. Twelve different reasons. I run Search Console on 29 sites and this one report explains more lost traffic than any keyword tool.

Search Console page indexing for magicslides.app: 103k not indexed, 3.59k indexed
magicslides.app, 5 Sep 2026. The grey bar is every URL Google knows about and refuses to serve.

Most of the 103k is fine. Robots blocks I chose. 404s for junk. The one row that matters is the one Google calls Crawled – currently not indexed, because those are pages I wanted in the index.

53,969
Blocked by robots.txt
Fine if you did it on purpose. Mine is on purpose — mostly.
32,882
Not found (404)
Junk URLs Google found once and keeps re-checking.
13,200
Crawled – currently not indexed
The dangerous one. Google saw the page and said no.
1,218
Page with redirect
Harmless bookkeeping.
555
Alternative page with proper canonical
Working as intended.
467
Excluded by 'noindex' tag
You asked for it.
Why pages aren't indexed table with page counts
The full reason table. Sort by Pages, then ignore everything you did on purpose.

What the message actually means

Google found the URL, fetched it, rendered it, and decided not to put it in the index. There is no error to fix. No status code. No redirect. It is a quality decision: not enough content, not enough unique content, or too many pages that look the same.

Hundreds of pages rejected off the bat means hundreds of pages that never even got a chance to rank. They are not competing and losing. They are not in the race.

The 5 things that land pages here

1
Thin pages — A title, a hero, and nothing else. Google crawled it, found no reason for it to exist, and moved on. This is the classic cause and it's still the most common one.
2
Half-translated pages — My case. I generated /es/, /it/, /hu/ versions of every tool page. The title and hero were translated, the rest of the page was still English. Hundreds of them, rejected off the bat.
3
Duplicate-ish pages — Ten pages that say the same thing with a different keyword in the H1. Google indexes one, maybe, and parks the rest here.
4
Crawl traps — URL patterns your app answers with 200 no matter what you put in them. Every garbage slug becomes a "page". Google crawls thousands, indexes none, and your real pages wait in the queue.
5
Non-HTML files in the sitemap — llms.txt, openapi.json, sitemap.xml itself. They show up in this report because Google crawled them and there is nothing to index. Harmless, but they muddy the list.
Example URLs in the crawled not indexed report
My examples list: /es/tools, /it/tools, /hu/… half-translated pages, plus llms.txt and openapi.json which are not pages at all.

The crawl trap that made it worse

My robots.txt blocked /p/. But every rule was root-anchored, so /fr/p/, /zh/p/ and every other locale path walked straight past it. Worse, the app answered any slug under those paths with a 200 and a full page. Google crawled 100,000+ of them. None indexed. Meanwhile my real pages waited.

Two fixes. The tourniquet: Disallow: /*/p/ in robots.txt. The real one: unknown slugs return 404 from the app. Both, not either.

Do this today — the 7 steps

1
Open the report — Search Console → Indexing → Pages → "Why pages aren't indexed" → Crawled – currently not indexed. Look at the trend first, then the Examples table.
2
Sort the examples into buckets — Read 50 URLs, not 5. Every URL falls into one of: thin, half-translated, duplicate, crawl-trap, or not-a-page. You'll usually find one bucket is 80% of the list.
3
Fix the page or remove it — Thin page you care about? Add the actual content — a real answer, screenshots, an example. Page you don't care about? Delete it and return 404 (or 410). Don't leave a half-page hoping Google changes its mind. It won't.
4
Close the crawl trap — Find the pattern that returns 200 for anything. Make unknown slugs return 404 in the app. Then block the pattern in robots.txt — for me that was Disallow: /*/p/ because /fr/p/, /zh/p/ were escaping the /p/ rule.
5
Finish the translation or kill it — A page in Spanish has to be fully in Spanish. If you can't translate the whole page, don't ship the locale. I dropped the half-translated ones instead of pretending.
6
Request indexing — after the fix — URL inspection → Request indexing works on a handful of pages you actually changed. Requesting indexing on an unchanged thin page does nothing. Google already looked.
7
Watch the trend, not the number — The count won't drop overnight. Mine went 75,000 → 13,200 over three months. What you want is the line pointing down every week.

What happened after the fix

Blocked the trap, 404'd the junk, dropped the half-translated pages. The report went from 75,000 to 13,200 in three months and it is still going down. Nothing else changed.

Crawled currently not indexed trend dropping from 75k to 13.2k
First detected Feb 2023. The drop starts the week the robots rule and the 404s went live.

If you build pages with AI — and I do, with BuildCheap — this report is the difference between 500 tool pages that rank and 500 tool pages Google quietly ignores. Generate the page, then make it actually complete before it ships.

Keep going

Getting indexed is step one. Here's the rest of the stack — build it, launch it, get found, then convert.

Build the app itself

BuildCheap — ship web & mobile apps with real $-per-action pricing, no confusing credits.

Start building

Learn to vibe-code

My course on building apps with AI — no coding needed.

Explore the course

Get your first visitors

106 hand-picked places to launch & promote your startup.

Browse the directory

Build SEO authority

166 dofollow backlink sources, filterable by DR, category & type.

See the list

If you do only one thing: open the Examples table, read 50 URLs, and delete the ones you would be embarrassed to show a human. Google already has.

Get the PDF + future guides

Drop your email and I'll send the printable PDF — plus the next guides as I make them.