Request Indexing
Learn how Google indexes pages and how to manually request indexing through Google Search Console for your content.
Google does not index every published page. Publishing a page or submitting an indexing request does not set a deadline for indexing.
According to Google’s official guidance, crawling can take a few days to a few weeks. This is not an indexing deadline, and even after crawling, there is no guarantee that a page will be indexed or appear in search results.
Manual Indexing Request
You can manually request indexing for a specific URL through Google Search Console. After submitting a request, monitor progress with the URL Inspection tool or the Page indexing report.
Notes
-
Requesting indexing repeatedly for the same URL does not make crawling faster.
-
Submitting a request does not guarantee that your page will be indexed.
-
There is a daily limit to how many indexing requests you can submit. If you need to index many pages, it is more efficient to submit a sitemap.
Steps to Request URL Indexing
-
Go to the URL Inspection tool in Google Search Console.
-
Enter the page URL you want to inspect.
-
On the result page, click Request Indexing.
-
If the real-time test confirms the page can be indexed, it will be added to the indexing queue.
If the test determines the page cannot be indexed, you will not be able to submit a request.
Does inblog Request Indexing for You? (Indexing API)
The sitemap is automatic. Indexing requests for individual posts are not.
- Your sitemap (
your-blog-address/sitemap.xml) is built from your live posts rather than from a stored file, so publishing or editing a post is reflected in it with no extra action. You never need to rebuild or resubmit the sitemap. A response may be served from cache for a few minutes, so a change can take a short while to appear. - inblog does not submit indexing requests for each URL through the Google Indexing API. Google officially supports that API for job posting and live stream pages only, so regular blog posts are out of scope for it.
To speed indexing up, requesting it yourself in Search Console is the supported path. Even then, indexing is not guaranteed.
"Discovered – currently not indexed" in Search Console
This is usually not an error. Google knows the URL but has not gotten around to crawling it. Two similar-looking states mean different things.
| Search Console status | Meaning | How to read it |
|---|---|---|
| Discovered – currently not indexed | The URL was found (e.g. via your sitemap) but has not been crawled yet | The sitemap is fine. Google has given the page a low crawl priority |
| Crawled – currently not indexed | Google crawled the page but decided not to index it | More likely a judgement about the content itself |
If the status is Discovered, sitemap submission and URL discovery are already done, so resubmitting the sitemap changes nothing. What actually helps:
- Add internal links to the post from pages that are already indexed. When nothing links to the blog at all, Google assigns it a low crawl priority. Linking to the blog from your main site's navigation or footer has the largest effect.
- Submit a Request Indexing in the Search Console URL Inspection tool. This is a supporting step that moves the queue along.
- Check that the topic has real search demand and does not duplicate your other posts.
Allow 2–4 weeks after making these changes before re-checking the index status to judge the effect. Backlinks can help with crawling and trust, but they are not a requirement for a post to be indexed.
Last updated 2026-09-10