# Being crawled is not being indexed

Google fetching your page and Google keeping it are different events. Most “my page isn’t ranking” is really a page that was fetched and declined.

Published: 2026-08-19T10:00:00.000Z

Canonical: https://thatseoagent.com/en/blog/crawled-is-not-indexed

Most people treat Google as a single machine that either knows about a page or does not.
It is at least three, and they disagree with each other constantly. Almost every “my page
isn’t ranking” question is really a question about which of the three stopped.

## The three events, in order

A URL has to survive all of these before it can rank for anything:

1. **Discovery.** Google learns the URL exists, from a sitemap, a link, or a redirect.
2. **Crawl.** Google fetches it. Fetching costs Google money and costs your server time,
   so it is rationed — Google's own name for the ration is the
   [crawl capacity limit](https://developers.google.com/search/docs/crawling-indexing/large-site-managing-crawl-budget),
   and it is set by how much load your host can absorb, not by how good the page is.
3. **Index.** Google decides the fetched page is worth storing. This is a judgement, not a
   mechanical step, and it is the one that quietly says no. Google states it plainly:
   “Indexing isn't guaranteed; not every page that Google processes will be indexed.”

Ranking is a fourth thing that happens only to pages that cleared the third. When someone
says “Google isn’t seeing my page”, they usually mean one of the first three, and which one
changes the fix completely.

## The status you get told, and what it means

Search Console reports these in language that sounds procedural but is actually a verdict.
The middle column is Google's own wording, not a paraphrase — worth reading, because two of
these are routinely explained wrongly.

| What Search Console says | What Google says it means | What you should hear |
| --- | --- | --- |
| Discovered - currently not indexed | “The page was found by Google, but not crawled yet.” | A queue, usually not a verdict |
| Crawled - currently not indexed | “The page was crawled by Google but not indexed.” | Fetched, read, declined |
| Duplicate without user-selected canonical | “This page is a duplicate of another page, although it doesn't indicate a preferred canonical page.” | Google kept a different page instead |
| Indexed | It is in | Now you can talk about rankings |

“Crawled - currently not indexed” is the one worth sitting with. Nothing is broken. There is
no error to fix, no header to correct, no robots directive in the way. Google read the page
and decided the index is better off without it. That is a content verdict wearing the
costume of a technical status.

## The one that gets explained wrongly

“Discovered - currently not indexed” is where the industry's stock answer and Google's
documentation part company. The stock answer is that the page was not worth the crawl
budget. Google's own explanation of that status is about your server:

> Typically, Google wanted to crawl the URL but this was expected to overload the site;
> therefore Google rescheduled the crawl.

So the first place to look is not word count. It is response time under load, error rates,
and anything that makes your host slow to answer — because that is what the crawl capacity
limit is computed from.

Crawl budget as a thing you manage is also narrower than it sounds. Google's guide to it
opens by saying who it is for: sites with more than a million pages that change weekly, or
more than ten thousand that change daily. If you publish 400 pages, this is almost never
your problem, and the hours spent on it are hours not spent on the third event.

## Why this matters for what you do next

The instinct when a page is not ranking is to do technical work: check the robots file,
resubmit the sitemap, request indexing, add schema. All of that is aimed at events one and
two. If your page is sitting at “crawled - currently not indexed”, every one of those
actions is answering a question nobody asked.

Resubmitting a page Google already fetched and declined asks it to make the same decision
again on the same evidence. It usually makes the same decision. Google's documentation for
that exact status says so without hedging: “no need to resubmit this URL for crawling.”

What actually moves a page from crawled to indexed is giving Google a reason it did not
have the first time:

- The page says something none of your other pages say. Two pages covering one topic
  usually means one of them gets kept and the other becomes “duplicate without
  user-selected canonical”.
- The page is reachable from somewhere that matters. A page whose only inbound link is the
  sitemap is a page nothing on your site vouches for.
- The page answers a question someone actually types, in the words they type. Thin does not
  mean short; it means it did not add anything. Google's own guidance for AI features uses
  the sharper version of this: a first-hand review “provides a unique perspective based on
  personal experience, whereas a summary of existing content simply restates information
  already available elsewhere”.

## The one thing to take away

Before you fix anything, find out which event stopped. Discovery, crawl, and index each
have their own failure and their own remedy, and the three remedies have almost nothing in
common. Technical work fixes the first two. Only better content fixes the third, and no
amount of resubmitting will substitute for it.

## Frequently asked questions

:::faq
### Should I click “Request indexing” again?
Not for a page at “crawled - currently not indexed”. Google's page indexing documentation
says there is no need to resubmit that URL, and its guidance on recrawling is to ask only
when there is an important change Google has not noticed for a week or more. A resubmission
does not add evidence, and the decision was about the evidence.

### How long does “crawled - currently not indexed” last?
There is no stated timeframe, and that is not evasion on Google's part: the status means
“may or may not be indexed in the future”. Treat it as a standing verdict rather than a
queue position. If nothing about the page changes, nothing about the answer is likely to.

### Is crawl budget my problem?
Almost certainly not, unless you run more than a million pages that change weekly or more
than ten thousand that change daily. Those are the thresholds Google puts at the top of its
own crawl budget guide, and it says outright that smaller sites do not need to read it.

### Will a sitemap get a page indexed?
No. A sitemap helps with discovery, which is the first event. It says nothing about whether
the page is worth keeping, and a page whose only inbound link is the sitemap has nothing on
your own site vouching for it.

### Does adding structured data help a page get indexed?
No. Structured data describes a page that is already being kept; it is not an argument for
keeping it. Google's guidance on optimizing for generative AI is blunt about the wider
version of this: you do not need to create new machine-readable files, AI text files,
markup, or Markdown to appear in Google Search.
:::

## Sources

- [Page indexing report](https://support.google.com/webmasters/answer/7440203) — Search Console Help, for every status string quoted above
- [In-depth guide to how Google Search works](https://developers.google.com/search/docs/fundamentals/how-search-works) — the three stages, and “indexing isn't guaranteed”
- [Large site owner's guide to managing your crawl budget](https://developers.google.com/search/docs/crawling-indexing/large-site-managing-crawl-budget) — crawl capacity limit, crawl demand, and the site-size thresholds
- [Google's guide to optimizing for generative AI features](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) — first-hand perspective versus restated content