Request Indexing asks Google to consider crawling a URL; it doesn't place the URL in the index. Google decides whether and when to crawl the page, which URL to treat as canonical, and whether to index it. Where you do not control the site, you can't submit someone else's page via your own Search Console property.
How to Submit a URL to Google in Search Console
For a new page or an significant update to an existing one, the official Google Search Console request indexing workflow is short:
- Open Google Search Console and sign in with a Google account that has owner or full-user access to the relevant property. Where the site has not been added and verified, complete that process prior to proceeding.
- Select the property that contains your URL. Check the full address, such as its protocol, hostname, path, and any meaningful URL parameters. Inspect the page you want Google to index, instead of assuming a homepage or another version represents it.
- Enter the exact URL in the URL Inspection field. Search Console retrieves Google's available information for that address. The indexed record may describe a previous crawl, not the page exactly as it appears now.
- Check for obvious obstacles. Where needed, use the live URL test to investigate current accessibility. A successful live test isn't proof that the page is already indexed, and it doesn't override Google's canonical selection.
- Select Request Indexing when the action is available. Google performs a preliminary check for indexing problems prior to adding an eligible URL to its indexing queue. Where the live test identifies the page as non-indexable, fix the reported issue where possible prior to trying again. A request confirmation means the URL was submitted to the queue, not that Google has crawled or indexed it.
- Return later to inspect the result. Keep the submitted URL and request date for your own records, especially when you're managing multiple newly published or substantially updated pages.
The official Google guidance on requesting a recrawl explains the request process and its limitations. You don't have to buy a third-party submission service to use Search Console for a verified property.
Before You Request Indexing
A manual indexing request is optional, not a required step for every published page. Google may discover URLs via normal crawling, internal links, and sitemaps. Use Request Indexing when you have a reason to ask Google to revisit a particular page. Make these decisions prior to submitting it:
| Your Situation | What to Check | Best Next Step |
|---|---|---|
| The URL is already indexed and the page has not materially changed | Confirm the indexed state in URL Inspection | No new request is normally needed; request a recrawl when a meaningful update or correction makes it appropriate |
| You own or manage the site | The URL belongs to a property where you have appropriate Search Console access | Inspect the exact URL and request indexing if appropriate |
| You manage the page but lack Search Console access | Property verification and user permissions | Ask a verified owner for access or complete verification; don't look for an unofficial Google submission form |
| The URL is on someone else's site | Who controls the source page and its Search Console property | Ask the publisher to investigate or request a crawl; your property may't authorize their URL |
| The page is unavailable or deliberately excluded | HTTP response, robots restrictions, noindex, redirects, and canonical signals |
Resolve the underlying condition where you have control prior to requesting another crawl |
| The page is live and indexable but has not appeared in Google | Whether Google has discovered or crawled it, and whether another canonical was selected | Use URL Inspection to find the relevant evidence prior to choosing an action |
An HTTP 200 response alone isn't proof that the page should be indexed. A page may load in your browser yet carry a noindex directive, point to a distinct canonical URL, or provide content Google elects not to index. A redirecting URL may also be distinct from the final page you intended to submit.
Blocking crawling may prevent Google from evaluating page-level directives. Fix technical or canonical problems instead of expecting a request to override them.
For a wider plan covering discovery, internal links, page readiness, and a site's overall indexing setup, see how to index a website on Google.
What Happens After You Request Indexing
Confirmation that Google accepted your indexing request establishes only that the request entered its workflow. It doesn't demonstrate that Googlebot revisited the page or that Google indexed it.
| Stage | What You Know | What You Still Do Not Know |
|---|---|---|
| Request accepted | Google received an eligible request via Search Console | Whether or when Googlebot will revisit the page |
| Page crawled | Google fetched or processed the URL, according to available crawl evidence | Whether Google will keep the content in its index |
| Page indexed | Google's indexed information confirms inclusion of the selected canonical; an alternate URL may not be indexed separately | Whether the page will rank or appear for a particular query |
| Page appears in Search | Google serves a result for a query | That the result will remain visible or hold a particular ranking |
This distinction matters for an updated product page, a rewritten article, or a corrected canonical. Suppose you publish a revised guide and request indexing. Google may crawl the updated URL but select another version as canonical. Another request alone may not change that decision; the more helpful action is to examine the duplicate and canonical relationship.
There's no reliable universal answer to how long a Google indexing request takes. Google may process a request, crawl later, or decide not to index the page. No public service may set a binding Google crawl or indexing deadline. Google's own documentation states that requesting a crawl doesn't promise inclusion in Search.
If You Cannot Request Indexing
If the Request Indexing button is unavailable or your request may't proceed, the next step depends on the particular obstacle.
- You may't open the correct property. Check that you're signed in with an account granted appropriate access. A Google account by itself doesn't give you permission to inspect or request indexing for every site.
- The URL is outside your property. Switch to the right verified property if you control it. Otherwise contact the site owner. Buying a backlink on a publisher's site doesn't give you that publisher's Search Console permissions.
- The live URL has an accessibility or indexing problem. Investigate its response, robots handling,
noindexdirective, redirect, or canonical. Resolve what you may control, then use URL Inspection again. - Search Console indicates a request limit or temporary restriction. Follow the current message in the interface and try again when permitted. Google applies limits, but an old quota number or an arbitrary waiting period isn't a reliable instruction.
- You have already submitted the same URL. Repeatedly pressing the button isn't a way to force higher crawl priority. Revisit the request after a meaningful page change or when new diagnostic evidence warrants it.
- The page belongs to someone else and you have no Search Console access. There's no equivalent universal official single-URL submission button that bypasses ownership requirements. You may ask the publisher to act, or assess independently available signals without claiming you have submitted the page to Google.
Where the request was accepted but the page continues to be excluded, investigate why a page is not indexed by Google instead of assuming another submission will solve it.
How to Check the Result and What to Do Next
Return to Search Console and inspect the same exact URL, not merely the domain or a similar page. The helpful next action depends on the evidence you find:
- Look at Google's indexed information. Review whether Google reports the URL as indexed and whether it identifies a distinct canonical. The indexed-state report and the live test answer distinct questions.
- Use the live test for present accessibility. A page may be fetchable today while Google's indexed record still reflects an earlier state, or while the URL isn't indexed.
- Match the follow-up to the finding. An inaccessible URL needs a technical fix; a distinct selected canonical needs canonical analysis; a crawled but excluded URL may need deeper content or duplication investigation.
- Recheck after something meaningful changes. Compare the page condition and Search Console evidence, instead of treating repeated requests as measurable indexing progress.
For an explanation of the indexed record, live test, and individual diagnostic fields, use our Google URL Inspection Tool guide. This matters especially when an interface message seems to contradict what you may see in a browser.
What if you don't own the site? Nuclear Link Indexer's independent Google Index Checker may check a URL for a search-result-based indexing signal, such as publicly accessible pages on other sites. It is a separate paid check, not Google's URL Inspection or an indexing request. Since the method relies on limited site: search results, a missing match doesn't conclusively prove that Google has excluded the URL.
Submit One URL or Use a Sitemap?
Select the route according to the size of the task and who controls the site.
| Your Task | Appropriate Route | What It Does Not Guarantee |
|---|---|---|
| Request a crawl of one significant new or updated page | Search Console URL Inspection and Request Indexing | A Googlebot visit, index inclusion, or ranking |
| Make many owned-site pages discoverable | A sitemap submitted and maintained via Search Console | That Google will crawl and index every listed URL |
Where you're managing dozens or hundreds of eligible URLs, learn how to submit and monitor a sitemap. A sitemap is a discovery resource, not a batch of guaranteed indexing commands. For a single corrected URL, an individual request may be the more direct way to signal that a page has changed.
Google also offers an official Indexing API, but it's restricted to supported content types, such as qualifying JobPosting pages and BroadcastEvent embedded in VideoObject pages. It isn't a general submission API for regular articles, product pages, or backlink donor URLs. Check Google Indexing API eligibility prior to considering that developer workflow.
Where you specifically need an independent, project-based URL delivery service, Nuclear Link Indexer's URL Indexer is a standalone option with its own processing and reporting. It isn't an official Google Search Console request, and delivery doesn't promise Google indexing.
For a page you own, start with Search Console. Inspect the URL, request indexing when appropriate, and follow the evidence instead of the number of requests submitted.