How to Request a Crawl or Recrawl of One URL in Google Search Console

If you have published or substantially updated one page, inspect that page’s exact URL in Google Search Console and request indexing if the option is available. The request asks Google to consider revisiting the URL. It does not make Google crawl it immediately, index it, or show it in search results. Indexely’s explanation of crawl requests puts the distinction plainly: a request is a hint, not a guarantee.

Choose the URL, not the whole site

URL Inspection is the focused option for an individual new or updated page. Suppose you revised https://example.com/guides/returns. Inspect that address—not just https://example.com/ and not a neighboring guide. A request for the homepage concerns the homepage; it does not ask Google to recrawl every page beneath it.

If you changed many URLs, keep your XML sitemap current instead. List the pages you want discovered and use accurate last-modified dates for pages that changed. A sitemap is useful for communicating a set of URLs, but submitting one does not guarantee that Google will crawl them. This comparison of single-URL requests and sitemaps describes the two approaches without suggesting there is a whole-site recrawl button.

Request indexing for the exact page

1. Open the Search Console property that covers the URL you changed.
2. Enter the full page address in URL Inspection. Check the inspected address before continuing: in the example, the target is https://example.com/guides/returns, not another URL in /guides/.
3. Run or review the live test. Look for a condition that would prevent Google from accessing or indexing the page rather than treating the inspection screen as an automatic go-ahead.
4. If Request Indexing is available and the live result permits the request, select it. Check that Search Console confirms the request for the intended URL.

The distinction between the inspected URL and its section matters. Requesting indexing for the returns guide is not a request to process every guide. A confirmation means the request was submitted; it is not a report of a completed Googlebot visit.

If Search Console will not accept the request

Use the live-test result to identify the immediate obstacle. A robots.txt block can prevent crawling; a noindex directive can prevent indexing; and an error response can keep the page from passing the test. Fix the condition that applies to the intended URL, then test that URL again before retrying. The live-test walkthrough here identifies those conditions as reasons a request may be unavailable.

Keep this check narrow. If the page returns an error, work on its response. If it is blocked by robots.txt, check the rule affecting its path. Removing a barrier merely makes a request possible; it does not establish that Google has crawled or selected the page for its index. For a broader investigation after the request is possible, see Technical SEO: How to Check Whether Google Can Crawl, Render, and Index a Page.

Check the result later—not just the confirmation

After submission, reinspect the same URL for Google’s reported crawl and indexing information. A later reported crawl would answer a different question from the submission confirmation: whether Google says it revisited the URL. An indexed status would answer another question: whether Google reports the page in its index. Neither observation promises a ranking or immediate appearance for a particular search.

There is no fixed crawl-time guarantee for a URL Inspection request. Timing depends in part on crawl demand, capacity, accessibility, and whether Google considers the URL worth revisiting. Avoid turning a confirmation into a deadline: record the exact URL you requested, then use its later inspection result to decide whether there is an access or indexing problem to investigate.