How long does Google take to index a page?

Hours on a site Google crawls constantly. Weeks on a site it visits rarely. Never, on a page it decides is not worth the space.

Anyone quoting you a single number is quoting an average across sites that have nothing to do with yours. The useful question is not “how long does it take” but “what decides how long it takes for me” — and that has real answers.

Three different questions

People arrive here asking one of three things and usually do not realise they are separate. The gap between them is where most of the confusion about timing lives.

The question	What has to happen	Typical shape of the answer
How long until Google crawls it?	Googlebot fetches the URL	Fast on a site crawled often; the queue is the whole delay
How long until Google indexes it?	It fetches, reads, and decides the page earns a place	Crawling plus a judgement that can go against you
How long until it ranks?	It is indexed, then competes	A different problem entirely — see below

Crawled is not indexed. Google can fetch a page today and still decline to store it, which is the status Crawled – currently not indexed describes. And indexed is not ranked: a page can be perfectly indexed and appear on nobody’s first page.

Most of this guide is about the middle row, because that is where the time actually goes.

What actually decides it

How often Google already crawls your site. This is most of the answer. A site that publishes daily and gets crawled hourly has new pages picked up almost immediately. A site that publishes twice a year is visited about as often.

Whether anything links to the new page. A page linked from your homepage, or from an article that already ranks, is on a path Google walks regularly. A page reachable only through a sitemap is on a list, not a path.

How much competition the page has in the index. A genuinely new answer gets indexed faster than the four hundredth article on a topic Google already has covered. This is the same judgement behind Crawled – currently not indexed, just earlier in the process.

Server health. Slow responses and intermittent 5xx make Googlebot back off, which stretches everything. See Discovered – currently not indexed for what to look at.

A brand-new site is a different question

Every answer above assumes Google already crawls your site. On a domain registered last week it does not, and nothing about the first few pages is representative of what the site will be like later.

There is no crawl history, so there is no rhythm to slot into. Google has to discover the site at all, then decide how much of it to fetch, with no record of whether previous pages were worth the trouble. Expect the first pages to take substantially longer than pages published on the same site six months from now, and expect the wait to be uneven — one page in a week, three more a month later, some not at all.

Two things genuinely help at this stage, and they are not the ones usually recommended:

• A link from a site Google already crawls. This is how discovery actually happens. One real link from an established site does more than a perfect sitemap, because a sitemap is a list and a link is a path.
• Verify the property in Search Console and submit the sitemap. Not because it makes Google hurry — it does not — but because it is how you find out what is happening instead of guessing.

The disappointing part: for a new domain with no links pointing at it, there is no lever that reliably compresses this into days. Waiting is most of the work, and the sites that appear to have skipped the wait almost always had links from somewhere.

What genuinely speeds it up

• Link to the new page from a page that already gets crawled often. The most reliable lever, and the most ignored one.
• Keep the sitemap accurate and current. It will not make Google hurry, but a sitemap full of 404s and redirects makes it trust the file less.
• Request indexing — once. It is a legitimate nudge for a genuinely new or substantially updated page. Once. It is not a lever you pull harder.
• Publish consistently. Crawl frequency is earned over months, not bought. This is the one that changes the baseline for every future page.

What does not

• Requesting indexing repeatedly. The quota is small, and re-queueing a queued URL achieves nothing.
• Indexing services and pingers. They either do nothing or attach your site to a link network you cannot inspect.
• Republishing with a new date. Google compares against what it stored. A changed timestamp on unchanged content is not new information.
• Social shares. They can lead to links, and links help. The share itself does not.

Recrawling, and how often Google comes back

First-time indexing and recrawling are different clocks, and the second one is the one people ask about when a page already exists.

There is no schedule. Google recrawls a URL roughly in proportion to how often it changes and how much it matters — a homepage that updates daily gets revisited constantly, an archive page that has not changed in two years may go months. That is why “how often does Google index my pages” has no single answer even within one site: two URLs on the same domain can be on completely different cycles.

When you change an existing page, the sequence is recrawl, then re-evaluate, then update the stored copy. Each step can pass without the next one following. A page can be recrawled and have its stored version left alone, because Google compared the new copy with the old one and decided nothing material changed — which is exactly what happens when the only edit was a new publish date.

If a change genuinely matters — a rewritten page, a fixed noindex, a corrected canonical — request indexing once and then leave it. The edit being substantial is what shortens the wait, not the request.

Search Console adds its own delay

This is the part that wastes the most time, because it makes indexing look slower than it is.

The Page indexing report is not a live view. It is built from data that lags, and it can be days behind what Google actually knows. A page reported as not indexed on Tuesday may have been indexed since Sunday. People re-request indexing, rewrite the page, and start debugging a problem that was fixed before they opened the report.

URL Inspection answers two different questions and it is easy to read the wrong one. The default result describes the indexed version — what Google has stored, which may be old. “Test live URL” fetches the page as it is right now. A page you fixed this morning will keep showing the old problem in the default view until Google recrawls it, and that is not a sign the fix failed.

So before concluding that indexing is taking too long, check whether you are looking at Google’s current state or at a report describing last week’s. The faster read is to ask the index directly rather than to ask Search Console what it recorded — how to check if a page is indexed covers the ways to do that and which of them are trustworthy.

Measure it for your own site

Averages from someone else’s site are entertainment. Your own number is a measurement, and it is not difficult to take:

1. Take the URLs you published in the last month or two.
2. Check the whole list at once and record what is indexed today.
3. Re-check the same list on a schedule — weekly is plenty.
4. The date each URL flips from not indexed to indexed is your real time-to-index.

After a couple of months you know your own distribution instead of an internet average: how long the median page takes, which sections of the site are slower, and whether the changes you made moved anything.

That number is worth more than any benchmark, because it is the only one that accounts for your domain, your linking, and your content.

Step 2 takes about a minute with our free index checker — ten URLs, no account — and that is your first data point. Steps 3 and 4 are the part worth automating: indexaction re-checks a saved list on a weekly schedule and compares each run against the last, so the date a URL flipped is recorded rather than remembered.

Indexed is not ranked

If the real question is “how long until this page brings me traffic”, indexing is only the first gate, and it is the easy one.

Being indexed means Google has stored the page and will show it when it is the best answer it has. On a competitive query it may never be. There is no waiting period after which an indexed page starts ranking — it is not a queue, and time served counts for nothing on its own.

What does change over time is everything around the page: links pointing at it, the site’s track record on the topic, and how the page performs for the people who do find it. Those move slowly and they are the actual work. A page that has been indexed for six months and ranks nowhere is not waiting its turn.

The useful thing to separate: if the page is not indexed, the rest of this guide applies. If it is indexed and gets no traffic, timing was never the problem and no amount of it will be the solution.

The uncomfortable part

Some pages never get indexed, and waiting longer does not change it.

If a page has been live for a couple of months on a site that is otherwise crawled normally, has internal links pointing at it, and is still not in the index, time is not the missing ingredient. That is Google having looked and declined, and the fix is on the page rather than on the calendar — which is a different guide.