How to force Google to recrawl a page after you update it

You updated a page. The title changed, the content changed, the meta description changed. You check Google a week later — same old title in the results. Frustrating, because Google's recrawl cadence for any given URL is opaque and often slow.

The fastest path to a forced recrawl

1. Sign in to Search Console with the account that owns the property.
2. Open URL Inspection for the URL. Note the "Last crawl" timestamp.
3. Click "Request indexing." This queues your URL for a fresh crawl (one URL at a time, rate-limited).
4. For batch updates, push the URLs through the Indexing API instead — same effect, no click-fest.
5. Wait. Most recrawls happen within hours; some take 1-3 days.
6. Re-check URL Inspection. New "Last crawl" timestamp = Google fetched the new content.

When the standard path doesn't work

Sometimes Search Console's Request indexing button silently fails — the queue is full, the URL recently got a request, or Google's quota is exhausted. Symptoms: 24 hours later, no new crawl timestamp, no error message. The Indexing API is more reliable here because the response tells you immediately whether Google accepted the hint.

What if the page is in cache but the cached version is wrong

Google caches your page in two places: the search index (what shows in results) and the rendered DOM (what the URL Inspection "Live test" returns). A successful recrawl updates both. If you see new content in Live test but old content in regular Search results, you're between a recrawl (done) and reindex (not yet done). Wait 24-48 hours, then re-push if still stale.

Diagnostic: is Google ignoring my recrawl request?

Run URL Inspection again 48 hours after pushing. Look at:

• Last crawl timestamp — if it's still the pre-update date, the recrawl didn't happen yet.
• Coverage state — if it flips from "Indexed" to "Discovered - currently not indexed," the new version got demoted.
• Indexed verdict — if it shows "FAIL" or "PARTIAL" where it used to show "PASS," something on the new version broke indexability (canonical change, noindex, etc).

Things that prevent recrawl from working

• robots.txt blocks the path (URL Inspection will say so).
• <meta name="robots" content="noindex"> on the new version.
• Canonical tag pointing elsewhere — Google recrawls but indexes the canonical, not this URL.
• Server returning 5xx or 4xx on Googlebot's IP range — check server logs.
• Page is JavaScript-heavy and the new content needs render — Google's render queue is much slower than the crawl queue.

Bulk recrawl for redesigns and migrations

If you've updated 100+ pages at once (template change, migration, content refresh), Search Console's one-URL-at-a-time button is brutal. The Indexing API handles batches of 50 in seconds. IndexerNow wraps that with sitemap-based selection, batch history, and a 24h recheck that re-inspects every URL and emails you the indexed/pending split.