You published a great post, but a week later it is still invisible on Google. The fastest fix is the Request Indexing feature in Google Search Console – a direct line that asks Google to crawl a specific URL now instead of whenever its scheduler gets around to it. This guide walks through exactly how to use it, when it works, when it does not, and what to do when Google still refuses to index your page.
What Request Indexing Actually Does
When you request indexing, the URL is added to a priority crawl queue. Googlebot typically visits within minutes to a few hours. Crawling, however, is not indexing: Google still runs the page through quality evaluation before deciding whether it enters the index. Think of the button as skipping the line at the door – the bouncer still checks your ID.
Step-by-Step: Requesting Indexing
Step 1: Open URL Inspection
Sign in to Google Search Console and select your property. At the very top is a search bar labeled “Inspect any URL”. Paste the full address of the page you want indexed, including https, and press Enter.
Step 2: Read the verdict
After a few seconds you get one of two headline results. “URL is on Google” means the page is already indexed – no action needed. “URL is not on Google” means it has not been indexed yet, and the details below explain why: not crawled yet, crawled but not indexed, blocked by robots.txt, or marked noindex.
Step 3: Click Request Indexing
If the page is not on Google and there are no blocking errors, click Request Indexing. Search Console runs a live test to confirm the page is reachable, then queues it. You will see a confirmation that the URL was added to the priority queue.
Step 4: Verify a day later
Come back after 24 hours and inspect the same URL. Most healthy pages on established sites show “URL is on Google” within a day. New domains may take longer – that is normal.
When Request Indexing Helps – and When It Does Not
- Helps: brand-new posts, significantly updated pages, pages fixed after an error, and time-sensitive content that cannot wait for the normal crawl cycle.
- Does not help: pages Google already crawled and chose not to index. Re-requesting the same weak page changes nothing – the page itself must improve.
- Cannot help: pages blocked by robots.txt, marked noindex, returning errors, or canonicalized to another URL. Fix the block first.
The Daily Quota Problem
Google limits how many individual URLs you can submit per day – roughly 10-12 per property. If you hit the limit, the button simply stops queueing. For bulk needs, the sitemap is the correct tool: update it, and Google recrawls everything on its own schedule. Reserve Request Indexing for the handful of URLs that genuinely cannot wait.
Why Your Page Still Is Not Indexed After Requesting
Crawled – currently not indexed
Google saw the page and declined. This is a quality and demand signal: the content may be thin, too similar to existing pages, or the site too new to have earned trust. Strengthen the content, add internal links from your most-visited pages, and give it time.
Discovered – currently not crawled
Google knows the URL exists but has not fetched it, usually because the site is new or crawl demand is low. Internal linking from indexed pages and consistent publishing accelerate this more than repeated button-clicking.
Duplicate or canonical issues
If Google chose a different canonical, your page will not index separately. Check that your canonical tag points to the page itself and that you are not competing with a near-identical URL on your own site.
Technical blocks
A stray noindex tag – often left over from staging – or a robots.txt disallow rule silently kills indexing. The URL Inspection details name the exact block; remove it, then request again.
Faster Indexing Habits That Beat the Button
- Submit an XML sitemap once, and keep it clean – only canonical, indexable URLs.
- Link every new post from your homepage or a high-traffic page for its first weeks.
- Publish on a consistent schedule; Google adapts crawl frequency to your rhythm.
- Share new URLs where real traffic finds them – clicks create crawl demand.
- Fix Page Experience basics: fast, mobile-friendly pages get crawled more willingly.
FAQ
How long does Request Indexing take to work?
Crawling usually happens within minutes to a few hours. Appearing in search results typically takes a few hours to a couple of days, depending on site trust.
How many URLs can I request per day?
Google does not publish an exact number, but in practice the limit is around 10-12 URLs per property per day. The quota resets daily.
Does clicking Request Indexing multiple times speed things up?
No. Repeat requests for the same URL do not move it up the queue. If the page was crawled and not indexed, the content – not the queue – is the problem.
Can I request indexing for someone else’s website?
No. URL Inspection only works for properties you have verified in your own Search Console account.
Is there a way to bulk-request indexing?
Not through Search Console. The Indexing API exists but officially supports only job postings and live-event pages. For everything else, a clean sitemap plus strong internal linking is the legitimate bulk solution.
If requesting indexing does not work, the page itself is usually the problem – see the seven fixes for crawled – currently not indexed. For getting new content discovered faster in the first place, read how to get a website indexed fast.
Final Thoughts
Request Indexing is the most direct tool you have for getting individual pages into Google fast – but it is a request, not a command. Use it for new and updated URLs, respect the daily quota, and read the inspection details carefully when Google says no. Pair the button with a clean sitemap and deliberate internal linking, and indexing stops being a bottleneck for good.