Google does not commit to a number. Its documentation says crawling can take anywhere from a few days to a few weeks, and that being crawled does not guarantee being indexed. In practice, a new page on an established, well linked site is often indexed within hours to a few days, while a page on a brand new domain commonly takes one to several weeks. Large sites can need months before most of their pages are in.
Anyone who quotes you an exact figure ("Google indexes pages in 4 days") is giving you an average from their own sites, not a rule. What you can do is understand what drives the delay and shorten the parts you control.
Three waiting periods, not one
"Time to index" is really three delays stacked on top of each other:
| Stage | What you are waiting for | What controls the wait |
|---|---|---|
| Discovery | Google finding out the URL exists | Sitemap freshness, links from pages Google crawls often, manual submission |
| Crawl | Googlebot fetching (and rendering) the URL | Crawl demand for your site, server capacity, the URL's apparent importance |
| Indexing | Google processing the page and deciding to keep it | Content quality and uniqueness, canonical signals, rendering complexity |
You can see where a specific URL is by inspecting it in Search Console:
- "URL is unknown to Google": still waiting for discovery.
- "Discovered - currently not indexed": discovered, waiting for a crawl.
- "Crawled - currently not indexed": crawled, and either still being processed or rejected.
- "URL is on Google": done.
This matters because the remedies differ. A sitemap fixes discovery and does nothing for a page that was crawled and declined.
Realistic expectations by situation
These ranges come from what Google states plus what is typical in practice. Treat them as orientation, not promises.
| Situation | Typical experience |
|---|---|
| News publisher or very active site, new article linked from the homepage | Minutes to hours |
| Established site, new page linked from crawled pages and in the sitemap | Hours to a few days |
| Established site, new page in the sitemap only, no internal links | Days to weeks, sometimes never |
| Brand new domain, homepage, with Search Console and a few external links | A few days to two weeks |
| Brand new domain, deep pages | Weeks |
| Large site publishing thousands of pages at once | Weeks to months for the bulk, some never |
| Updated content on an existing indexed page | From hours to several weeks, depending on how often Google recrawls that page |
JavaScript adds a possible extra step. Google processes JavaScript pages in two phases: it crawls the HTML first and queues the page for rendering. Google says the page can stay in the render queue for a few seconds, but it can take longer. If your content or links exist only after rendering, that delay is added on top. Server-rendered HTML avoids it.
What makes indexing faster
Signals that your site deserves frequent crawling
Google crawls more when it expects to find new, valuable things. Sites that publish regularly, get linked to and have a history of pages worth indexing are visited more often. There is no setting for this. It is earned over months.
Strong internal links from frequently crawled pages
The fastest route into the index for a new URL is a link on a page Googlebot visits every day: your homepage, a main category, a popular article. If new content appears there at publication time, discovery and crawl often happen the same day.
A clean sitemap with truthful lastmod
Google uses <lastmod> when it is consistently and verifiably accurate. If every URL shows today's date on every request, Google learns to ignore it. If it only changes when the page changes, it becomes a useful recrawl signal. Validate your file with the sitemap validator.
<url>
<loc>https://www.example.com/blog/new-post</loc>
<lastmod>2026-09-02T09:30:00+00:00</lastmod>
</url>
A fast, reliable server
Google's crawl capacity limit goes up when the site responds quickly and down when it slows or returns server errors. Check Settings > Crawl stats for average response time and the share of 5xx responses.
Request indexing for single pages
URL Inspection > Request indexing puts the URL in a priority queue. It is the most direct supported action for an individual page. It has a daily quota and does not scale, as covered in Request indexing limits.
The Indexing API, for eligible pages
For JobPosting pages and livestream BroadcastEvent pages, the Indexing API is the fastest supported path, designed for content that expires quickly. It is officially limited to those two types, with a default of 200 publish requests per day per project. The Google Indexing API guide explains the trade-offs of using it for anything else.
What makes indexing slower
- Orphan pages. URLs with no internal links are crawled late or not at all.
- Huge numbers of low value URLs. Filters, parameters, internal search pages and thin archives compete with your real pages for crawl attention.
- Slow responses and 5xx errors. Googlebot backs off when the server struggles.
- Blocked resources. If robots.txt blocks the JavaScript or CSS needed to render the content, Google sees an incomplete page.
- Duplicate or near-duplicate content. Google spends time working out canonicals and often indexes only one version.
- Long redirect chains between the URL Google discovers and the final destination.
- New domain with no external links. Google has little reason to prioritise a host nobody references.
- Publishing far faster than Google is indexing you. The backlog only grows.
- Thin pages. They get crawled and then sit in Crawled - currently not indexed, which looks like slowness but is a rejection.
Things that do not speed it up
- Requesting indexing repeatedly. Google says it does not help.
- Resubmitting the sitemap daily. Google fetches known sitemaps on its own schedule.
- Pinging Google. The sitemap ping endpoint was deprecated in 2023 and no longer works.
<priority>and<changefreq>in the sitemap. Google ignores both.- Spending on Google Ads. Ads and organic indexing are unrelated.
- IndexNow. A good idea for Bing, Yandex and other participants, but Google does not take part in it.
- Paid "instant indexing" link blasts. No third party controls Google's index, and spammy links carry their own risk.
How to measure your own indexing time
Your own numbers beat any industry average. A simple way to get them:
- Record the publish date of each new URL.
- A few days later, inspect it in Search Console and note "Last crawl" and whether it is indexed.
- For a second signal, look at the Performance report filtered to that page. The first day with an impression is the latest possible date it was indexed.
- After 20 or 30 URLs you will know your site's normal range, and you will spot quickly when something changes.
Server logs give you the crawl half precisely: the first Googlebot request for a URL is the crawl date.
If you do not want to do this by hand, TurboIndex checks every URL in your sitemaps through the URL Inspection API and records when each one changes status, so you can see your real time to index per section of the site. For planning how long a backlog will take at Google's quotas, there is also an indexing time calculator.
When waiting stops being reasonable
Patience is right in the first weeks and wrong after that. A rule of thumb I use:
| Time since publishing | Status | What to do |
|---|---|---|
| Under 1 week | Anything | Make sure it is in the sitemap and linked. Request indexing if it matters. Wait. |
| 1 to 3 weeks | Unknown or Discovered | Add stronger internal links, check the Sitemaps report for a recent "Last read". |
| 1 to 3 weeks | Crawled - currently not indexed | Check the rendered HTML in the live test. Otherwise wait a little longer. |
| Over 4 weeks | Unknown or Discovered | Treat as a structural problem: linking, URL bloat, server health. |
| Over 4 weeks | Crawled - currently not indexed | Treat as a content or duplication problem. |
| Any time | noindex, robots.txt, redirect, 4xx, 5xx | Do not wait. These never resolve on their own. |
The last row is the important one. A lot of "slow indexing" is a blocker that was there from day one. Run new templates through the indexability checker before launch, and if pages are still missing after a month, go through why is my page not indexed.
Frequently asked questions
- How long does it take Google to index a new page?
- Google's documentation says crawling can take anywhere from a few days to a few weeks, and it gives no guaranteed time for indexing. On established sites that Google crawls often, new pages are frequently indexed within hours or days. On new or rarely crawled sites it commonly takes weeks.
- How long does it take Google to index a brand new website?
- Expect the homepage within days to a couple of weeks once the site is verified in Search Console, has a submitted sitemap and has at least a few links pointing to it. Full coverage of all pages takes longer, often several weeks to a few months, depending on size and quality.
- Does requesting indexing make it faster?
- It usually speeds up the crawl of that one URL, because the request goes into a priority queue. It does not guarantee indexing, there is a daily quota, and Google states that requesting the same URL several times does not make it crawl any faster.
- Why did my old pages get indexed fast and my new ones are slow?
- Common reasons are weaker internal links to the new pages, a growing number of low value URLs competing for crawl attention, slower server responses, or new pages that are very similar to existing ones. Compare the Crawl stats report now with a few months ago to see what changed.
- How long do updates to an existing page take to show in Google?
- The change shows after Google recrawls and reprocesses the page. Pages Google considers important and frequently changing are recrawled daily or faster, and rarely changing deep pages can go weeks or months between crawls. An accurate lastmod in your sitemap and a Request indexing both help.