← All posts

How Long Does Google Take to Recrawl a Page?

Google says a recrawl takes a few days to a few weeks. Here's how to read when it last came, what actually speeds it up, and why the recrawl is when an SEO change starts.

QueryScope team · · 7 min read · search console gsc crawling indexing

Google's own answer is "anywhere from a few days to a few weeks". On most sites a changed page that Google already knows is reread within days, and a page Google cares little about can wait well over a month. You can't set the date, but you can read it: URL Inspection shows the last time Googlebot fetched the page, so you know whether your change has been seen yet.

That date matters more than it looks. Until Google rereads the page, no searcher has seen your edit, so nothing in Search Console can reflect it. A change judged from deploy day is judged on days when it did not exist yet.

TL;DR:

  • Google says crawling "can take anywhere from a few days to a few weeks". On our own site, three changed pages were reread in two to three days, and one has waited 42 days.
  • URL Inspection's last crawl date is the only fact here. Anything else is a guess.
  • What helps: an accurate sitemap lastmod, a link from a page Google crawls often, and one indexing request. Asking again does not help.
  • A recrawl is not an index decision. Google can reread a page and still decline to keep it.

How long does a recrawl actually take?

Google's recrawl documentation gives the range and no more: "Crawling can take anywhere from a few days to a few weeks." The spread is wide because there is no queue you join. Google decides how often to come back to each URL.

Here is what that looked like on queryscope.dev, read from the change log QueryScope keeps for its own site on 2026-11-14:

  • /blog/crawled-currently-not-indexed: changed 2026-10-12, reread 2026-10-15. 3 days.
  • /blog/striking-distance-keywords: changed 2026-10-19, reread 2026-10-21. 2 days.
  • /semrush-alternative: changed 2026-11-10, reread 2026-11-12. 2 days.
  • /blog/anonymized-queries-search-console: changed 2026-10-03, not reread yet. 42 days and counting.

Same site, same sitemap, same week of edits. Three pages came back inside three days. The fourth was last crawled on 2026-09-19 and has not been fetched since, even after an indexing request on 2026-11-11. One small site is not a benchmark, but it shows the shape: most rereads are quick, and a slow one can run past a month.

Why does Google come back to some pages faster?

Google calls the deciding force crawl demand. Its crawl budget guide says that for Googlebot, "demand varies based on a site's size, update frequency, page quality, and relevance, compared to other sites", and names two drivers that matter at page level: "URLs that are more popular on the Internet tend to be crawled more often to keep them fresher in our systems", and "Our systems want to recrawl documents frequently enough to pick up any changes."

In practice that means:

  • Pages Google sees as important get reread first. Your homepage, pages with links pointing at them, and pages that earn clicks.
  • Pages that change often get checked more often. A page that has been the same for a year teaches Google it can wait.
  • Pages Google is lukewarm about wait longest. A page sitting in crawled, currently not indexed is one Google already read and declined to keep, so it has little reason to hurry back.

Crawl budget itself is rarely the limit on a normal site. Google's guide is written for "Large sites (1 million+ unique pages)" and "Medium or larger sites (10,000+ unique pages) with very rapidly changing content". On a few hundred pages, a slow recrawl is about demand for that page, not a site running out of budget.

Try it

Point an SEO agent at your own site, not just an essay about one.

QueryScope holds the plan for your site, reads your real Search Console, and hands the coding agent you already have one change at a time to rank for the searches you decided to win. From $49/month, everything included.

How do you check when Google last crawled a page?

Open URL Inspection in Search Console, paste the URL, and read the crawl section. The last crawl date there is the last time Googlebot fetched the page. If it is earlier than your deploy, Google has not seen the change. If it is later, it has.

Two things to keep apart:

  • The inspected result versus the live test. The default view is what Google last stored. The live test fetches the page now, which proves the page can be crawled but tells you nothing about when Google will come back on its own.
  • Crawled versus indexed. The same screen tells you whether the page is in the index. A fresh crawl date with "not indexed" beside it means Google read your change and still passed. That is a quality question, and recrawling again will not answer it. How to check if a page is indexed covers the difference.

The URL Inspection API returns the same field (lastCrawlTime), which is how you check many pages without opening each one.

What actually speeds up a recrawl?

Nothing forces it. A few things give Google a reason to come back sooner:

  • An accurate sitemap lastmod. Google says it uses the lastmod value when it is "consistently and verifiably (for example by comparing to the last modification of the page) accurate", and that it ignores priority and changefreq. Bump lastmod only when the page's own content, structured data or links changed. A lastmod that moves on every deploy teaches Google to ignore it on every page. The sitemap lastmod guide goes through what counts.
  • A link from a page Google crawls often. Googlebot finds pages by following links. A new link on a page Google rereads every few days puts your page in its path. Pick a page that is not in the middle of being measured itself.
  • One indexing request. URL Inspection's request indexing button is Google's own route for "just a few URLs". Google is plain about the limits: "there's a quota for submitting individual URLs", "requesting a recrawl multiple times for the same URL won't get it crawled any faster", and "Requesting a crawl does not guarantee that inclusion in search results will happen instantly or even at all."

What does not help: requesting the same URL every day, resubmitting the whole sitemap, or editing the page again to look fresh. That last one costs the most, because it resets the change you were waiting on.

Why the recrawl is when an SEO change starts

If you shipped a title change on Monday and Google rereads the page two weeks later, the first two weeks of data after the deploy are the old title. Judge the change from Monday and you average two weeks of nothing into the result.

So a change's clock starts at the recrawl, not the deploy. From there, the wait depends on what you changed: how long SEO changes take covers why a title settles faster than a rewritten page. The full method, logging each change against the search it was for and holding the page until the window closes, is on tracking SEO changes.

Waiting on Google without checking every day

Checking crawl dates by hand is the kind of chore that stops after a week. QueryScope reads the last crawl date for each changed page from the URL Inspection API, starts each change's clock on the day Google rereads the page, and lists the changed pages Google has not read in 14 days or more, with what to do about each. The four pages above came from that list. It reads your own Search Console and stops there: it cannot make Google crawl faster, and it says so.

Sources

  • Google Search Central, Ask Google to recrawl your URLs ("Crawling can take anywhere from a few days to a few weeks"; the quota on individual URL requests; repeat requests do not speed it up; a request does not guarantee indexing).
  • Google Search Central, Build and submit a sitemap (lastmod is used when it is consistently and verifiably accurate; priority and changefreq are ignored).
  • Google Search Central, Crawl budget management for large sites (crawl demand, popularity and staleness; the guide is aimed at sites of 10,000+ or 1 million+ pages).
  • QueryScope's change log for queryscope.dev, read 2026-11-14 (change dates and Google's reread dates for four pages).

Try it

Put an SEO agent in your editor.

Ask your coding agent what to work on. QueryScope reads your real Search Console, holds the searches you decided to win, and hands back one move at a time with the proof it worked. From $49/month, everything included. 1, 3 or 10 sites.