How to ask Google to recrawl a URL: the two documented methods, the quota, and what to do while you wait
Google documents exactly two ways to request a recrawl: URL Inspection for a handful of pages and a sitemap for many. Here is how each one works, how long it takes, and how to fix the reasons a changed page stays stale.
Published by AI Knows Us · Updated 12 October 2026
There are two documented ways to ask Google to recrawl a URL. For a handful of pages, use the URL Inspection tool in Search Console and click Request Indexing. For large numbers of URLs, submit or resubmit a sitemap. Google's own guidance, last updated 10 December 2025, lists only these two methods, states that you cannot request indexing for URLs you do not manage, and notes that crawling can take anywhere from a few days to a few weeks.
Two other things from that same page are worth knowing before you start. You must be an owner or full user of the Search Console property to request indexing through URL Inspection, there is a quota on individual URL submissions, and requesting a recrawl repeatedly for the same URL will not get it crawled any faster. Google also states that requesting a crawl does not make inclusion in search results instant or certain, because its systems prioritise fast inclusion of high quality, useful content.
Method one: URL Inspection, for a few pages
- Open Search Console and select the property that contains the URL.
- Paste the full URL into the inspection bar at the top. Use the exact canonical form, with the right protocol, host and trailing slash.
- Read the result first. If it reports the page as blocked, redirected, canonicalised elsewhere or returning an error, requesting indexing will not help until that is fixed.
- Click Test Live URL to confirm Google can fetch and render the current version, and compare the rendered HTML with what you expect to see.
- Click Request Indexing. The URL joins a priority crawl queue.
- Check back in a few days using the same tool, and watch the Pages report for the change in status.
Use it for the pages where speed genuinely matters: a corrected price, a fixed legal statement, a new landing page tied to a launch, a page you have just rewritten substantially. The daily quota is small by design, so spending it on every blog post you publish wastes the one mechanism you have for urgent cases.
Method two: sitemaps, for many pages
A sitemap is how Google discovers URLs at scale, and Google specifically recommends it when you have large numbers of URLs, have just launched a site, or have recently performed a site move. It is also the right tool for a bulk content update.
- Include only canonical, indexable URLs that return a 200 status. Redirects, noindex pages and parameter duplicates in a sitemap dilute the signal.
- Set a truthful lastmod date, and change it only when the content meaningfully changed. A file where every URL claims to have changed today teaches Google to ignore the field.
- Split large sites into several sitemaps under a sitemap index, grouped so you can see in the Sitemaps report which group is lagging.
- Resubmit the sitemap in Search Console after a bulk change, or simply ping the file so the crawler sees the new lastmod values.
- Keep the sitemap referenced in robots.txt so every crawler that reads it finds the file.
Which method, and what each one is for
| Situation | Use | Why |
|---|---|---|
| One urgent correction | URL Inspection, Request Indexing | Fastest documented route for a single URL |
| A rewritten page set of 200 URLs | Sitemap with updated lastmod | Built for volume, and the quota does not apply |
| A new site or a domain move | Sitemap, plus internal links from existing pages | Google names both cases as sitemap use cases |
| A page that will not get indexed at all | Neither; diagnose first | A request cannot override a technical block or a quality judgement |
| Job postings and livestream pages | The Indexing API | It is restricted to those two content types |
That last row is the one people reach for by mistake. What the Indexing API covers, and the job posting and livestream limit, are set out in the guide to the Google Indexing API. For Bing, the equivalents are URL submission and IndexNow, covered in how to index a site on Bing.
Why a changed page still shows the old version
Most recrawl requests are really a different problem wearing a recrawl costume. Work through these before you submit anything.
- The snippet is stale, not the index. Compare the live page with what URL Inspection reports as last crawled. If Google has the new version and the snippet is old, the snippet will catch up on its own.
- The page is canonicalised to another URL. URL Inspection names the Google selected canonical. If it is a different URL, your edits are being attributed elsewhere, and the fix is the canonical tag and internal links.
- The change is invisible to a crawler. If the new content loads from JavaScript after an interaction, run Test Live URL and read the rendered HTML. Content that only exists after a click is content Google has not seen.
- Nothing links to it. Google discovers URLs mainly through links on crawled pages. A page with no internal link into it is slow to be revisited whatever you submit.
- The page is blocked. A robots.txt disallow prevents the fetch, so nothing downstream can happen, including Google reading a noindex tag.
- It returns the wrong status. Soft 404s, redirect chains and 5xx responses during crawl all stall indexing quietly.
- The page is thin. Where Google's systems prioritise useful content, the fastest route to a recrawl that sticks is making the page worth indexing, then requesting it once.
How to make recrawls happen without asking
Sites that get crawled promptly share a few habits. Keep an accurate sitemap with honest lastmod values. Link new and updated pages from pages that are already crawled often, such as a hub page, a category index or the latest list. Keep response times low and error rates near zero, because a server that struggles gets fetched less. Avoid parameter and faceted URL explosions that consume requests on duplicates. Where requests are being spent on worthless URLs, fix that first; the patterns and the tooling are in crawl budget optimization.
Recrawl requests: what people ask when a page will not update
How long does a recrawl take after I request it?
Google says crawling can take anywhere from a few days to a few weeks, and recommends monitoring progress with the Index Status report or the URL Inspection tool rather than resubmitting.
Does requesting indexing multiple times speed it up?
No. Google states plainly that requesting a recrawl multiple times for the same URL will not get it crawled any faster, and repeat submissions consume your quota.
What is the daily limit on Request Indexing?
Google documents that a quota exists without publishing the figure, and the practical effect is that you get a small number of individual submissions per property per day. Treat it as a scarce resource for urgent pages and use sitemaps for everything else.
Can I request a recrawl for a site I do not own?
No. You must be an owner or full user of the Search Console property, and Google states that you cannot request indexing for URLs you do not manage.
Do third party instant indexing tools work?
The documented methods are the two above, and the Indexing API for job postings and livestreams. Anything offering instant indexing for ordinary pages on Google is either wrapping those same methods or doing nothing, so check which before you pay for it.
Should I request a recrawl after every content edit?
No. Save it for changes with a deadline or a commercial consequence. For routine edits, an accurate lastmod in your sitemap and a link from a frequently crawled page does the same job without spending quota.
The other queue, and nobody has a submit button for it
A recrawl request fixes one thing: Google's copy of your page. It does nothing about the description of your business that circulates on other people's sites, and that is what an AI assistant draws on when a buyer asks it for recommendations. Those answers lean on directories, review platforms, roundups and comparison pages, each with its own refresh habits, so a price you corrected on your own site this morning can keep being quoted wrongly for months through a listing you have forgotten about. There is no URL Inspection tool for that, which is why the work is to find the sources behind the answers and update them at source. AI Knows Us re runs those buying questions after a change ships, shows which sources each answer used, and tells you when the corrected version starts appearing instead. The free check at aiknowsus.com is the quickest way to see what is being repeated about you.