How to Submit a New URL in Search Console Without Treating It as a Ranking Trick
Request indexing in Google Search Console is the button people reach for when a new URL should be seen. It is not a ranking action. It asks Google to crawl one URL you manage, and submitting that request does not guarantee the page will enter the Google index.
The useful version of the click is a fail-closed gate, not a habit. Run the live test first. If that test treats the page as non-indexable, you cannot submit it. Only an owner or full user of the property can request indexing, and only for URLs you manage. Repeating the same URL does not make the crawl faster, and Google does not publish a numeric daily cap for the button, so the 10, 12, and 15 figures that circulate in SEO posts are not from Google's documentation.
What you should expect next is a wait, not a result. Indexing typically takes a day or so and can take much longer; crawling can take anywhere from a few days to a few weeks, and Google also says it can take up to a week or two. Even URL is on Google means the URL is eligible to appear, not that it is showing in results. For many new or updated pages, the better move is a sitemap with accurate lastmod, not a queue of manual requests.
- Request indexing nudges Google to crawl one URL you manage; it does not rank the page or guarantee indexing.
- Submit only after the live test does not mark the URL non-indexable, and only as an owner or full user.
- Repeating the same URL does not speed the crawl, and Google does not publish a numeric daily limit for the button.
- Expect about a day in typical cases, and up to a week or two or longer; crawling can take a few days to a few weeks.
- Many new or updated URLs belong in a sitemap with a truthful lastmod, not in a bulk Request indexing queue.
How to request indexing for one new URL
To request indexing, open the Search Console property you manage, paste the exact new URL into URL Inspection, and run the live test. Click Request indexing only if that test does not treat the page as non-indexable. The click is a crawl nudge for one URL, not a ranking action.
Only an owner or full user of the property can submit, and only for a few individual URLs you manage. You cannot request indexing for a URL you do not manage.
Repeating the same URL does not make the crawl faster. The path for many new or updated URLs is a sitemap, covered later.
One clean request — Request indexing is a one-URL crawl nudge an owner or full user may send only after a live test does not mark the page non-indexable.
Does clicking Request indexing guarantee the page will be indexed?
Once that one URL is submitted, the click is easy to overread. No. Request indexing asks Google to crawl the inspected URL. It does not guarantee the page will enter the index, and a daily limit still applies. Google’s own help is direct: submitting a request does not guarantee that the page will appear in the Google Index.
Requesting indexing does not make a page rank faster either. A crawl nudge is not a ranking action, a priority boost, or a reason to publish thinner URLs.
If the goal is a higher position on a query you already rank for, refresh or merge the existing URL instead of minting a new one and spending a request on it. Point that decision to the striking-distance gate already on this site.
Not a ranking trick — Request indexing only asks Google to crawl one URL. It neither guarantees indexation nor moves the page up in results.
How long to wait after you request indexing
Once the request is accepted, plan on about a day in a typical case, and treat up to a week or two as still normal. Google’s URL Inspection help says indexing typically takes a day or so but can take much longer; Search Central says a recrawl can take a few days to a few weeks. Do not click the button again while you wait. Watch the Index Status report or URL Inspection instead.
Wait, don’t refresh — Wait about a day, allow a week or two, and know a few weeks can still pass. Monitor Index Status or URL Inspection; do not refresh Request indexing.
What is the daily limit for Request indexing, and did Google publish it?
That wait is also why the unpublished cap matters. Google documents a quota on individual URL submissions and a daily limit on Request indexing, but it does not publish the number. The 10, 12, and 15 figures repeated in SEO posts are not from Google's documentation, so do not plan a daily spend around them.
Requesting a recrawl multiple times for the same URL will not get it crawled any faster. Do not automate those repeats.
Keep three quotas separate: the request-indexing limit, the daily limit on inspection lookups for each property you own, and the separate per-property daily limit on live tests. Hitting one is not a reason to hammer another.
Unpublished cap — Google confirms a Request indexing quota but never publishes the number, and a second click on the same URL does not speed the crawl.
What to check before you spend a Request indexing click
A scarce daily slot is the reason to be picky. Spend the click only if you manage the URL, you are an owner or full user, the change is significant, you have not already requested this URL, and a quick live check finds no immediate indexing errors.
If the live test treats the page as non-indexable, you cannot submit it. Fix the block, then run the live test again. Do not retry the same URL to force the queue.
A passing live test is not proof of indexing. It does not check duplicates, quality and security guidelines, manual actions, removals, or temporary blocks.
If Google selects another URL as canonical, the inspected page is a duplicate and will not be indexed. Spend nothing until the canonical is the URL you intend to own.
Before you click — Request indexing only after a clean live test on a significant change you have not already submitted. A pass does not mean the page will be indexed, and a non-indexable or non-canonical URL should not be queued at all.
Should I request indexing for every article an automated publisher ships?
That same gate answers the automation question. Should you request indexing for every article an automated publisher ships? No. Request indexing is for a few individual URLs, not a step in the publish pipeline.
When should you submit a sitemap with lastmod instead? For many new or updated pages. Google’s documented method for large numbers of URLs is a sitemap, not repeated URL Inspection requests, with the updated pages marked by lastmod.
Google ignores sitemap priority and changefreq. It uses lastmod only when that date is consistently and verifiably accurate. Set it for a significant change — primary text, structured data, or links — not a sidebar or footer tweak. A false recent date trains Google to ignore the field.
Keep the manual click for the exception that already passed the live-test gate. Send ordinary publish volume through the sitemap, and send non-Google change pings through the IndexNow workflow already published on this site.
The split — An automated publisher does not request indexing for every article it ships. Ordinary new and updated URLs go in a sitemap with an accurate lastmod; the button stays a one-URL exception.
Can the URL Inspection API, Indexing API, or IndexNow submit Request indexing?
Those same automation paths still cannot press Request indexing for you. The Search Console URL Inspection API returns only the indexed version of a URL. It cannot test whether a live URL is indexable, so it cannot replace the in-product live test or the Request indexing click. Quota is 2,000 queries per day and 600 queries per minute per property. Use it to read status, not to submit a crawl.
The Indexing API is not a substitute for blog and article URLs. It can only be used to crawl pages with JobPosting or BroadcastEvent embedded in a VideoObject. The default publish quota is 200 URL_UPDATED or URL_DELETED requests per project per day, resetting at midnight Pacific Time. Refuse it for ordinary articles; this site’s IndexNow versus Indexing API piece spells out that boundary for automated publishing.
An IndexNow ping does not replace Request indexing for Google. Documented endpoints are the global endpoint plus Amazon, Bing, Naver, Seznam.cz, Yandex, and Yep. Google is not on that list. Notifying Google still means Search Console, a sitemap, or a natural crawl, not an IndexNow ping.
What "URL is on Google" actually means
"URL is on Google" means the URL is eligible to appear, not that it is appearing. Google's URL Inspection help is explicit: the label does not guarantee the page will show in Search results, because the tool does not check every condition required to appear.
Do not read that status as proof the request worked, a ranking win, or a reason to request the URL again. If the page should not own the query, fix the canonical or the content job so a support task and a concept post are not both chasing it.
Eligible, not visible — "URL is on Google" only means the URL may appear. It is not a ranking result, and it is not a reason to spend another Request indexing click.
Key Takeaways
Put significant new and updated URLs in an accurate sitemap, reserve Request indexing for the live-test exception, and use this site’s IndexNow workflow for non-Google change pings.