---
title: "Crawled, currently not indexed: causes and fixes"
description: "“Crawled” means Google fetched the page and chose not to index it; “Discovered” means it hasn’t fetched it yet. How to read the report, fix old URLs and real pages."
url: https://katman.pro/crawled-currently-not-indexed
lang: en
updated: 2026-10-17
---

Guide Updated 17 Oct 2026

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

> “Crawled, currently not indexed” means Google fetched the page and decided not to index it for now; “Discovered, currently not indexed” means Google knows the URL but hasn’t fetched it yet. Neither is an error by itself. Export the URLs, check what each returns today, 301 dead old URLs to their closest live page in one hop, and give real pages text in the HTML, links and a sitemap entry. Then wait.

## 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](https://support.google.com/webmasters/answer/7440203), 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

| What the URL is | Typical status | Why | Fix |
| --- | --- | --- | --- |
| A real page, new site | Discovered | Few links point to it; Google hasn’t got round to it | Link it from pages that are indexed, keep it in the sitemap, wait |
| A real page with little text in the HTML | Crawled | Without JavaScript the page is a near-empty shell | Server rendering or prerendering for public pages (see [six traps for vibe-coded sites](https://katman.pro/vibe-coded-site-invisible-to-chatgpt)) |
| A page that repeats another page | Crawled, or a duplicate status | Same title, same text, different URL | Merge, or make the job of each page different |
| An old URL from a previous version of the site | 404, or Crawled | It no longer exists | 301 to the page that does the same job now |
| Login, app screens, parameter URLs | noindex or alternate canonical | Working as intended | Nothing |

Google’s [crawl budget guide](https://developers.google.com/search/docs/crawling-indexing/large-site-managing-crawl-budget) 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.

| Reason | Count | What it was |
| --- | --- | --- |
| Page with redirect | 156 | Retired language versions, all sent to the home page |
| Not found (404) | 27 | Old URLs the new site had no rule for |
| Discovered, currently not indexed | 22 | New pages and old orphan pages |
| Crawled, currently not indexed | 18 | Mostly old pages with no links and no sitemap entry |
| Others (alternate canonical, noindex, duplicate) | 12 | Login and parameter URLs, mostly expected |

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](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) 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?](https://katman.pro/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:

```bash
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](https://katman.pro/mcp) 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](https://katman.pro/done-for-you) 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](https://katman.pro/tools/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.

## Who this is not for

-   Sites with a manual action or a security issue in Search Console: fix that report first.
-   Large sites with millions of URLs: Google’s crawl budget guide is written for you, and this page isn’t.
-   Anyone who wants a way to force Google to index a page: there isn’t one.

## Frequently asked questions

### What is the difference between “Crawled” and “Discovered - currently not indexed”?

Crawled means Google fetched the page and chose not to index it for now. Discovered means Google found the URL but hasn’t fetched it yet; it rescheduled the crawl, so the last crawl date is empty.

### Should I click “Request indexing” for every URL in the report?

No. Google says there’s no need to resubmit a crawled URL, and the tool has a small daily quota. Use it for a handful of your most important pages after you have fixed them.

### Should I click “Validate fix” on “Page with redirect”?

No. A redirecting URL is never indexed itself, only its target, so those URLs leave the report slowly on their own. Validate the 404 group after your redirects are live.

### Is it bad to redirect all my old URLs to the home page?

Yes. Google’s site-move guide says many old URLs redirected to one irrelevant page, such as the home page, might be treated as a soft 404. Send each one to the page with the same job.

### How long does a fixed page take to get indexed?

Google says validation usually takes up to about two weeks and can take longer. Pages Google only “Discovered” can take longer still on a new domain, because nothing forces a crawl.

### Does this report matter for ChatGPT?

Indirectly. ChatGPT search uses its own crawler, so a page can be read by OAI-SearchBot and still be absent from Google. But the causes, empty HTML and weak internal links, hurt both.

## Related pages

-   [**I built my site with Lovable, Bolt or Cursor, and ChatGPT never mentions it** Built it with Lovable, Bolt, v0 or Cursor and ChatGPT never mentions it? Six traps hide vibe-coded sites; each has a one-minute test and a fix for your AI tool.](https://katman.pro/vibe-coded-site-invisible-to-chatgpt)
-   [**Does ChatGPT use Bing’s index?** ChatGPT search runs its own crawler, OAI-SearchBot, and sometimes uses partner search providers; Copilot runs on Bing. What that means and how to get into Bing.](https://katman.pro/does-chatgpt-use-bing)
-   [**AI crawler checker** Free: we load your homepage as GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot and 8 other bots, then show which ones your CDN blocks and what robots.txt says.](https://katman.pro/tools/ai-crawler-checker)
-   [**The Katman method: research, plan, build, verify** Four steps, three gates and 15 prompts with acceptance criteria that make a site readable, quotable and recommendable by ChatGPT, Claude, Gemini and Perplexity.](https://katman.pro/method)
-   [**How do I track traffic from ChatGPT in Google Analytics 4?** GA4 has an AI Assistant channel since May 2026, but ChatGPT often sends no referrer. Use utm\_source=chatgpt.com and a custom channel group regex to count it all.](https://katman.pro/track-chatgpt-traffic-ga4)
-   [**Katman MCP** Katman MCP runs in Cursor, Claude Code and VS Code: it scans your code, audits your live site like AI crawlers do and checks every fix. Katman Pro from $99/month.](https://katman.pro/mcp)

Updated 17 October 2026 · Katman