Request Indexing in Google Search Console: What It Does and the Daily Limit

Request indexing is the button in Google Search Console's URL Inspection tool that asks Google to crawl one URL and consider it for indexing. When you click it, Google runs a quick live test of the page and, if nothing blocks indexing, adds the URL to its crawl queue. A request doesn't index the page or guarantee that it will be indexed, and there's a daily limit on requests whose size Google doesn't publish.

The button sits on the result of the URL Inspection tool. This post covers what a Google indexing request does after the click, the limit behind Quota exceeded, and when a request is worth spending. If yours fails, see indexing request rejected.

What Request indexing does

What happens after the click, with the first two steps as Google's URL Inspection tool help describes them:

1. A quick check. Google tests the live page for immediate indexing errors. If the live test finds the page non-indexable, for example because robots.txt blocks it, a noindex rule is present or the fetch fails, you can't request indexing.
2. The queue. A page that passes is submitted to the indexing queue.
3. The crawl. Googlebot fetches the page later. Nothing in the index changes before that.
4. The decision. Google processes the page as it would after any crawl: whether to index it, and which URL in a group of duplicates to treat as canonical.

A request changes when Google crawls one URL, not what Google decides after the crawl. Google's page on how to ask Google to recrawl your URLs says a crawl request doesn't guarantee the page will appear in results quickly, or at all, and that requesting the same URL several times won't get it crawled sooner.

Passing the check isn't a prediction either. The live test can't evaluate several Page indexing reasons, including Crawled - currently not indexed, Discovered - currently not indexed and the duplicate and canonical reasons, and Google says no test can guarantee that a page will be included in its index.

How to request indexing in Google Search Console

1. Open the property that contains the URL. The URL must be in the property that's currently open, and only an owner or full user of the property can request indexing (Ask Google to recrawl your URLs).
2. Paste the full URL into the bar at the top of Search Console, labeled Inspect any URL as of October 2026, and press Enter.
3. Read the indexed result first. If it says URL is on Google and you haven't changed the page since Last crawl, there's nothing to request.
4. If you just fixed something, click Test live URL. It fetches the current version, so you can see that the fix is live before you spend a request (live test vs indexed version).
5. Click Request indexing once and wait for the quick check to finish.
6. Inspect the URL again in a few days. A newer Last crawl date means Google crawled the page; the verdict tells you whether it indexed it.

As of October 2026, the dialog that follows usually shows one of these answers:

The Request indexing limit and Quota exceeded

Google limits indexing requests without saying by how much. The URL Inspection help mentions a daily limit on index requests, and the recrawl page a quota for individual URL submissions. As of October 2026, neither gives a number, says whether the count is per property or per account, or says when it resets. Figures quoted in forums are observations, not a documented limit.

The same help lists separate daily limits, also unpublished, for inspections and for live tests in each property. The only published numbers are for the URL Inspection API: 2,000 calls per day and 600 per minute per property (Search Console API usage limits). That API returns the indexed result only, can't test a live URL and has no method that requests indexing (method reference).

What to do after Quota exceeded

When the limit is used up, Search Console answers Quota exceeded instead of Indexing requested, and the URL isn't queued. Clicking again won't change that. Since Google doesn't document the reset, wait until the next day. Midnight Pacific Time is a reasonable line to wait for: it's when Google's Indexing API, a separate system, resets its own daily quota (Indexing API quota).

For the URLs you couldn't request:

• Put them in your sitemap with an accurate lastmod. The URL Inspection help calls a sitemap the best choice for many new or updated pages. Google uses lastmod when it's consistently and verifiably accurate, and ignores priority and changefreq (Build and submit a sitemap).
• Link to them from pages Google already crawls. Google primarily finds pages through links from pages it has crawled (SEO Starter Guide).
• Save tomorrow's requests for the few pages that matter most.

<url>
  <loc>https://example.com/pricing</loc>
  <lastmod>2026-10-28</lastmod>
</url>

Scripts that push ordinary pages through the Indexing API aren't a way around the limit: Google documents that API only for pages with JobPosting or a BroadcastEvent embedded in a VideoObject, and warns that abuse can get access revoked (Indexing API quickstart). There's no public API for the button either (request indexing API); bulk request indexing compares what works at scale.

When a request is worth it

Google's SEO Starter Guide says you usually don't need to do anything except publish your site, and the recrawl page notes that hosted platforms such as Blogger or WordPress usually submit new content for you. Requests are for the exceptions.

Worth a request

• An important new page Google hasn't found. URL Inspection shows no Last crawl date, which Google's guide to troubleshooting a single page reads as Google not having found the page yet: run a live test, then request. The Page indexing report help adds that a request can reduce the indexing lag for new content.
• A page you just unblocked. You removed a noindex, lifted a robots.txt rule, or fixed a 404 or a 5xx. Once the live test shows the fix, the same guide says to click Request indexing to tell Google the page has changed.
• An important change you need in Search soon. A corrected fact, a new price, a rewritten title on a page that gets traffic. Otherwise Google picks up changes when it next recrawls the page (Google recrawl).

Not worth a request

• An unchanged page Google crawled and didn't index. For Crawled - currently not indexed, the Page indexing report help says there's no need to resubmit the URL. Change the page first (crawled, currently not indexed).
• Hundreds of URLs. The limit makes it impractical, and Google points to a sitemap instead.
• A duplicate you want indexed on its own. The live test doesn't check duplicates or canonical selection, so the request can go through and Google can still pick a different URL as canonical. Fix the canonical, redirects and internal links instead.
• Pages on sites you don't own. Google lets you request indexing only for URLs you manage, which rules out backlinks and other third-party pages.

How long indexing takes after a request

Google gives ranges, not a schedule. The URL Inspection help says indexing typically takes only a day or so but can take much longer, and elsewhere that it can take up to a week or two; the recrawl page says crawling can take anywhere from a few days to a few weeks. Follow the page in URL Inspection, and read how long it takes Google to index a page for what changes the wait.

Request indexing compared with the other routes

How IndexCyborg handles indexing requests

IndexCyborg's Chrome extension, loaded from the dashboard's Settings, makes the request in your own Chrome: it opens your Search Console property in a background tab, types the URL into Inspect any URL, clicks Request indexing and logs Google's answer. It makes at most 10 requests per property per rolling 24 hours, a cap enforced by the API, the database and the extension, and a Quota exceeded answer pauses the site until midnight Pacific time.

When it picks pages itself, known-unindexed pages go first; pages excluded on purpose (noindex, robots.txt, redirects, duplicates) and pages that don't return 200 are never requested, and a page isn't picked again for 14 days. After you change a page, queue it by name with POST /v1/sites/{id}/google-indexing or the MCP tool request_google_indexing: named URLs skip that wait and are requested even when indexed, within the same cap. Requested means queued for a crawl, not indexed.

Frequently asked questions