How long before a new landing page shows up on Google?

Publish a landing page and type its title into Google five minutes later to find… nothing: this reflex triggers a common worry that's rarely justified. Google doesn't know a page exists the moment it goes live — it first has to discover it, crawl it with its bot, then decide whether to add it to its index. Each of these three steps takes a different amount of time depending on the nature of the page, the authority of the site hosting it, and how well it's linked to the rest of the web. This guide covers a realistic timeline and the concrete levers to shorten it, without confusing indexing with ranking — two very different things.

Discovery, crawl, indexing: three steps that often get mixed up

According to Google Search Central's official documentation, a page goes through several stages before it can appear in search results. First, discovery: Google has to learn the URL exists, either because it's listed in a submitted sitemap or because a link from an already-known page points to it. Then crawling: Googlebot visits the page to read its content. Finally, indexing: Google decides whether to add the page to its index, the database search results are built from. A page can be discovered and crawled without ever being indexed, if its content is judged too thin, duplicate, or not relevant enough. And an indexed page doesn't necessarily rank well: indexing only guarantees the page exists for Google, not that it ranks — ranking depends on other factors, covered in our guide to landing page SEO.

How long it actually takes

There's no guaranteed timeline — Google says so explicitly in its own documentation — but clear patterns emerge depending on the starting situation.

• A few minutes to a few hours: a page added to an already-established site that Google crawls frequently (news, a large e-commerce site), and linked from a high-traffic page.
• 1 to 7 days: the most common case for a landing page added to an already-indexed, mid-sized site, with an up-to-date sitemap and at least one internal link pointing to it.
• Several weeks: an isolated page with no inbound links, on a recent or rarely crawled domain — the typical scenario for a landing page published alone, without a blog post or internal linking around it.
• Never, or very late: a page mistakenly blocked in robots.txt, accidentally tagged noindex, or judged too close to content already existing on the site.

Why Google doesn't recrawl everything, all the time

This delay isn't arbitrary: it comes from a trade-off search engines constantly have to make between index freshness and computing cost. A study that became a reference in the field, Junghoo Cho and Hector Garcia-Molina's "Effective Page Refresh Policies for Web Crawlers" (ACM Transactions on Database Systems, 2003), mathematically models this trade-off: a search engine can't crawl the entire web continuously, so it has to allocate its crawl budget by prioritizing pages based on their estimated importance and their likely rate of change. A brand-new page, on a site with no track record of frequent updates, ends up mechanically lower in that queue than a page on a site Googlebot visits several times a day — hence the sometimes very wide gap in observed delays from one site to another.

Why an internal link (really) speeds up discovery

The most reliable way to shorten the discovery phase is also the oldest: a link from a page Google already knows and visits regularly. This principle traces directly back to the foundations of web search: in "The PageRank Citation Ranking: Bringing Order to the Web", Larry Page, Sergey Brin, Rajeev Motwani and Terry Winograd (Stanford InfoLab, 1998) describe how a search engine discovers the web by following links from page to page, and how a page's perceived importance — and therefore its crawl priority — largely depends on the number and quality of links pointing to it. An isolated landing page, never mentioned anywhere else on the site, behaves for Googlebot like an island with no bridge: it will eventually be found via the sitemap, but far more slowly than a page linked from day one from a blog post or the homepage.

5 concrete levers to speed up indexing of a new landing page

1. Submit (or refresh) the XML sitemap in Google Search Console. A Next.js site with generateSitemap automatically adds any new static route to sitemap.xml — but Google still needs to come back and read it, which you can trigger from Search Console instead of waiting for the bot's next natural pass.
2. Create at least one internal link from a page that's already indexed and gets traffic — a blog post that links to the new landing page, or a link from the homepage. It's the most direct lever, and it lines up with what the Page et al. study cited above shows.
3. Request manual indexing via Search Console's URL Inspection tool ("Request indexing"). It's not a guarantee of an immediate crawl — Google says so itself — but it puts the page earlier in the queue than if it waited for a natural crawl.
4. Share the link publicly once the page is live (social media, newsletter, a mention on another site): every place the link appears is a new possible entry point for discovery, independent of the crawl schedule Google runs on your domain alone.
5. Check for technical blockers before assuming it's just a delay: a noindex tag left over from a staging environment, an overly restrictive robots.txt, or content nearly identical to another page on the site can block indexing indefinitely, no matter how much time passes.

Indexing isn't always the right battle

Not every landing page is meant to be indexed, and it's worth telling the two apart before worrying about a delay. A page built purely for an ad campaign — Google Ads, Meta Ads, an email campaign — doesn't need organic visibility at all: traffic already arrives through a direct link, and what matters is load speed and consistency with the ad, not Google ranking. A landing page meant to capture search traffic (a local service page, a product page), on the other hand, benefits from content built around it — one or two blog posts that answer the audience's pre-purchase questions, with a natural link to the page, exactly the logic covered in our article on landing page SEO. Internal linking serves two purposes there at once: speeding up indexing and signaling the page's real topic to Google.

The redesign case: no need to start from zero

Replacing an already-indexed landing page with a new version changes the picture: it's no longer discovery from scratch, but an update to a URL Google already knows, usually recrawled faster. The real risk in that case isn't the indexing delay but losing the ranking already earned if the URL changes without a proper redirect — a topic covered in detail in our article on redesigning a landing page without losing its SEO. Adding consistent structured data also helps Google quickly understand the content of a newly crawled page; see our guide on structured data (Schema.org) to go further.

A clean deployment makes each of these levers easier: on Vercel, every new Next.js route automatically regenerates the sitemap and serves the page instantly, with no manual build step to forget — covered in our article on deploying a Next.js landing page on Vercel. That's exactly the architecture behind the 10 LanderKit templates (€89 each, €229 for the full bundle): each one, from the local agency template built for local SEO to the real estate template designed to capture qualified search traffic, ships as Next.js source code ready to be linked, indexed, and measured from day one — with no visual builder generating URLs you can't control.