The fastest way to check when Google last crawled a page is the URL Inspection tool in Google Search Console: paste the exact URL, run the inspection, and read the “Last crawl” timestamp under Coverage. For site-wide crawl behaviour use Settings → Crawl Stats; for ground-truth proof of every Googlebot hit, read your server logs. Each answers a slightly different question, and knowing which to reach for is the difference between a guess and a fact.
Last Crawl Date
The last crawl date is the most recent timestamp at which Googlebot fetched a specific URL, recorded by Google and surfaced in Search Console’s URL Inspection tool as the “Last crawl” field.
Why the crawl date matters
Crawl date is the first checkpoint in a chain that ends with ranking: Google can only index what it has crawled, and only rank what it has indexed. When you ship a content change, fix a canonical, or add structured data, none of it counts until Googlebot re-fetches the URL — the crawl date tells you whether your edit is live in Google’s eyes or still in a queue.
It also diagnoses the indexing failures we see most in audits. A page stuck on “Discovered – currently not indexed” with no crawl date was found but never fetched — usually a crawl budget or internal-linking problem. A page crawled yesterday but still excluded points instead at a canonical, robots, or quality signal.
One caveat up front: Google retired the public cache (
cache:operator and the “Cached” link in SERPs) in 2024. If a guide tells you to check the cached date, it is out of date. The methods below are the ones that still work.
Method 1 — URL Inspection (single URL, authoritative)
This is the canonical answer for one page on a property you own. Open Search Console, paste the exact URL — full protocol, exact casing, trailing slash if the page uses one — into the inspection bar, and run it. Expand the Coverage section: the “Last crawl” line is when Googlebot last fetched that URL.
While you’re there, read the surrounding signals: indexing status, the Google-selected canonical, the crawled-as user agent (smartphone Googlebot for most sites), and any structured data findings from that crawl.
Live Test vs. last crawl — the most misread part of this tool. The “Last crawl” date reflects the indexed fetch. Clicking Test Live URL fetches the page right now and shows current crawlability and rendering, but it does not update the last-crawl date or push anything to the index. Use Live Test to confirm Googlebot can reach the final content; use “Last crawl” to know what’s actually in Google’s index.
Method 2 — Crawl Stats (site-wide patterns)
When the question is “how is Google crawling my site,” not a single URL, go to Settings → Crawl stats. The report shows the last 90 days of total crawl requests and their daily trend, average Googlebot response time, a breakdown by response code (200s, 301s, 404s, the dreaded 5xx spikes), and splits by file type, purpose (refresh vs. discovery), and Googlebot type.
This is where you catch a server choking Googlebot, crawls wasted on parameter URLs, or a drop in crawl demand. It gives you no per-URL dates — it gives you the behaviour pattern that explains why a page’s crawl date is fresh or stale. Pair it with how web crawlers work to read the curve.
Method 3 — Server logs (ground truth)
Search Console reports what Google chooses to show you. Server logs record every request Googlebot actually made — real timestamp, exact path, status code, user agent. This is the only method that gives you forensic, per-URL, per-hit history at scale. A minimal log line for a verified Googlebot fetch:
66.249.66.1 - - [21/Jun/2026:14:32:08 +0000] "GET /pricing/ HTTP/1.1" 200 18243 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"Two non-negotiables: verify the bot — the user-agent string is trivially spoofable, so confirm real Googlebot with a reverse-then-forward DNS lookup (it must resolve to googlebot.com or google.com) or match Google’s published IP ranges — and filter to the verified set before drawing any conclusion about crawl frequency or depth.
For sites large enough to have a crawl-budget question at all, log analysis turns “Googlebot seems slow” into a quantified list of wasted requests — core to how we run programmatic SEO at scale, where one template bug can burn a six-figure crawl budget on junk URLs.
Which method should you use?
| You want to know… | Use | Authority | Scale |
|---|---|---|---|
| When one specific URL was last crawled | URL Inspection | High (Google’s record) | Single URL |
| Whether Google can fetch a page right now | Live Test (URL Inspection) | High (real-time) | Single URL |
| Site-wide crawl rate, response codes, demand | Crawl Stats | Medium (aggregated) | Whole property |
| Every Googlebot hit, with real timestamps | Server logs | Highest (ground truth) | Whole site |
| A rough public signal without GSC access | site: + sorting / third-party tools | Low (indirect) | Limited |
In practice: URL Inspection for the one-off “did my fix get crawled,” Crawl Stats for the weekly health glance, server logs whenever a crawl problem is big enough to justify the dig.
Method 4 — without Search Console access
If you don’t own the property, you only have weaker proxies. The cache: operator is dead, so your options are the site:domain.com operator to confirm what’s indexed (presence, not a date), third-party crawlers like Ahrefs or Semrush reporting their own last-seen date, and the page’s modified date — which tells you about the CMS, not Google. None are authoritative. The honest answer to “when did Google last crawl this page I don’t control” is: you can estimate, you can’t confirm.
Reading the date correctly
The timestamp is only useful if you read it right:
- Stale date ≠ broken page. Google crawls high-value pages often and stable evergreen pages rarely. A months-old date on a static “about” page is normal; the same date on a daily-updated pricing page is a red flag.
- Fresh crawl ≠ indexed change. Crawling, rendering, and indexing are separate stages. A new crawl date means Google fetched the update; processing still takes time, and a meta robots or X-Robots signal can block indexing entirely.
- AI Overviews don’t change the mechanism. Crawl → render → index still feeds both classic rankings and AI Overviews. There is no separate “AI crawl date” in 2026 — the same Googlebot fetch underpins both.
How to force a fresh crawl
Checking the date usually leads to “and now I need it crawled sooner.” Your levers, in order of leverage:
- Request Indexing in URL Inspection — fine for one or two high-priority URLs after a fix. Rate-limited per property; it’s a request, not a command.
- Submit or resubmit an XML sitemap — the right tool for batches. Keep
<lastmod>honest; Google uses it as a recrawl hint. - Strengthen internal links — the most durable lever. Well-linked pages get crawled more often, full stop, which is why we treat it as a crawlability problem, not a UX nicety.
- Genuinely update the content — a real change to a page that already earns crawls triggers a recrawl when you refresh and update content.
If recrawls are chronically slow site-wide, that’s structural — exactly what our growth program fixes, not something you patch one Request-Indexing click at a time.
Frequently Asked Questions
How do I check when Google last crawled a specific page?
Open Google Search Console, paste the exact URL into the URL Inspection tool, and run it. Expand the Coverage section and read the “Last crawl” line — that timestamp is the most recent time Googlebot fetched the URL. It’s the authoritative answer for any page on a property you own.
Can I still use the Google cache to see the last crawl date?
No. Google retired the public cache in 2024 — the cache: operator and the “Cached” SERP link no longer work, so older guides recommending them are out of date. Use URL Inspection for the crawl date, or server logs for a complete, verifiable history of every Googlebot fetch.
What’s the difference between “Last crawl” and a Live Test in URL Inspection?
“Last crawl” shows the fetch that informs Google’s current index — what Google actually has stored. Live Test fetches the page in real time to confirm crawlability and rendering now, but it does not update the crawl date or push to the index. Use Live Test to verify access; Last crawl to know what’s indexed.
Why hasn’t Google crawled my page in months?
Google allocates crawl attention by value and freshness, so stable pages are crawled rarely by design. If an important or frequently-updated page is stale, the usual causes are weak internal links, crawl-budget waste on low-value URLs, or slow server responses. Check Crawl Stats and internal linking first.
How can I check the crawl date for a site I don’t own?
You can’t confirm it. With the public cache gone and no Search Console access, you’re limited to proxies: site: to confirm indexing, third-party tools reporting their own last-seen date, or the page’s modified date. These estimate, they don’t verify — a real crawl date needs Search Console access.