How to Request Indexing in Google Search Console (Step by Step)
You published a new post and it is not on Google yet. Here is how to use the URL Inspection tool to request indexing, and what to do when the request does not help.
- In Search Console, paste the page URL into the search bar at the top to open the URL Inspection tool.
- Click Test live URL, then Request indexing if the page is available to Google.
- Google says indexing usually takes a day or so, but can take longer. A request is not a guarantee.
- For many pages, submit a sitemap instead of requesting each URL.
You wrote a good post, published it, and searched for it on Google. Nothing. Days pass, and the page still does not appear. This is one of the most common worries for new bloggers.
Google Search Console has a tool that lets you ask Google to crawl a single page. This guide shows you exactly how to use it, how to read the results, and what to do when the page still is not indexed.
What does "request indexing" mean?
Crawling is when Google's bot visits your page. Indexing is when Google stores the page so it can show in search results. A page must be indexed before anyone can find it on Google.
Normally, Google finds new pages on its own through links and sitemaps. Request indexing is a button in the URL Inspection tool that adds one URL to Google's crawl queue. It is a polite request, not an order. Google still decides whether to index the page.
Before you start: what you need
- Your website added and verified in Google Search Console.
- The full URL of the page, including
https://. - The page should be published, public and not blocked by a login or password.
If you have not added a sitemap yet, do that first. Our guide on submitting a sitemap in Google Search Console takes about five minutes.
How to request indexing: step by step
- Open Google Search Console and choose your property (your website) from the top left.
- Copy the full URL of your page.
- Paste it into the Inspect any URL search bar at the top of the screen and press Enter.
- Wait for the result. It shows what Google already knows about this URL from its index.
- Click Test live URL to check the current version of the page.
- If the live test says the URL is available to Google, click Request indexing.
- Google runs a quick check. If there are no immediate errors, you will see a message that the URL was added to a priority crawl queue.
What do the URL Inspection results mean?
The first result shows the indexed version, which is what Google saw last time. Google's help page lists these main statuses:
| Status | What it means | What to do |
|---|---|---|
| URL is on Google | The page is indexed and can appear in search. It is not a promise that it will rank. | Nothing urgent. Work on content and links. |
| URL is on Google, but has issues | Indexed, but some extra features (like structured data) have problems. | Open the details and fix the listed issues. |
| URL is not on Google | The page is not indexed and cannot appear in search. | Read the reason, fix it, then run a live test. |
| URL is unknown to Google | Google has never seen this URL. | Request indexing and add the page to your sitemap and internal links. |
The live test has its own labels: URL is available to Google, available but has issues, and not available to Google. Only the first two allow you to request indexing.
Request indexing not working? Common reasons and fixes
1. The page has a noindex tag
Some themes, SEO plugins or scripts add noindex to new pages, tag pages or the whole site in "development" mode. Check your SEO settings and remove noindex from pages you want in search.
2. robots.txt blocks the page
Open yourdomain.com/robots.txt and look for Disallow lines that cover your posts. Remove the block only for pages you want Google to crawl.
3. The page redirects or shows an error
If the live test shows a 404, a 5xx server error or a redirect, the page itself has a problem. Open it in a private browser window to check. Slow or overloaded hosting can also cause server errors.
4. You hit the daily limit
Google says there is a daily limit on index requests per property, plus separate limits for inspections and live tests. If you see a quota message, wait until the next day. Use a sitemap for bulk pages instead.
5. The request worked, but the page is still not indexed
This usually means Google crawled the page but decided not to index it yet. In Search Console this often appears as "Crawled - currently not indexed". Our guide on fixing Crawled - currently not indexed explains what to improve.
Request indexing vs sitemap: which should you use?
| Situation | Best method |
|---|---|
| One new, important post | Request indexing in URL Inspection |
| You fixed an error on one page | Live test, then request indexing |
| Many new or updated pages | Sitemap with lastmod dates |
| A whole new website | Submit sitemap, then request indexing for the home page |
Google's own advice for many new or updated pages is to submit a sitemap with lastmod values, rather than inspecting each URL one by one.
How to help Google index new posts faster (without tricks)
- Link to the new post from your home page and from two or three related older posts. See our internal linking guide.
- Keep your sitemap automatic, so new posts appear in it the moment they go live.
- Publish useful, original content. Thin or copied posts are often crawled but not indexed.
- Keep your site fast and online. Frequent downtime makes crawling harder.
- Share the post on your social pages so real people visit and link to it.
If you are building a news or updates site where fresh posts matter, a script with a clean structure, an automatic sitemap and fast pages helps a lot. You can look at our AdSense-ready website scripts to see how they are set up.
Should you request indexing after updating an old post?
Yes, if the update is meaningful. Good reasons include adding a new section, fixing wrong information, changing the title to match search intent better, or removing a noindex tag by mistake. Small changes, like fixing one typo, do not need a request. Google will see them on its next normal crawl.
When you update a post, follow this order:
- Make the change and clear your site cache, if you use one.
- Make sure the date in your sitemap (
lastmod) changes too. - Inspect the URL and run Test live URL to confirm Google sees the new version.
- Click Request indexing once. Do not repeat it every day.
How to check if a page is indexed later
- Inspect the URL again in Search Console after a few days.
- Open the Pages report under Indexing to see indexed and not indexed pages.
- Check the Performance report to see when the page starts getting impressions.
Final word
Request indexing is a useful button, but it is not magic. It works best when the page is open to Google, linked from your site, listed in your sitemap and worth indexing.
Next step: open Search Console, inspect your newest post, run a live test, and request indexing. Then add links to it from two older posts today.
Frequently asked questions
How long does Google take to index a page after I request indexing?
Google's help page says it typically takes a day or so, but it can take much longer in some cases. A request also does not guarantee that the page will be indexed.
Is there a limit on indexing requests?
Yes. Google says there is a daily limit on index requests for each property, and separate daily limits for inspections and live tests. Google does not publish the exact numbers on that page.
Should I request indexing for every new post?
You can for important posts, but for many new or updated pages Google recommends submitting a sitemap with lastmod values instead. Requesting the same URL again and again does not make it faster.
Why is the Request indexing button not working?
You cannot request indexing for a page that the live test marks as not indexable, for example because of a noindex tag or a block in robots.txt. Fix the issue shown, run the live test again, and then request indexing.