Google Search Console’s “last crawled” timestamp feels definitive. You publish a post, check the index status, and see a date. But that date doesn’t mean what most operators think it means—and misreading it costs you diagnostic time when traffic doesn’t arrive.
Here’s what the timestamp actually represents, how indexing lag works behind the scenes, and what to check when Google says it crawled your page but you’re still not ranking.
What “last crawled” measures
The “last crawled” field in Search Console’s URL Inspection tool shows the most recent time Googlebot fetched your page. That’s it. It doesn’t confirm:
- That the page was indexed
- That the content was understood or valued
- That the page is eligible to rank
- That internal links were followed
Google crawls millions of pages it never indexes. A crawl is a request; indexing is a decision that happens after parsing, quality filtering, and duplicate detection. The timestamp only proves the bot showed up.
If you see “Crawled – currently not indexed,” the date tells you Google looked at the page and chose not to include it. If you see “Discovered – currently not indexed,” Google found a reference to the URL but hasn’t fetched it yet. Both statuses can persist for weeks, even on sites with healthy crawl budgets.
Why the lag exists
Indexing happens in stages. Googlebot crawls, sends the HTML to processing infrastructure, runs quality checks, compares the content to existing indexed URLs, decides whether to include it, then updates the index. Each stage introduces delay.
For established sites publishing fresh content, indexing usually completes within hours. For newer domains, low-authority pages, or content flagged as thin or duplicate, the gap stretches to days or weeks. Google doesn’t publish service-level agreements for indexing speed—there’s no guarantee.
Search Console’s own interface updates on a lag, too. The “last crawled” date can be 24–48 hours behind actual crawl logs. If you requested indexing via the inspection tool this morning, don’t expect the timestamp to update until tomorrow at the earliest.
What to check when crawl dates look current but traffic doesn’t
Start with the “Coverage” report in Search Console. Filter by “Excluded” and look for your missing URLs. Common exclusion reasons:
- Duplicate without user-selected canonical: Google chose a different URL as the canonical version, usually because of thin content or near-duplicate text across pages.
- Crawled – currently not indexed: The page was fetched but deemed too low-quality or low-value to include. Check word count, internal links pointing to the page, and whether the topic overlaps heavily with existing indexed content.
- Discovered – currently not indexed: Google knows the URL exists but hasn’t prioritised fetching it. This happens on sites with hundreds of pages and limited crawl budget, or when the page sits deep in the site structure with no external links.
Next, run a live URL inspection. Search Console shows you both the indexed version (what’s in Google’s index) and the live version (what Googlebot sees when it fetches the page right now). If the indexed version is weeks old and the live version shows current content, you’ve confirmed indexing lag—not a crawl problem.
Finally, check your server logs if you have access. Search Console only reports successful crawls. If Googlebot is hitting 404s, 500 errors, or timeouts, those won’t appear in the “last crawled” field at all. Log analysis tools like Screaming Frog Log File Analyser or GoAccess will show you the actual request pattern, including failed attempts.
When to request indexing manually
The URL Inspection tool includes a “Request indexing” button. Use it sparingly. Google allows roughly 10–12 requests per day per property. Burn through your quota on low-priority pages and you can’t prioritise genuinely time-sensitive content.
Request indexing when:
- You’ve published breaking news or time-sensitive content that needs to rank within hours
- You’ve fixed a critical error (like a noindex tag or broken canonical) and need Google to re-evaluate the page
- You’ve updated high-traffic content and the indexed version is stale
Don’t request indexing for every new post. If your site publishes daily and has healthy crawl frequency, Google will find new content via your sitemap and internal links within 24 hours anyway. Save the manual requests for exceptions.
The bottom line
“Last crawled” timestamps are diagnostic signals, not success metrics. A recent crawl date with no indexed status means Google looked and passed. An old crawl date on an indexed page means nothing changed, so Google didn’t prioritise a re-crawl.
If you’re tracking indexing speed across dozens of posts, export the Coverage report weekly and compare indexed-vs-excluded ratios over time. Patterns matter more than individual page delays.
Want more operator-focused breakdowns of the tools you already use? Subscribe to One Two Three Send for weekly deep-dives on email platforms, AI tools, hosting, and traffic—no fluff, just the mechanics that matter.