How to Request Indexing in Search Console: Limits and What to Do When It Does Nothing

The Request Indexing button is in the URL Inspection tool, right below the coverage status. You paste a URL, run the inspection, and click it. Google says it will try to crawl the URL sooner than it would have on its own schedule. That much is true. What the button does not do is guarantee indexing, guarantee speed, or give you unlimited uses.

If you have spent any time submitting URLs manually, you have probably hit the quota message or submitted a page three times and watched it stay out of the index. This guide explains what the button actually does, what the limits are, and what to work on instead when manual submission is not moving things forward.

What "Request Indexing" Actually Does

When you click Request Indexing, Google adds your URL to a priority crawl queue. According to Google Search Central documentation, this is not a guarantee of indexing. It is a signal that the URL is ready and worth crawling soon.

Google still decides, after crawling, whether to index the page. The crawl and the indexing decision are separate events. A URL can be crawled immediately after a request and still end up in Crawled - currently not indexed because Google found the content thin, low-quality, or not meaningfully different from other indexed pages.

The Request Indexing button is most useful for two scenarios: a page that was recently published and has not been crawled yet, and a page that was recently updated with a significant change that Google should see quickly. It is not a fix for pages Google has crawled and declined to index.

Daily Limits and Quota

Google does not publish the exact quota for Request Indexing, but the URL Inspection tool enforces a daily limit per property. You will see a message when you have used up your requests for the day: "Request indexing quota exceeded. Please try again tomorrow."

In practice, the quota is typically around 10 requests per property per day for Search Console properties. For Google Search Console API users, the Search Console API documentation describes separate quota for the Indexing API, which is a different mechanism built for large sites with Job Posting or BreadcrumbList structured data.

If you manage multiple properties, the quota applies per property, so a request on one domain does not count against another.

When the Button Does Nothing

If you request indexing and the page stays out of the index after several days, the issue is almost always content quality, not crawl frequency. The Request Indexing queue gets the page crawled faster. It does not change what Google finds when it arrives.

The most common reasons a requested page does not get indexed:

Thin or low-quality content. Google uses quality signals that include E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness). A page with a few hundred words, no original insight, and no demonstrated expertise is likely to be passed over regardless of how many times you request indexing.

Duplicate or near-duplicate content. If the page closely matches another page on your site or on the web, Google may index a different version or none at all. Use the URL Inspection tool to check whether Google identifies a different canonical.

Thin category or archive pages. Pagination pages, filtered views, and category archives with minimal unique content are frequently crawled and not indexed. Adding substantial unique content or using rel="canonical" pointing to the main category page can help.

noindex in meta or HTTP header. This is easy to miss after a CMS update or theme change. The URL Inspection tool will show if a noindex directive is present.

Blocked by robots.txt. The page might be crawlable but blocked from indexing by a Disallow rule interacting oddly with the page's configuration.

How to Actually Diagnose a Page That Will Not Index

Open the URL Inspection tool for the specific page. The coverage status at the top tells you which bucket the page is in. For pages that will not index despite multiple crawl requests, run the following checks in order.

Check the Google-selected canonical. If Google shows a different canonical than the page you are inspecting, it has decided another URL represents this content better. The issue is at the site architecture level, not crawl frequency.

Check the last crawl date and rendered HTML. The URL Inspection tool shows the page as Googlebot rendered it. If the rendered HTML is missing content that your browser shows, there is a JavaScript rendering problem. Google is seeing an empty or partial page.

Check the page experience signals. Core Web Vitals failures and mobile usability issues do not directly prevent indexing, but they are part of the broader quality picture Google evaluates.

Pull the Performance report filter. If the page has zero impressions over 90 days, it has either never been indexed or was indexed briefly and dropped. If it had impressions and then lost them, check whether a site update changed the page's content or added a noindex.

What to Fix Instead of Clicking the Button More

If the page has a genuine quality problem, additional indexing requests will not help. Focus on the content itself.

For informational pages, make sure the page actually answers the question a searcher would type. Thin introductory pages that link out to the real answer rarely index reliably.

For product or landing pages, check whether the page has enough unique content to stand on its own. Category pages with five products and three words of description per product are regularly excluded.

For pages that were indexed and dropped, compare the current version against the version that ranked. Use the 16-month Performance report in Search Console to find when impressions fell. That date is usually close to when the content changed, the page was migrated, or a site update added unexpected noindex signals.

Internal linking matters too. A page with no internal links pointing to it looks low-priority to Google's crawl scheduler. Even after a successful Request Indexing submission, a page with no internal links may not hold its index status. Add links from at least two related pages on your site, using descriptive anchor text that matches what the page is about.

How we got 312 pages indexed in 30 days covers the internal linking and submission workflow in detail for sites managing indexing at scale.

Using the Search Console Tools Index Boost

For pages that have passed the content quality check but still need faster indexing, Search Console Tools provides an Index Boost feature that works alongside manual URL submission. It monitors your crawl request history and surfaces pages that have been requested but not yet indexed, so you can prioritize which pages actually need content work versus which are simply waiting in the crawl queue.

The free tool connects to your Search Console data directly, so you are working from real crawl and coverage data rather than guessing.

The Indexing API: When Manual Submission Is Not Enough

The Google Indexing API is a separate mechanism that some sites use for rapid indexing. It is officially supported only for pages with JobPosting or BroadcastEvent structured data. Using it outside those schemas violates Google's terms of service.

If you see guides suggesting the Indexing API as a workaround for general content indexing, those guides are recommending something Google does not permit and may penalize. For standard blog posts, product pages, and service pages, the URL Inspection tool and a solid internal linking structure are the right tools.

Submitting Your Sitemap

For new sites or after major migrations, submitting a sitemap through the Sitemaps report (found in the left-hand navigation in Search Console) gives Google a complete inventory of your pages. The URL Inspection tool is for individual page checks; the sitemap is for communicating your full page set.

After submitting a sitemap, the Sitemaps report shows how many URLs Google has discovered and how many are indexed. That ratio is a useful signal. A high discovered-to-indexed gap, combined with a lot of Crawled - currently not indexed or Discovered - currently not indexed pages, points to a crawl budget or content quality problem that manual indexing requests will not solve.

Frequently Asked Questions

How long does Request Indexing take to work? Google does not publish a specific timeline. In practice, pages that Google is ready to index often appear within a few hours to a few days after a request. Pages with content quality issues may not index at all, regardless of how quickly Google crawls them.

Can I request indexing for a page that shows Discovered - currently not indexed? Yes. The Request Indexing button is available for any URL in your property, regardless of its current coverage status. For Discovered - currently not indexed, the request moves the URL from the pending crawl queue to the priority queue.

Does requesting indexing through the API count against my UI quota? The Indexing API has its own quota, separate from the URL Inspection tool's daily limit. Using one does not affect the other.

Why does my page show as indexed in the URL Inspection tool but not appear in Google search results? The URL Inspection tool reflects Google's index as of the most recent crawl. There can be a delay between when a page is indexed and when it appears in search results, and not every indexed page ranks for every query. Check the Performance report to see whether the page has any impressions.

Is there a limit on how many times I can request indexing for the same URL? Google does not block repeated requests for the same URL, but after two or three submissions with no indexing result, additional requests are unlikely to change the outcome. At that point, the issue is content quality or a technical block that crawl requests alone cannot fix.