Request Indexing in Google Search Console: What It Does and Its Limits (2026)

Request Indexing is the Google Search Console feature that submits one URL to a priority crawl queue: paste the URL into the search bar at the top of Search Console, wait for the inspection to load, and click Request Indexing. It buys a faster crawl — typically within hours to two days — and nothing else: the indexing decision that follows the crawl remains quality-gated, and the button accepts roughly 10–12 URLs per property per day.

This guide gives the exact walkthrough, what happens after the click, the caps, the reasons the button goes missing, the two-month period in 2020 when Google switched it off entirely, why re-requesting an unchanged page does nothing, and the channels that replace it at scale.

TL;DR — Quick Summary

• The path: Search Console search bar → inspect the URL → Request Indexing — one URL per request, verified properties only
• What it does: places the URL in a priority crawl queue; Googlebot typically fetches within hours to 2 days
• What it does not do: guarantee indexing — Google's quality thresholds apply after the fetch, unchanged
• The caps: roughly 10–12 manual requests per property per day; past them, Search Console reports the quota as exceeded until the next day
• Button missing or failing: quota exhausted, or the URL is blocked by robots.txt or noindex — fix the block first
• History check: Google disabled the feature for about two months in late 2020 — it is a convenience, not an entitlement
• At scale: sitemaps carry the inventory, internal links set priority, bulk submission services clear backlogs and third-party URLs

---

How Do You Request Indexing in Google Search Console?

You request indexing through the URL Inspection tool: inspect the exact URL in a property you have verified, then click the Request Indexing button on the result screen. The whole flow takes under a minute per URL.

1. Open Google Search Console and select the property containing the URL
2. Paste the full URL — protocol included — into the search bar at the top of any screen
3. Read the inspection verdict: "URL is on Google" or the specific exclusion state
4. Run Test live URL when the page is new or recently fixed — the live test confirms the URL is fetchable and indexable before you spend a request on it
5. Click Request Indexing and wait for the confirmation that the URL was added to a priority crawl queue

Ownership gates everything here: URLs on domains outside your verified properties cannot be inspected or submitted. The button also submits exactly the URL you inspected — one variant, one request — so inspect the canonical version, not a parameter or protocol variant.

---

What Happens After You Click Request Indexing?

The URL enters a priority crawl queue, and Googlebot typically fetches it within hours to two days — well ahead of natural scheduling on small and new sites. After the fetch, the standard pipeline runs unchanged: rendering, canonical selection, and a quality-gated indexing decision.

That last stage is the one the button never touches. Google's documentation on asking Google to recrawl your URLs is explicit that a request queues a crawl without promising an indexing outcome — a page Google evaluated and declined before comes back to the same verdict after the requested crawl unless the page changed. Request Indexing moves a URL to the front of the fetch line; it buys no exemption from search engine indexing selectivity.

Measure the result instead of refreshing search results: re-inspect the URL after a day or two and read the last-crawl date. A new crawl date means the request worked; the verdict above it tells you what Google decided.

---

What Are Request Indexing's Limits?

Request Indexing processes one URL at a time and stops at roughly 10–12 manual requests per property per day. The caps are the feature's defining constraint, and they are per property, not per user.

The arithmetic sets the feature's real role. A 300-URL backlog at a dozen requests per day is a month of daily clicking — before counting the URLs that need a second pass. Request Indexing is built for the single urgent URL: the launch page, the corrected page, the page whose fix cannot wait. Inventory-scale submission belongs to the channels in the final section.

---

Why Is the Request Indexing Button Missing or Not Working?

The button disappears or fails for three reasons: the daily quota is exhausted, the URL cannot be crawled, or the URL cannot be indexed. Each has a distinct signal in the inspection result and a distinct fix.

• Quota exceeded. Search Console reports the quota as exceeded after roughly 10–12 requests in a day. Nothing is broken; the quota resets daily, and requests past the cap are rejected until it does.
• URL blocked by robots.txt. A Disallow rule matching the URL means Googlebot is forbidden to fetch it, so a crawl request has nothing to do. Remove or narrow the rule first — the inspection panel's crawl-permission line tells you when this is the blocker.
• URL excluded by noindex. A noindex directive makes the crawl pointless: Google fetches the page and is instructed not to index it. Remove the directive, confirm with Test live URL that the live page is indexable, then request.

The order of operations matters: fix the block, prove the fix with the live test, and spend the request last. A request fired at a blocked or noindexed URL consumes quota to reconfirm the block.

---

Has Request Indexing Ever Been Turned Off?

Yes. Google disabled Request Indexing in October 2020, citing infrastructure changes, and restored it in December 2020 — roughly two months in which the button simply did not exist. Discovery and indexing ran normally the entire time through sitemaps, internal links, and scheduled crawling.

The episode is the clearest statement of what the feature is: a convenience layer on top of Google's crawl systems, not a load-bearing part of them, and removable at will. An indexing strategy that depends on manually requesting every URL fails the moment the button pauses, hits its quota, or disappears again. Build on the channels that never switch off — the inventory and link infrastructure below — and reserve Request Indexing for the URLs where a single fast crawl changes something.

---

Does Requesting Indexing Again and Again Help?

No. Repeated requests for an unchanged page do not stack: Google documents that requesting a recrawl multiple times for the same URL does not get it crawled any faster, and a page that was crawled and declined returns to the same verdict for as long as it is the same page.

Re-requesting is legitimate in exactly one case: the page changed. New content, a removed noindex, a fixed canonical — after a real change, one new request is the fast way to get the new version fetched. Without a change, the loop of request → "Crawled - currently not indexed" → request again spends quota to re-run a settled evaluation.

Before any repeat request, confirm what actually happened the first time. The inspection's last-crawl date separates "never fetched" from "fetched and declined", and the five verification methods are compared in how to check if a page is indexed on Google. A missing crawl date means the request has not been processed; a fresh crawl date with an exclusion verdict means the page — not the submission — is the problem.

---

How Do You Submit URLs at Scale?

Request Indexing tops out at about a dozen URLs a day, so scale runs on three other channels: an XML sitemap for the inventory, internal links for priority, and bulk submission services for backlogs and third-party URLs.

• XML sitemap for the inventory. One file carries up to 50,000 URLs with lastmod recrawl hints — the submission flow is in how to submit a sitemap to Google. Discovery-only, but it covers everything.
• Internal linking for priority. Links from frequently crawled pages get new URLs discovered within hours, with no quota and no button to press.
• Bulk submission services for the rest. Backlogs beyond the manual caps, and URLs on domains you don't own — backlinks — which neither Request Indexing nor any Search Console feature accepts. A submission service pushes them into Google's crawl systems directly, at pay-per-URL volume.

The full ranking of all five channels — speed, capacity, and the decision table matching each situation to its channel — is in how to submit a URL to Google. Whichever channel submits, verify outcomes the same way: batch-check the URLs in the Google Index Checker a few days later.

---

Frequently Asked Questions

How long does Request Indexing take to work?

The crawl typically arrives within hours to two days of the request. The indexing decision follows the fetch: established sites often see the page indexed within a day, while new domains wait longer because quality evaluation — not crawl scheduling — is their bottleneck.

How many URLs can you request per day?

Roughly 10–12 manual requests per property per day, one URL at a time. Past the cap, Search Console reports the quota as exceeded and rejects further requests until the daily reset.

Why is my page still not indexed after requesting indexing?

Because the request buys a crawl, not an indexing decision. Re-inspect the URL: a missing last-crawl date means the fetch has not happened yet, while a fresh crawl date with an exclusion verdict means Google evaluated the page and declined it — a content problem that another request cannot fix.

Can you request indexing for a URL on a site you don't own?

No. URL Inspection and Request Indexing work only inside Search Console properties you have verified. URLs on other domains — including backlinks pointing at your site — reach Google through links on crawled pages or through bulk submission services.