How long does it take to get indexed, and when to stop waiting

How long does it take to get indexed is four questions wearing one coat, and only one of them has a published answer. Google states that crawling can take a few days to a few weeks and that requesting it guarantees nothing. Indexing, ranking and citation have no published window at all. This chapter gives you a way to tell which stage you are stuck at and when to stop waiting.

Read this first

This is an L3 chapter, which means it is about boundaries and when to quit rather than about doing the thing. The doing is in get your page indexed faster, and the fourteen-day review that tells you whether a change worked is in did it work.

You need Search Console access for most of what follows. Without it you can still observe crawling in your server logs, but you cannot see indexing state, and the stop-loss table below assumes you can.

How long does it take to get indexed: the only published number

Google's documentation on requesting a recrawl says: "Crawling can take anywhere from a few days to a few weeks." The same page adds that "requesting a crawl does not guarantee that inclusion in search results will happen instantly or even at all."

Read the second sentence twice. It separates two things that get conflated constantly — being fetched and being included. A page can be crawled promptly, repeatedly, and never enter the index, and nothing in that sequence is broken.

Notice also what the range covers. It is a statement about crawling only, and it is a range wide enough that almost no observation could contradict it. That is not evasion on Google's part; it reflects that fetch scheduling depends on the site, and a single number would be wrong for most of them. It does mean the sentence cannot be used to judge whether your own page is late.

Four stages, four different clocks

These do not happen on one timeline. They are separate events with separate evidence, and confusing them is why people conclude a change failed while it is still in progress.

Each stage is a gate for the next one, so the diagnosis is always the earliest stage that has not happened. Chasing rankings on a page that is not indexed is the most common wasted week in this whole discipline.

What to check at each stage

One check per stage, chosen so that a negative result is unambiguous rather than merely discouraging.

1. Crawled. Grep your access log for the URL and a known bot user agent, then confirm the request IP falls inside that vendor's published range. A user agent alone proves nothing.
2. Indexed. Run URL Inspection in Search Console. It reports the state directly. Do not use a site: search — sampling makes the result unreliable, and an absent result there is not evidence of anything.
3. Ranking. Look for impressions, not position. A page with zero impressions over a fortnight is not ranking badly; it is not competing at all, which is a different problem.
4. Cited. Run a fixed set of prompts on a fixed schedule and record whether the page appears. This is manual, and the manual method is in the share-of-voice chapter.

Crawled but not indexed is the stall worth knowing

Of the four stages, this is the one that traps people longest, because every signal says progress is happening. The logs show fetches. Search Console shows the URL as known. And the page never becomes eligible to appear.

The reason it stalls is that indexing is a judgement, not a queue position. Google decides whether the page adds something to what it already holds. So the fix is never to submit again — it is to make the page distinguishable from whatever the index already contains, which usually means it is near-duplicate of another page of yours, or thin enough that no claim on it is unique.

Practical test: take the page's central claim and search it in quotes. If your own site returns three pages making it, you have found the duplication. That is a merge decision, not a waiting decision.

What actually shortens the first stage

Discovery is the only stage you can influence directly, and there are exactly three levers. All three are one-time setup rather than ongoing effort.

1. Get the URL into your sitemap, and make sure the sitemap is referenced from robots.txt. A URL nothing points at is found last.
2. Link to it from a page that already gets crawled often. Orphan pages sit undiscovered for as long as nothing references them.
3. Notify the engines that accept notifications. That is what IndexNow does, and it removes the waiting-to-be-found step for participating engines.

Nothing on that list touches the second stage. Once a page has been fetched, discovery levers stop applying, and pulling them harder is the single most common misdirected effort in this whole sequence.

The stop-loss table

This is the deliverable. It states when to conclude that waiting longer will not change the answer, so that a stalled page gets diagnosed instead of hoped over.

The first four rows use 14 and 28 days because those match Search Console's own reporting granularity and give you a full comparison window, not because we measured those thresholds. They are decision deadlines, chosen so you act on a schedule instead of waiting indefinitely.

Why the last row has no number

Nobody publishes how often AI answer engines re-evaluate sources, and the answer they give varies between identical prompts. So there is no defensible deadline for "this page should have been cited by now" and we are not going to make one up to complete the table.

What you can do instead is compare. Run the same prompt set against a page you know is cited and one you suspect is not, on the same day. That controls for the engine's own variability, which is the part you cannot measure directly.

Three ways this goes wrong

All three come from treating a judgement as a queue — from assuming that if nothing has happened yet, the answer is to wait harder or ask again.

1. Using site: as an indexing check. It samples, it varies between runs, and a page missing from those results may be perfectly well indexed. URL Inspection is the only direct answer.
2. Resubmitting the same URL every few days. Google says requesting a crawl does not speed inclusion, and repeated submission mostly buys you the feeling of having done something.
3. Judging a change at day three. Every deadline in the table above is measured in weeks, and a fortnight of impatience has caused more unnecessary rewrites than any algorithm update.

What we have not measured

We have no first-party numbers for any of these windows. The experiment that would produce them — taking a new site from first deploy to first citation with every timestamp recorded — is planned and has not run, because it needs a site that launched recently enough to instrument from day one.

So treat everything here as a decision framework rather than as data. The stages are real and the evidence sources are real. The day counts are deadlines we chose, and when we do have measurements they may well move.

We also cannot tell you whether pushing harder helps. IndexNow shortens discovery for participating engines by notifying them directly rather than waiting for a crawl — that mechanism is documented and covered in IndexNow setup — but by how much, on your site, is exactly the thing nobody has published a controlled measurement of.

Keeping this diagnosis running across a whole site, so a stalled page surfaces on its own rather than when you happen to look, is what QueryWin is being built to do.

Common questions

How long does it take to get indexed after publishing?

Google publishes a range for crawling — a few days to a few weeks — and no figure at all for indexing, because inclusion is a decision rather than a queue. A page can be crawled within hours and still not be included.

Does requesting indexing make it faster?

Google's own wording is that it does not guarantee inclusion instantly or at all. It puts the URL forward; it does not move it up a line.

My page was indexed and then disappeared. What happened?

Indexing is not permanent. Pages get dropped, most often for duplication or thin content, and URL Inspection will usually say which. That is a content diagnosis, not a timing one.

Is a new site slower than an established one?

It is widely believed and not something we have measured. What is observable is that a new site has fewer internal links and no crawl history, both of which affect discovery — and discovery is the one stage you can fix directly.

When should I give up on a page entirely?

When it has been indexed for a month with no impressions. That combination says the page is eligible and nothing you targeted is being searched, and no amount of further waiting changes a keyword problem.