How Long Does Google Take to Index a New Page in 2026?

Google does not index a new page on a fixed timetable, and it has never promised one. A well-linked page on a site that Google already visits often gets crawled and indexed within days. A page that sits on a new, slow or thin site, or that nothing links to, can wait weeks, and some pages are crawled but never indexed at all. Google has not published a single number for "a new page", so anyone who quotes you an exact figure is guessing.

The question is back in the news because, according to Search Engine Journal's SEO Pulse of 10 October 2026, Google's Gary Illyes showed timing ranges for crawling, indexing, site moves and core update recovery at a Search Central event in Barcelona on 2 October. That gives business owners a better sense of what "normal" looks like, and of when waiting stops being sensible and fixing starts.

Below is the honest answer, what slows indexing, and a launch routine for a new service page, blog post or city page: before you publish, on the day, and after a week.

What Google shared about crawl timing ranges in October 2026

Search Engine Journal reported that Illyes showed timing ranges for crawling, indexing, site moves and core update recovery. The figures it quoted came from an attendee recap of the talk, and only two of them had numbers attached:

• Site moves: one to three months in the typical case, and six months to more than a year at the slowest.
• Core update recovery: about three to six months as typical, and six months to a year in the slowest cases.

The article did not give a numeric range for crawling or indexing a single new page, and it noted that the recap does not state the sample size, the time period, or what "typical" means. Treat these as ranges, not deadlines: a typical case and a slow tail.

Google's Search documentation updates log also records that on 10 July 2026 it updated the canonicalisation troubleshooting guide "to provide better expectations about how long it takes for canonicalization changes to take effect". Google is setting expectations, not promising speed.

Why there is no fixed answer to "how long does Google take to index a new page"

Indexing happens in stages. Google has to discover the URL (through a link or a sitemap), crawl it (Googlebot fetches the page), render it, and then decide whether to index it, meaning store it so it can appear in results. The last stage is a decision, not a formality.

Crawl speed depends largely on crawl demand: how much Google wants to visit your site. In the same SEO Pulse, Search Engine Journal reported John Mueller saying crawl demand often depends on how the site's quality is perceived. A Mumbai fintech whose blog Googlebot visits regularly will see new posts picked up faster than a brand-new Dubai property site.

What to check afterwards: look at how quickly your last few pages were indexed. That history is a better guide for your site than any industry figure.

Before you publish: make the page worth indexing

The most common reason a new page is not indexed is not speed. Google simply does not see enough reason to keep it. Check three things.

• Is it different from pages you already have? A Jaipur jeweller's new "Gold bangles" page that repeats the "Gold jewellery" page with one word changed is a duplicate. Add what is specific: designs, price ranges, care advice, real photographs, real customer questions.
• Is it thin? A heading and two lines of text is easy for Google to skip.
• Is the canonical tag right? It tells Google which version of a page is the main one. Templates often copy another page's canonical by mistake.

What to check afterwards: view the page source and confirm the canonical URL is the page's own address.

Before you publish: remove anything that blocks indexing

Two settings stop indexing completely, and both are easy to leave on after building a page on a staging site.

• A noindex tag. A robots meta tag (or X-Robots-Tag HTTP header) that tells Google not to index the page. Google updated its documentation on 24 March 2026 on how it processes robots meta tags outside the HTML head, so do not assume a misplaced tag is ignored. For JavaScript sites, its December 2025 update advises: "don't use a noindex tag in the original page code".
• A robots.txt block. If robots.txt disallows the page's folder, Googlebot cannot crawl it.

What to check afterwards: view the live page source, search for "noindex", and check the HTTP response headers too, where a noindex is invisible on the page.

Before you publish: link the new page from pages Google already visits

Internal links, links from your own pages, are how Google discovers most new URLs and judges which ones matter. A page reachable only through the sitemap looks unimportant.

• Link a new service page from the main services page, and from the menu if it is a core offer.
• Link a new blog post from two or three older posts on the same subject, with descriptive anchor text.
• Link a new city page from your locations page and the relevant service page.

Check mobile too. In November 2024 Google added a crawl budget note that "the discovery of new pages can be slower if the mobile version does not include all the links". Many sites hide menu or footer links on mobile. If you are changing URLs as part of the launch, follow our guide to 301 and 302 redirects so old links keep working.

What to check afterwards: on your phone, try to reach the new page from the homepage in two or three taps.

Same day: add the page to your XML sitemap

An XML sitemap is a file listing the URLs you want search engines to find. Most WordPress and Shopify setups update it automatically, but confirm the new URL appears, that it is the final URL (not a staging or redirected one), and that the sitemap is submitted in Search Console.

If a valid sitemap shows "Couldn't fetch", Search Engine Journal reported Mueller giving two causes: host load and crawl demand. Often the problem is not the file but how much Google wants to crawl your site.

What to check afterwards: open your sitemap URL in a browser and search for the new page's address.

Same day: inspect the URL and request indexing in Search Console

Google's own documentation points people to the URL Inspection tool because it holds the most up-to-date version of your page that Google has. Paste the new URL into the inspection bar at the top of Search Console and it will tell you whether the URL is on Google, whether crawling is allowed, and which canonical Google has chosen. Use the live test to confirm Googlebot can fetch the page now.

If the live test is clean, use Request indexing. It asks Google to crawl the page; it does not guarantee indexing or a faster ranking, and requesting the same URL again and again does not help. Do it once, after the page is final.

No shortcut exists here: Google's Indexing API is documented for specific page types such as job postings, not ordinary service pages or blog posts.

What to check afterwards: note the date you requested indexing so you can judge progress fairly a week later.

Check that a slow server is not holding indexing back

Host load, how much strain your server can take, is one of the two causes Mueller gave for sitemap fetch problems. A slow or error-prone server makes Google crawl more cautiously. A Delhi D2C brand on cheap shared hosting that slows during a sale may see crawling slow exactly when it launches new collection pages.

Fix server errors and keep the main content in the HTML rather than loading it only through scripts. Our guide to Core Web Vitals in 2026 covers speed for visitors; for indexing, what matters is a fast, error-free response to Googlebot.

What to check afterwards: in URL Inspection, the live test shows whether the page was fetched successfully. Repeated failures point to the server.

After a week: why is my page not indexed?

If the page is still not on Google after about a week, stop waiting and diagnose. Inspect the URL again, then open the Pages report in Search Console, which groups URLs by the reason they are not indexed. Two common statuses mean different things:

• Discovered, currently not indexed: Google knows the URL but has not crawled it. Usually crawl demand or the server. Strengthen internal links and check server health.
• Crawled, currently not indexed: Google fetched the page and chose not to index it for now. Usually quality or duplication. Improve the content, differentiate it, and link to it from stronger pages.

Also check the canonical Google chose. If it picked a different URL, it sees your page as a duplicate.

What to check afterwards: once you have made changes, use the live test again and request indexing once.

Launching city pages without creating near-duplicates

City pages are where small businesses most often hit "crawled, currently not indexed". A Dubai property firm that publishes ten area pages with the same text and a swapped area name is creating near-duplicates, and Google may index one or two and ignore the rest. The pattern sits close to tactics in 8 outdated SEO tactics that could get your website penalised.

Publish a city page only when you have something local to say: address or service area, local projects, prices, delivery times, photographs. Launch in small batches and watch the Pages report before adding more.

What to check afterwards: if most of a batch is not indexed after a few weeks, improve those pages before publishing the next batch.

How to check whether it is working

• URL Inspection: confirms whether each new URL is on Google and which canonical Google selected.
• Pages report: track whether new URLs move from "not indexed" to "indexed", and whether the count of "crawled, currently not indexed" pages grows after a launch.
• Sitemaps report: confirms your sitemap was fetched successfully, not "Couldn't fetch".
• A manual search: search Google for a distinctive sentence from the page in quotation marks. This is a rough check, not a guarantee, so trust URL Inspection over it.
• A launch log: a sheet with URL, publish date, request date and indexed date shows your site's normal range. If an agency does this, see how to read the reports your marketing agency sends.

Indexing is step one. Whether the page then gets shown and cited is covered in our checklist for getting cited in Google AI Mode.

Frequently asked questions

How long does Google take to index a new page in 2026?

Google has not given a single figure for a new page. On a site Google crawls often, a well-linked page is commonly indexed within days; on a new or weak site it can take weeks or not happen at all. The numeric ranges reported from Gary Illyes' October 2026 talk covered site moves and core update recovery, not individual pages.

Does Request indexing in Search Console make Google index my page faster?

It asks Google to crawl the URL, which can help a new page get discovered sooner. It does not force indexing, and Google can still decide not to index the page. Requesting the same URL repeatedly does not speed things up.

Why does my page say "crawled, currently not indexed"?

Google fetched the page but chose not to add it to the index for now. This usually points to thin content, a page too similar to others on your site, or weak internal links. Improve the page and its links, then request indexing once.

Should I submit my sitemap every time I publish a new page?

No. Submit the sitemap once in Search Console and make sure it updates automatically when you publish. What matters on launch day is that the new URL actually appears in the sitemap and that the sitemap fetches without errors.

If new pages on your site are taking weeks to appear, or your Pages report is filling up with "not indexed" URLs, a technical review usually finds the cause quickly. Sage Media's SEO services cover indexing audits, internal linking and launch routines for new pages, and if you are based in Rajasthan you can talk to our SEO team in Jaipur.