How Long Does Google Search Console Take to Index a Page?
By Toy Wen Da, Co-Founder · Updated · 6 min read · scored 97/100
Usually a few hours to a few days after you click Request Indexing, though a page with quality or technical problems can take longer. Search Console doesn't index anything itself; it only reports status, so the URL Inspection tool is where you find out what's holding a page back.
Before you keep refreshing, run the page through the free Googlebot Simulator at SearchBlueprint. It fetches the URL the way Googlebot does and shows the raw HTML, status code and rendered content Google would see. That catches blockers such as a stray noindex tag, a JavaScript rendering gap or a server error, which Search Console's status message won't always spell out.
What "indexed" actually means in Search Console
Google's documentation defines an indexed page as one Googlebot has visited, analyzed and stored in the Google index, and only indexed pages are eligible to appear in search results (Google Search Central). Search works in three stages: crawling (fetching the page), indexing (understanding and storing it) and serving (showing it for relevant queries). A page can clear one stage and stall at the next.
So Search Console can report a page as indexed while you still can't find it in a live search, because being indexed and ranking are separate questions. A brand-new page that takes weeks to show up anywhere in results has a ranking timeline problem, which is covered in how long a new website typically takes to rank on Google.
The fix inside Google Search Console, step by step
If a page isn't indexed, work through these steps in order:
- Open URL Inspection and paste the exact URL. Search Console will show "URL is on Google" or "URL is not on Google," along with the reason.
- Read the status message carefully. Common ones include "Discovered - currently not indexed," "Crawled - currently not indexed" and "Page with redirect."
- Check the Coverage (Indexing) report under the Index section. If the same issue appears across many URLs, the cause is site-wide rather than confined to one page.
- Fix the underlying problem first. A noindex tag, a robots.txt block or a canonical pointing elsewhere needs fixing before resubmitting does anything.
- Click Request Indexing from the URL Inspection tool once the fix is live. Google re-crawls the URL and re-evaluates it.
- If you've fixed several URLs at once, submit or resubmit your sitemap under the Sitemaps report, which helps Google rediscover them in bulk.
- Wait, then recheck. Re-run URL Inspection a few days later instead of requesting indexing repeatedly on the same URL.
When Search Console's own tools are enough and when they aren't
Requesting indexing works well for isolated cases and poorly for patterns.
| Situation | Is Request Indexing enough? | What to do instead |
|---|---|---|
| One new blog post not showing up | Yes, inspect and request indexing | Wait 1-7 days, then recheck |
| A handful of updated pages after a redesign | Yes, page by page | Resubmit the sitemap too |
| Dozens of URLs stuck at "Discovered - currently not indexed" | No | Investigate crawl budget, site speed and content quality site-wide |
| Whole sections of the site missing from the index | No | Check robots.txt, internal linking and server response codes |
| Pages indexed but not ranking for target terms | No, this isn't an indexing problem | Review content and backlink quality |
A single stubborn URL is a Search Console job, while a recurring pattern across many URLs calls for a technical SEO audit. If you also suspect low-quality backlinks are dragging on the whole site's crawl trust, finding them with only Search Console data (no paid tool) is worth doing alongside this check.
Common causes of Google Search Console indexing delays
| Cause | How it shows in Search Console | Typical fix |
|---|---|---|
| Noindex meta tag or header | "Excluded by 'noindex' tag" | Remove the tag, request indexing |
| Blocked by robots.txt | "Blocked by robots.txt" | Update robots.txt rules |
| Low-quality or thin content | "Crawled - currently not indexed" | Expand or rewrite the content |
| Duplicate or wrong canonical | "Duplicate, Google chose different canonical" | Set the correct canonical tag |
| Server errors or slow response | "Server error (5xx)" | Fix hosting or server config |
| New page, not yet discovered | "Discovered - currently not indexed" | Add internal links, submit sitemap |
Common mistakes to avoid
- Resubmitting the same URL daily. Repeated requests don't speed anything up and can look like spam.
- Skipping the stated reason. "Crawled - currently not indexed" almost always points to content quality rather than a technical fault.
- Leaving robots.txt rules or noindex tags in place from a staging environment.
- Treating indexing and ranking as the same problem. A page can be indexed and still rank nowhere near page one.
- Never checking JavaScript rendering. If content only appears after scripts run, Google may see a mostly empty page.
FAQs
How long does Google Search Console take to index a new page after I request it?
Google doesn't commit to a fixed timeline. Many pages get crawled within a few hours to a few days of a request, but full indexing depends on the page's quality, the site's crawl activity and whether any technical blockers exist.
Why does my page still say "Discovered - currently not indexed"?
It usually means Google found the URL but hasn't prioritized crawling it yet, often because of limited crawl budget, thin content or weak internal linking to that page.
Does requesting indexing multiple times make it faster?
No. One request adds the URL to the crawl queue, and repeating it doesn't move the URL up and can waste your limited daily requests.
Can a page be indexed but still not show up in search results?
Yes. Indexing only means the page is stored in Google's index, and whether it ranks for a query depends on relevance and quality signals evaluated during serving.
Is submitting a sitemap faster than requesting indexing one URL at a time?
For many new or updated pages at once, yes, because a sitemap tells Google about all the URLs in one submission instead of through one-by-one manual requests.
Check the status, then fix the cause
Open URL Inspection for the exact page you're worried about. The status message there names the real blocker, which is the answer to how long Google Search Console will take to index it. If the status looks ambiguous, run the page through the Googlebot Simulator first, then talk to the team at SearchBlueprint through a free sample SEO report to see what else might be slowing your site's indexing down.
Resources / References
Sources
About the author
SearchBlueprint researched, wrote and scored this article with the content pipeline our customers run on their own sites. The score in the byline is what our content engine gave this page before it published. Nothing here is reviewed by hand, which is the point: it is the product's output, published where anyone can check it.