Request Indexing in Search Console: Limits and Quota

The Request indexing button in the URL Inspection tool adds a single URL to a priority crawl queue. Google confirms there is a daily quota on these requests but does not publish the number, and it says that asking several times for the same URL does not make the crawl happen sooner. The button is meant for a few important pages. For anything more than that, sitemaps and internal links are the mechanism Google expects you to use.

What the button actually does

When you click it, Search Console runs a quick live test to make sure the URL is fetchable and has no obvious indexing blocker, then queues the URL for crawling with elevated priority. You get the message "Indexing requested".

What it does not do:

• It does not index the page. It schedules a crawl. Google then evaluates the page like any other and may still decline it.
• It does not bypass quality evaluation, canonicalisation or duplicate handling.
• It does not apply to the pages linked from that URL. One request covers one URL.
• It does not give you a timeline. Google's guidance is that crawling can take from a few days to a few weeks, although requested URLs are in my experience often fetched within hours to a couple of days.

The limits, stated honestly

Limit	What Google says	What that means for you
Daily quota	"There's a quota for submitting individual URLs." No number published.	Commonly reported as roughly ten or so requests per property per day. Plan around a handful.
Repeat requests	Requesting a recrawl multiple times for the same URL won't get it crawled any faster	One click per change is enough
Permission	You must be an owner or full user of the property	Restricted users cannot use it
Guarantee	Requesting a crawl does not guarantee inclusion in search results instantly or at all	It is a request
Bulk	No bulk option and no API equivalent	Large sets need a sitemap

Two other practical limits:

• The live test that runs before the request can take a minute or two and sometimes times out. That is a Search Console hiccup. Try again later.
• Google has at times switched the feature off for maintenance. If the button is missing or disabled for everyone, there is nothing to fix on your side.

"Quota exceeded"

This message means the property's daily allowance is used up. It resets the following day. It has no effect on your site's standing in search, and it does not mean anything is wrong with the URL.

If you manage several Search Console properties for the same site (a Domain property plus URL-prefix properties), you may notice that each has its own allowance. Do not build a workflow on that. It is still a manual, one-by-one tool, and adding properties to multiply requests is working against the intent of the quota.

When it is worth using

• A new page that matters commercially: a launch, a key landing page, a time-sensitive article.
• A significant update to an indexed page: a changed price, a corrected fact, a rewritten title.
• A fix to something embarrassing in the search result, such as a wrong title or an old snippet.
• After removing a noindex or a robots.txt block from an important page.
• A page you just restored from a 404 or 5xx.
• The first few pages of a brand new site (homepage and main sections), so Google starts following your links.

When it is a waste of quota

• The page is already indexed and unchanged. Nothing to gain.
• The status is "Crawled - currently not indexed" and you changed nothing. Google already saw the page and passed. A second look at the same content rarely ends differently. See Crawled - currently not indexed.
• The URL has a blocker. noindex, a canonical pointing elsewhere, a redirect, a 404. Fix it first.
• You have 5,000 pages to get indexed. At a handful per day, the arithmetic never works.
• You requested it yesterday. It is already queued.

A good routine for each request

1. Inspect the URL and read the current status.
2. Click Test live URL. Confirm "URL is available to Google", with crawling and indexing allowed.
3. Click View tested page and check the screenshot and rendered HTML contain your main content. If the render is empty, a crawl will not help.
4. Check that User-declared canonical is the URL itself (or whatever you intend).
5. Click Request indexing once.
6. Note the date. Re-inspect after a few days and look at Last crawl. If the crawl happened after your request and the page is still not indexed, the issue is the page, not the queue.

A pre-check saves quota. The indexability checker tests status code, robots.txt, meta robots, X-Robots-Tag and canonical in one go, so you do not spend a request on a page that cannot be indexed anyway.

How to get many URLs crawled

The button does not scale, and Google does not intend it to. These are the mechanisms that do.

1. XML sitemap with accurate lastmod

Google's recrawl documentation recommends a sitemap when you have many URLs. Keep it clean (canonical, 200-status, indexable URLs only) and update <lastmod> only when a page really changes. Submit it once under Indexing > Sitemaps. Google then re-reads it on its own schedule. Check yours with the sitemap validator, and see lastmod best practices for how Google uses the field.

2. Internal links from frequently crawled pages

Link new and updated pages from your homepage, category hubs or other pages Googlebot visits daily. For most sites this is the single most effective lever for faster crawling, and it has no quota.

3. Validate fix for a whole issue group

If you fixed a problem that affected many URLs, open Indexing > Pages, click the reason and press Validate fix. Google rechecks the affected URLs over time. It says validation typically takes up to about two weeks and can take much longer, but it covers the full set without any per-URL work.

4. Request the hub, not every leaf

If you published 40 new product pages in a category, request indexing for the category page that links to all of them. One request, and Googlebot discovers the 40 links when it crawls.

5. The Indexing API, within its rules

Google's Indexing API accepts URL notifications programmatically, with a default quota of 200 publish requests per day per Google Cloud project. Google officially supports it only for pages with JobPosting or livestream BroadcastEvent markup, and it applies spam detection to submissions. Using it for other content is common but unsupported. If you are considering it, read the Google Indexing API guide first. TurboIndex automates this route alongside sitemap monitoring, is free for one site, and states the same caveat in the product: a notification is a crawl request, not an indexing guarantee.

6. IndexNow for the other search engines

IndexNow has no comparable per-URL daily friction: a single POST can carry up to 10,000 URLs for Bing, Yandex, Naver, Seznam and other participants. Google does not take part, so this helps everywhere except Google. The IndexNow submitter sends a list in one go.

Troubleshooting

"Indexing request rejected" or "During live testing, indexing issues were detected." The pre-check found a blocker: noindex, a robots.txt disallow, an error status code or a redirect. Open the live test details, fix the cause and try again.

The live test fails but the page works in a browser. Something treats Googlebot differently: a firewall rule, bot protection, geo blocking, or rate limiting. Check the fetch error in the live test and then your CDN or WAF logs.

"Oops, something went wrong" or endless spinning. Usually temporary on Google's side. Wait and retry. If it persists only for one URL, check that the URL responds quickly, since very slow pages can time out the live test.

The button is greyed out. You probably have restricted access to the property. Ask an owner to raise your permission to Full.

Requested days ago, last crawl date unchanged. Priority does not mean immediate. If a week passes with no crawl, check Settings > Crawl stats for host problems and whether Googlebot is being blocked or slowed.

Crawled after the request, still not indexed. The queue did its job. Now it is a content, duplication or canonical question. Use the flow in why is my page not indexed.

The short version

Use Request indexing sparingly, once per URL per meaningful change, after confirming the page is indexable. Let sitemaps, internal links and Validate fix handle volume. If you find yourself wishing for a higher quota, the better question is why Google is not crawling those pages on its own, and the answer is usually in your internal linking or your content.