“Crawled - currently not indexed” in Search Console: what it means and how to fix it

What the two statuses mean

Search Console’s Page indexing report lists every URL Google knows and why it isn’t indexed. Two reasons confuse people most:

• Crawled, currently not indexed: “The page was crawled by Google but not indexed.” Google adds that it may or may not be indexed in the future, and that there’s no need to resubmit it (Search Console Help, Page indexing report, read 15 Oct 2026).
• Discovered, currently not indexed: the page was found but not crawled yet. Google wanted to crawl it, expected that to overload the site, and rescheduled the crawl, which is why the last crawl date is empty (same page).

Google says a page can be not indexed for reasons other than an error. The job is to sort the rows into “fine as it is”, “old URL that needs a redirect” and “real page Google doesn’t want yet”.

Usual causes on app and vibe-coded sites

Google’s crawl budget guide is written for sites with 10,000 or more fast-changing pages. On a fifty-page site, “Discovered” is about links and patience.

A worked example: our own site, October 2026

Search Console’s report of 9 October 2026 for katman.pro showed 41 pages indexed and 235 not indexed, across seven reasons. The live sitemap was clean: every listed URL answered 200 and was indexable. The not-indexed rows were almost all URLs from earlier sites on the same domain.

The cause: when we moved katman.pro to a new codebase on 30 September, its routing had none of the old redirect rules, and about 285 old URLs started answering 404. On 15 October we probed 364 historical URLs: 270 answered 404 and 15 more redirected to a 404.

The fix was one-hop 301s: each old URL now goes straight to the English page with the same job (a retired German pricing URL to /pricing, for example), and unknown old slugs return a plain 404. “Everything to the home page” was the earlier mistake: Google’s site-move guide says many old URLs redirected to one irrelevant page might be treated as a soft 404, and advises redirecting to the final destination directly. We expect the “Page with redirect” count to fall over weeks, not days.

How to fix it, step by step

1. Export the rows. Open each reason in the report and export the URL list.
2. Check what each URL returns today.
3. Old URLs: add a 301 to the closest live page, in one hop, and keep it for at least a year, as Google’s site-move guide advises. If nothing matches, let it return 404.
4. Real pages: text in the HTML without JavaScript, a unique title and first paragraph, links from indexed pages with a normal <a href>, and a sitemap entry.
5. Request indexing in URL Inspection for your most important fixed pages only.
6. Validate fix on the 404 group once the redirects are live. Leave “Page with redirect” alone.
7. Tell Bing too: it has its own index; see Does ChatGPT use Bing?.

Example: check every exported URL in one go

Save the “URL” column of the export as urls.txt, one URL per line, then run:

while read -r u; do
  echo "== $u"
  curl -sIL "$u" | grep -iE '^(HTTP/|location:)'
done < urls.txt

Good output for an old URL: one 301, one location:, then HTTP/2 200. Two location: lines mean a chain to shorten.

What Katman does here, and what it can’t

Katman is an MCP server that runs inside your AI coding tool. katman_audit_site checks your live pages for status codes, redirects, soft 404s, noindex, canonicals, words visible without JavaScript and internal links, and katman_prompt hands your coding tool the fix with an acceptance check. Your coding tool makes the change; Katman checks it was made. Katman Pro is $99 a month for up to 3 sites, with fix prompts and page briefs uncapped. Or have us do it: Growth writes 30 pages a month for you.

It can’t read your Search Console account, so you bring the exported URLs, and it can’t make Google index a page; nobody can. For bot access alone, the AI crawler checker is free.

Written by the Katman team, Rnify Limited. Google pages checked 15 October 2026; katman.pro figures from our own Search Console and a URL probe, 9 to 15 October 2026.