When and how to request indexing in Google

Request indexing is a crawl nudge, not a rank nudge

The Request indexing button in the URL inspection tool tells Google this specific URL changed and is worth another crawl. It does three things: it asks for a crawl, it warns Google not to use JSON-LD that some invalid markup hides, and it does not promise any rank. It expedites a crawl for one URL, subject to daily limits.

The mental model matters: Google decides indexing. You can influence crawl priority and fix blockers, but a request will not override a quality decision, a duplicate-content decision, or a missing page state.

When requesting actually helps

Request indexing is worth doing when all four are true:

1. The page is index-worthy (unique, useful, not duplicate content).
2. The technical gate passes: the live URL test says it is available to Google.
3. You made the change that matters (fixed a noindex, fixed a redirect, added content, fixed a blocked resource).
4. The page is not a duplicate of a canonical you do not intend to consolidate.

If the reason the page is not indexed is still present, the request is wasted. The live test does not test every reason, so a clean live test is not proof the page will index, but a failing live test is proof it will not.

A practical sequence

1. Inspect the URL and read the current reason.
2. Fix the underlying cause (canonical, robots, content quality, server response).
3. Click Test live URL.
4. When it says available to Google, click Request indexing.
5. Wait. Google processes the request in the normal crawl queue; there is no rank guarantee and no notification.

Rate limits and the "one per day per page" thinking

Request indexing is rate-limited to around ten to twelve requests per property per rolling day from the manual tool. You can request the same URL again later (about once per day applies for that URL), but pushing one stubborn URL again and again is noise, not signal. The privacy sandbox hides the exact limit, so treat the conservative number as the ceiling.

For bulk, the correct tool is the sitemap. A sitemap change to a new page tells Google to crawl it more eagerly without consuming the manual limit, and any page in a submitted sitemap is discoverable. The submit a sitemap guide covers this path, because re-clicking Request indexing for hundreds of pages is the most common misuse.

When it will not help

• A noindex page: fix the tag, then request.
• A page Google already selected a different canonical for: fix the canonical logic first.
• A soft 404: return real content or a hard 404.
• A page Google already indexed repeatedly and chose not to keep: improve the page and give it real internal links, then re-request weeks later, not daily.

The site-wide view of what needs a request comes from the Pages report, which shows the pattern where inspection shows the single case.