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, open the Page indexing section and read the “Last crawl” timestamp. To see when Google last crawled your website as a whole, use Settings → Crawl stats, which charts every Googlebot request over about the last 90 days and lists example URLs with their crawl times. For proof of every single Googlebot hit, read your server logs. And if Bing sends you traffic, its Webmaster Tools has its own URL Inspection with Bingbot’s last crawl. 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.
What “last crawled” means
“Last crawled” means the last time a search engine’s bot requested the URL from your server and got a response. It says nothing about rankings, and it is a different event from indexing: Google can fetch a page today and still leave it out of the index.
Google’s own definition of the Search Console field is “the last time this page was crawled by Google, in your local time”, and the rest of the inspection result (indexing status, canonical, structured data) is derived from that crawled version. So the time shown is the moment of that fetch, converted to your time zone. Two practical limits apply. The report can trail reality, so your server logs may show a later Googlebot hit that Search Console has not reported yet. And if the field reads N/A, Google knows the URL exists but has never fetched it, which is what “Discovered - currently not indexed” usually looks like.
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 and never fetched, usually a crawl budget or internal-linking problem. A page crawled yesterday and still excluded points at a canonical, robots or quality signal instead.
One caveat up front: Google retired its public cache in 2024. The “Cached” link left the results pages early that year, and the
cache:operator stopped working in September 2024. If a guide tells you to check the cached date to see when Google last saw a page, 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 at the top, and run it. The top line tells you whether the URL is on Google. Expand Page indexing: the “Last crawl” line is when Googlebot last fetched that URL.
While you’re there, read the surrounding fields: Crawled as (smartphone Googlebot for most sites), Crawl allowed?, Page fetch, Indexing allowed?, the Google-selected canonical, and any structured data findings from that crawl. If “Crawl allowed?” says no, your robots.txt is blocking the page; the free robots.txt generator builds a clean file you can compare against yours.
Live Test vs. last crawl is the most misread part of this tool. The “Last crawl” date and everything under it describe the version Google has indexed. Clicking Test Live URL fetches the page right now and shows current crawlability and rendering. The live test leaves the last-crawl date and the index as they were, so use it to confirm Googlebot can reach the final content and use “Last crawl” to know what Google actually has.
To see which resources Googlebot loaded (scripts, stylesheets, images) and whether any failed, click View crawled page for the indexed version or View tested page for a live test, then open More info. The page resources list there is the fastest way to catch a blocked script that breaks rendering.
Method 2: Crawl stats (when Google last crawled your site)
When the question is “when was my website last crawled” or “how is Google crawling my site”, go to Settings → Crawl stats → Open report. It is available for root-level properties only: a Domain property or a URL-prefix property at the root, such as https://example.com/. The report shows total crawl requests and their daily trend, average response time, host status, and breakdowns by response code (200s, 301s, 404s, the dreaded 5xx spikes), file type, purpose (refresh or discovery) and Googlebot type.
Click any row and you get a list of example URLs, each with its crawl time, response code and size. Google calls that list an example selection, so read it as a sample of recent crawls. For the full per-URL history you need logs.
This is where you catch a server choking Googlebot, crawls wasted on parameter URLs, or a drop in crawl demand: the behavior 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, any date range)
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 for any date range you keep logs for. A minimal log line for a 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)"To find when Google last crawled one URL, filter the log for that path and the Googlebot user agent and read the last line; to check a date range, filter on the timestamp too. Two non-negotiables before drawing any conclusion: verify the bot (the user-agent string is trivially spoofable, so confirm real Googlebot with a reverse-then-forward DNS lookup that must resolve to googlebot.com or google.com, or match Google’s published IP ranges) and filter to the verified set.
Google Analytics will not help here. It counts visitors whose browsers run its tracking script and excludes known bots, so crawlers like Googlebot and Bingbot never show up in it. To see what crawled your site, use logs or each engine’s own webmaster tools.
On sites large enough to have a crawl-budget question at all, log analysis turns “Googlebot seems slow” into a quantified list of wasted requests. Our guide to crawling and indexing controls covers the robots rules, sitemaps and canonicals that redirect that waste.
Method 4: Check when Bing last crawled the page
Bing runs its own crawler on its own schedule, so a fresh Google date tells you nothing about Bing. In Bing Webmaster Tools, open URL Inspection, paste the URL, and read the index details: they cover when the URL was discovered, when Bingbot last crawled it and whether it is indexed, plus the HTTP response Bingbot received. A live URL test is there too. Bing’s index also feeds Copilot answers, which makes this check worth a minute of your time. Our guide to mastering Bing Webmaster Tools and IndexNow walks through the setup.
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 |
| When Google last crawled the site, response codes, demand | Crawl stats | Medium (aggregated, sampled URLs) | Whole property |
| Every Googlebot hit in a date range, with real timestamps | Server logs | Highest (ground truth) | Whole site |
| When Bing last crawled a URL | Bing Webmaster Tools URL Inspection | High (Bing’s record) | Single URL |
| A rough public signal without GSC access | site: search, 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, and Bing’s inspection whenever Bing is part of your traffic.
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 a page is indexed (it shows no date), third-party crawlers like Ahrefs or Semrush reporting the date their own bot last saw the page, and the page’s modified date, which describes the CMS and says nothing about Google. None of them is 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:
- A stale date can be perfectly normal. Google crawls high-value pages often and stable evergreen pages rarely, so some pages crawled yesterday and others last crawled a month ago is an ordinary pattern. A months-old date on a static “about” page is fine; the same date on a daily-updated pricing page is a red flag.
- A fresh crawl is only the first step. 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.
- Crawl date and publish date are separate facts. The crawl date records when Google fetched the page. When the page was first published lives in the page itself or its
datePublishedmarkup, and a recent crawl of an old page is common. - AI Overviews run on the same crawl. Crawl, render and index still feed both classic rankings and AI Overviews. There is no separate “AI crawl date”; 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. Google sets a daily limit per property, and a request carries no promise of when Google will recrawl.
- Submit or resubmit an XML sitemap: the right tool for batches. Keep
<lastmod>honest; Google uses it as a recrawl hint only when it proves accurate. - Strengthen internal links: the most durable lever. Well-linked pages get crawled more often, full stop, which is why we file it under crawlability along with robots rules and server health.
- Genuinely update the content: a real change to a page that already earns crawls triggers a recrawl when you refresh and update content.
- For Bing, ping IndexNow: Bing and several other engines accept IndexNow pings and usually fetch the URL soon after. Google does not use IndexNow.
When stale crawl dates become a business problem
One old date is a non-event. It becomes a problem when it is a pattern: hundreds of templated pages last crawled months ago, a growing pile in “Discovered” or “Crawled - currently not indexed”, or crawl requests that fall after a migration and stay down. If your site has a few hundred pages and the important ones were crawled this quarter, keep checking them yourself; you don’t need us. On large and programmatic sites we find where the crawl goes in the logs, cut the URLs that waste it, and rebuild the internal links and sitemaps that point both bots at the pages that earn money. That work is part of our programmatic SEO service. On Prawomat’s launch, 1,125 pages earned four times more clicks from Bing than from Google in the first six months, which is why we check both engines.
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 Page indexing 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.
How do I find when Google last crawled my whole website?
Open Settings, then Crawl stats, in Search Console. The chart shows Googlebot’s requests day by day over about the last 90 days, so the latest bar with requests is the last time Google crawled the site, and clicking a row lists example URLs with their crawl times. For a complete record, filter your server logs for verified Googlebot.
Does the “Last crawl” time mean Google crawled the page at that exact moment?
Yes. It is the time of the fetch Google used for the inspection result, shown in your local time. The report can lag, so your server logs may already show a newer Googlebot visit, and running a live test does not change the date.
How can I tell if Google has crawled a link at all?
Inspect the URL. If “Last crawl” shows a date, Googlebot has fetched it. If it shows N/A, or the status reads “Discovered - currently not indexed”, Google knows the URL and has not fetched it yet. Server logs give the same answer for any URL on your site, including ones you have never inspected.
Can I still use the Google cache to see the last crawl date?
No. Google retired the public cache in 2024. The “Cached” link left the results early that year and the cache: operator stopped working in September 2024, 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” describes the fetch behind Google’s current index: what Google actually has stored. Live Test fetches the page in real time to confirm crawlability and rendering now, and it leaves the crawl date and the index untouched. Use Live Test to verify access and 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 do I check when Bing last crawled my page?
Use URL Inspection in Bing Webmaster Tools. It shows when Bingbot discovered and last crawled the URL and whether it is in Bing’s index. Bing crawls on its own schedule, so its date often differs from Google’s.
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. All of them are estimates; a verified crawl date needs Search Console access.