Indexing a page in Google Search Console means asking Google to crawl it through the URL Inspection tool. Paste the full URL into the inspection bar at the top, click Test live URL to confirm Google can reach it, then click Request indexing. Google adds the URL to its crawl queue. It does not promise to index it.
That last sentence matters more than the button. Google’s own guide to how Search works says plainly: “Google doesn’t guarantee that it will crawl, index, or serve your page.” Request Indexing speeds up a crawl. Whether the page gets indexed is still Google’s call.
So I treat this as a two-part job. First, the clicks. Then the real work, which is making the page worth indexing and easy to find.
Before You Start: Three Checks
You need three things in place, or the button won’t help.
- Access. You must be an owner or full user of the Search Console property. Restricted users can inspect URLs but can’t request indexing.
- The right property. The URL has to sit inside the property you’re working in. A page on
shop.example.comwon’t inspect inside a property forwww.example.comunless you use a Domain property. - A finished page. Publish the final version first. Requesting a crawl for a draft with placeholder text just wastes a request.
How to Index Pages in Google Search Console in Four Steps
This is the exact routine I follow when I publish a page that matters. It takes about two minutes per URL.
Step 1: Inspect the URL
Open Search Console, pick your property, and paste the full URL, including https://, into the search bar at the top that reads “Inspect any URL.” Press Enter.
After a few seconds you’ll see one of two headlines. “URL is on Google” means it’s indexed and eligible to appear. “URL is not on Google” means it isn’t, and the report usually tells you why under Page indexing.
If it already says “URL is on Google,” stop here. You don’t need to request anything unless you changed the page and want the new version picked up sooner.
Step 2: Run a Live Test
Click Test live URL in the top right. This fetches the page as it is right now, not as Google last saw it.
Look at three things in the result: whether the page is available to Google, whether indexing is allowed, and the screenshot under View tested page. If the screenshot shows a blank page or a cookie wall, Google may be seeing far less content than your visitors do.
One warning from Google’s URL Inspection help page. It asks whether a valid live test means the page will be indexed, and answers: “No.” A clean test only proves Google can access the page.
Step 3: Click Request Indexing
Click Request indexing. Google runs a quick check for obvious indexing errors first. If the page is blocked by a noindex tag or robots.txt, the request fails, which is useful because it tells you exactly what to fix.
When it works, a small dialog confirms the request and says the URL went into a priority crawl queue. Close it and move on.
Don’t click it again tomorrow. Google’s recrawl documentation says requesting a recrawl multiple times for the same URL “won’t get it crawled any faster.”
Step 4: Wait, Then Re-inspect
Google says crawling “can take anywhere from a few days to a few weeks.” In my experience, checking back after 7 days is about right, so I set a reminder and inspect the URL again then. The Last crawl date under Page indexing tells you whether Googlebot has visited since your request.
Don’t trust a site: search for this. It’s a rough sample. URL Inspection reads Google’s index record for that exact URL, so it’s the answer I rely on.
How Many Pages Can You Request Each Day?
There is a limit, but Google doesn’t publish the number. The help page only says “there is a daily limit to how many index requests you can submit,” and the recrawl page says there’s a quota for individual URLs.
You’ll see various numbers quoted on SEO blogs. I don’t repeat them, because Google hasn’t confirmed any of them and the limit could change without notice. When you hit it, Search Console shows a quota message and you try again the next day.
In practice the limit rarely bites if you use the tool the way it’s meant to be used. I request indexing for new money pages, important updates and fixed errors. Everything else goes through the sitemap.
Which Route Should You Use?
Request Indexing is one of three ways to get a URL in front of Google. Picking the right one saves time and quota.
If you have one to a handful of important pages, use URL Inspection and Request Indexing. A new service page or a corrected product page fits here.
If you have many URLs, or you publish regularly, rely on your XML sitemap. Google’s recrawl guide says: “If you have large numbers of URLs, submit a sitemap.” You submit it once, and Google rereads it over time. I walk through the clicks in how to submit a sitemap to Google Search Console, and what should go inside it in XML sitemap best practices.
If you were thinking of the Indexing API, check your page type first. Google’s Indexing API quickstart says it “can only be used to crawl pages with either JobPosting or BroadcastEvent embedded in a VideoObject.” Using it for blog posts or product pages is outside its supported use, and I don’t do it for clients.
| Situation | Best route | Why |
|---|---|---|
| One new or updated key page | URL Inspection, Request indexing | Fast, targeted, uses one request |
| A new blog post on a site with a sitemap | Sitemap plus an internal link | Google rereads the sitemap; no quota |
| Hundreds of new URLs | Sitemap (or sitemap index) | Built for scale |
| Job listings or livestream pages | Indexing API | The only page types it supports |
| A page fixed after an error | Request indexing, then Validate fix in the report | Confirms the fix across affected URLs |
On that last row, be patient. Google’s help says validation “typically takes up to about two weeks, but in some cases can take much longer.”
Why Isn’t Google Indexing Your Page?
If you requested indexing and the page is still “not on Google” weeks later, the button wasn’t the problem. Open Indexing, then Pages, find the reason listed for the URL, and follow the branch that matches.
Discovered, currently not indexed. Google knows the URL exists but hasn’t crawled it. This often points to weak internal linking or a site with lots of low-value URLs. My fixes are in Discovered, currently not indexed.
Crawled, currently not indexed. Google fetched the page and decided not to index it for now. In my audits this usually comes down to thin or overlapping content, and rewriting the page tends to help far more than requesting it again. My full diagnosis is in Crawled, currently not indexed.
Soft 404. The page returns a 200 status but looks empty or like an error to Google. Thin category pages and “no results” pages trigger it a lot. See my guide to soft 404 errors.
Alternate page with proper canonical tag. This one is often fine. The URL points to another page as its canonical, and Google indexed that one instead. I explain when to worry in alternate page with proper canonical tag.
URL marked ‘noindex’ or blocked by robots.txt. Remove the block, then request indexing. On WordPress, check the “Discourage search engines” box under Settings, Reading, and your SEO plugin’s per-post settings.
Duplicate, Google chose different canonical than user. Google thinks another URL is the better version. If two of your own posts target the same query, that’s often keyword cannibalization, and merging them works better than fighting the canonical choice.
Google’s own Page indexing report help adds useful perspective: “You should not expect all URLs on your site to be indexed, only the canonical pages.” So a handful of excluded URLs is normal. A key page stuck for weeks is not.
Don’t Skip Internal Links
Here’s what I tell every client who asks me to “just index” a page. If nothing on your site links to it, you’re asking Google to care about a page you don’t seem to care about.
Google discovers new pages by following links from pages it already knows. An orphan page, one with no internal links pointing to it, depends entirely on the sitemap or a manual request, and it sends a weak signal about how important it is. Before I request indexing for a new page, I add two or three links to it from related posts that already get traffic, using descriptive anchor text.
When I compare pages that got internal links on day one with pages that only got a request, the linked ones are the ones I stop worrying about. That small step usually does more than the request itself. The request gets Googlebot there once. The links keep it coming back.
A Quick Decision Path
If URL Inspection says “URL is on Google”, do nothing, unless you changed the page. Then request indexing once.
If it says “not on Google” and the live test fails, fix the error the test shows first. Noindex, robots.txt, a 404 or a redirect all block the request.
If the live test passes, request indexing, add internal links, and check that the URL is in your sitemap.
If it’s still not indexed after a few weeks, stop requesting. Read the reason in the Page indexing report, fix the page, then request once more.
When Should You Get Help?
If dozens of important pages sit in “Crawled, currently not indexed” or “Discovered, currently not indexed” at once, you probably have a sitewide issue. Crawl traps, duplicate URL patterns, JavaScript rendering or a quality problem across a whole template are common causes.
That’s technical SEO work rather than button pressing. Our technical SEO service handles exactly this kind of indexing diagnosis, and it’s part of our complete SEO service for ongoing clients. If you just want to know where you stand, the free SEO audit is a good first step.
Frequently Asked Questions
How Long Does It Take Google to Index a Page After Requesting?
Google says crawling can take a few days to a few weeks, and a crawl doesn’t guarantee indexing. Re-inspect the URL after about a week and check the Last crawl date. If Google crawled it but didn’t index it, the page itself needs work.
Can I Request Indexing for Pages on a Site I Don’t Own?
No. You need to be an owner or full user of a verified Search Console property that contains the URL. For sites you don’t control, the only route is earning links from pages Google already crawls.
Does Requesting Indexing Improve Rankings?
No. It only asks Google to crawl the URL sooner. Rankings depend on the page’s content, relevance and links once it’s indexed. Requesting indexing after a real update can get the new version seen faster, which is the only benefit.
Why Is the Request Indexing Button Not Working?
The most common reasons are a quota message after many requests that day, a page blocked by noindex or robots.txt, or not having owner or full user permission. Run the live test to see whether the page itself is blocked.
Should I Use an Indexing Tool or Plugin That Promises Instant Indexing?
I’d avoid tools that push ordinary pages through the Indexing API. Google limits that API to job posting and livestream pages. Fix internal links, keep your sitemap clean, and use Request Indexing for the few pages that need it.
Last updated: October 2026 by Mizanur Rahman
