Publishing a page is the fast part. What happens after you hit publish — discovery, crawling, indexing, ranking, and, if something goes wrong, recovery — runs on clocks you mostly don't control, and for years nobody at Google would put numbers on them. In October 2026 that changed: at the closing day of Search Central Live Deep Dive Europe in Barcelona, Google's Gary Illyes showed a slide of internal timing ranges for each stage, with both a typical case and a slowest case. This guide takes those figures and turns them into something you can plan around. It walks the full lifecycle one stage at a time — why discovery, crawling, and indexing are three separate waits and not one; why a change to an existing page follows a different clock than a brand-new URL; and why a title or snippet edit shows up in days while recovering from a core update can take half a year. It is honest about the single most important caveat Google attached to the whole slide: these are reference points, not deadlines or service levels, and a page can sit at any stage for weeks, months, or never. It explains what actually moves the clock in your favor (and the handful of things that don't, no matter how many SEO threads promise otherwise), how to read the 'Discovered — currently not indexed' and 'Crawled — currently not indexed' states in Search Console without panicking, and why recovery is a volume-and-consistency problem measured in months rather than a switch you flip. The through-line is that the one half of this you genuinely control is production: how fast you can get a verified, quality page published, and how consistently you keep publishing — because the long indexing and recovery clocks only start once the page exists, and a site that publishes steadily gets crawled more often than one that doesn't.
For years, the honest answer to "how long until my page shows up in Google?" was a shrug: anywhere from a few hours to a few weeks, and sometimes never, with no official figures to anchor the guess. That changed on October 2, 2026. On the closing day of Search Central Live Deep Dive Europe in Barcelona, Google's Gary Illyes showed a slide of internal timing ranges for the whole lifecycle — discovery, crawling, indexing, serving changes, site moves, and recovery — each with a typical case and a slowest case. It is the clearest picture Google has ever given of how long each stage actually takes.
Two caveats come attached, and they matter as much as the numbers. First, Google has not formally published these figures with a methodology or a sample size — they come from attendees recapping a conference slide, so treat them as well-sourced reference points rather than documentation. Second, and this is Illyes' own framing: these are reference points, not deadlines, and a delay at one stage carries into the next. Nothing here is a service level Google owes you. With that said, they are the best planning numbers available, and this guide walks the lifecycle one stage at a time so you know which clock you're actually watching.
The biggest misconception is that "getting indexed" is a single event. It isn't — it's a pipeline, and each step has its own clock. A page is discovered, then crawled, then indexed, then served (ranked), and any later change to it runs its own smaller version of the same pipeline. When people say a page is "taking forever," they usually can't say which stage it's stuck at, and the fix is different for each.
Before Google can do anything with a page, it has to know the URL exists. For a brand-new URL, Illyes' typical figure is about 20 hours — the time from the page going live to Google becoming aware of it, usually via a sitemap, an internal link from a page it already crawls, or an external link. The slowest case is "weeks to never," which is the honest ceiling: an orphaned page with no links pointing at it and no sitemap entry can sit undiscovered indefinitely. This is the one stage you most directly influence, because discovery is a linking problem — a page Google can reach from pages it already visits gets found fast.
Crawling is Google fetching the page's content. For a new page, this follows discovery closely. The surprising number is on the other side: refreshing a URL Google already knows about — recrawling it to pick up a change — has a typical figure of about 30 days. That asymmetry trips people up constantly. Publish a brand-new article and it can be crawled within a day; edit an existing article and Google may not come back to re-read it for weeks. How often a given page gets recrawled scales with how important and how frequently updated Google judges it to be, which is why a homepage is recrawled far more often than a three-year-old archive page.
Indexing is Google processing a crawled page: understanding its content, picking a canonical version, and storing it so it can be served. The typical figure here is strikingly fast — about 1.5 hours end-to-end once the processing runs. The catch is in that last clause. The 1.5 hours is the compute, not the wait in line before it; the slowest case is "months, or never." A page can be crawled and then sit unindexed because Google judged it thin, duplicative, or low-value. Indexing is the stage where quality, not plumbing, decides your fate — Google does not promise that every page will be indexed, and it won't index one it doesn't think is worth storing.
Once a page is indexed, changes to how it appears in results run on their own clock. Illyes' figures put title and snippet updates at 1-2 days typical, stretching to several weeks or months in the slow case. So if you rewrite a title tag or a meta description, the SERP usually reflects it within a couple of days on a healthy page — but that assumes Google recrawls the page to see the change, which loops back to the ~30-day recrawl clock for pages it visits less often. The fastest-moving pages get title changes live in a day or two; neglected pages wait for the next crawl.
Every one of these figures has a typical case and a much worse slowest case, and the gap between them is almost always explained by quality and crawl priority, not by a technical setting. A healthy, well-linked, frequently-updated site lives near the typical numbers. A new site with little authority, thin or duplicated content, weak internal linking, or crawl-budget problems lives in the slow lane — and the slow lane's ceiling really is "never." The practical consequence: when a page is taking far longer than the typical figure, the question is rarely "what button do I press?" and almost always "is this page good enough and reachable enough for Google to prioritize?"
This is also why Illyes' "delays in one stage carry into the next" caveat is load-bearing. If discovery is slow because the page is orphaned, everything downstream is late too. If crawling is deprioritized because the site's crawl budget is spent on junk URLs, indexing can't happen on time because the fetch hasn't. The stages are a chain, and the weakest link sets the pace for the whole thing.
If indexing a fresh page is the fast half of this topic, recovery is the slow half — and it's where expectations go most wrong. Two kinds of recovery showed up on Illyes' slide, and both are measured in months.
When a site loses rankings in a Google core update, the typical recovery figure is 3 to 6 months, and the slowest is 6 months to a year. The reason it's so long is structural: core updates run roughly every three to four months, and the improvements you make after being hit often won't be fully re-evaluated until the next core update rolls out. You can fix your content the week after an update lands and still wait months for the scoring to catch up. Recovery is also rarely a clean line up — sites that track rankings through a rollout typically see them dip, partially recover, and dip again before stabilizing, so a steady three-to-four-week climb after a later update is a far more trustworthy signal than any single good day. Telling a stakeholder "we'll be back in a month" after a core-update hit is almost always wrong.
A domain migration or a large-scale URL change has a typical settling time of 1 to 3 months, with a slowest case of 6 months to over a year. During that window, Google is recrawling the old and new URLs, following redirects, and transferring signals — and rankings wobble while it does. The takeaway for anyone planning a migration is to not panic at week two and start changing things; the typical timeline assumes you set up redirects correctly and then wait out the recrawl, which runs on that ~30-day-per-URL refresh clock across the whole site.
Plenty of the lifecycle is out of your hands, but not all of it. The levers that genuinely help cluster around discovery and crawl priority: a clean, current sitemap so new URLs are found without waiting for a crawler to stumble on them; strong internal linking so a new page is reachable from pages Google already visits often; and fixing crawl waste (soft 404s, infinite parameter URLs, duplicate paths) so budget goes to pages that matter. Google's URL Inspection tool and its "Request Indexing" button help with discovery — they signal Google to look at a URL — but they do not guarantee indexing, don't jump a queue on demand, and won't rescue a page Google has decided isn't worth indexing. Request indexing is a nudge, not a lever.
The things that don't work are worth naming, because the SEO underworld sells them constantly. Repeatedly requesting indexing on the same URL does nothing extra. Third-party "instant indexing" services that aren't using a sanctioned API are, at best, noise. And no amount of technical prodding will index a page that fails the quality bar — if a page is "Crawled — currently not indexed," the fix is the content, not the crawl. The single most reliable thing you can do is the least gimmicky: publish genuinely useful pages, link them well, and keep publishing, because a site that ships quality content steadily earns more frequent crawling than one that goes quiet.
Google Search Console's Page Indexing report is where you actually watch these clocks, and two states cause the most needless alarm. "Discovered — currently not indexed" means Google knows the URL exists but hasn't crawled it yet — it's a discovery/crawl-priority state, often temporary on a new or low-authority site, and sometimes a sign Google rescheduled the crawl to avoid overloading your server. "Crawled — currently not indexed" is the more serious one: Google fetched the page and chose not to index it, which is almost always a quality, thinness, or duplication signal rather than a bug. The first often resolves with better internal linking and patience; the second resolves by making the page worth indexing.
The discipline that keeps you sane is matching your reaction to the typical figures. If a new page isn't indexed after a day, that's normal — wait. If it's still not indexed after a week or two on a healthy site, investigate discovery and quality. If a core-update recovery isn't visible after a month, that's expected, not failure — the clock is months, keyed to the next update. Most "Google is broken" panics are just someone watching a months-long clock and expecting a days-long one.
Here is the useful way to think about all of this: the lifecycle has two halves, and you only control one of them. The half Google controls — discover, crawl, index, rank, recover — runs on the clocks above and mostly resists pressure. The half you control is production: how fast you can get a verified, quality page from idea to published, and how consistently you keep publishing. That second half is exactly what Kompozy exists to compress, and it matters here for a specific reason — every one of Google's long clocks only starts once the page actually exists. The faster and more consistently you publish good pages, the sooner each indexing clock starts and the more often it runs.
Kompozy is a full AI content generation and multi-platform publishing engine, and against this topic its relevance is about cadence and quality, not about tricking a crawler — nothing can, and this guide is clear that quality, not plumbing, decides indexing. Concretely: from one idea the engine generates across 18 output formats — blog articles, newsletters, text posts, images, and carousels — so the production bottleneck that keeps most sites publishing sporadically is gone, and a site that publishes steadily is a site Google learns to crawl more often. A consistent Autopilot cadence across the eight social platforms plus blog and email is, in crawl terms, exactly the "frequently updated, worth revisiting" signal that pulls your recrawl interval below the ~30-day typical. You can't order Google to crawl faster; you can earn it by being a site that always has something new worth fetching.
The quality half lines up too, and it's the part that keeps you out of the "Crawled — currently not indexed" slow lane. Every asset is generated against a Persona Brief that fixes voice and enforces a banned-word filter, held to a brand template by HyperFrames, and routed through a per-post review gate before anything publishes — so a human verifies the page is worth indexing instead of flooding the site with thin pages that spend crawl budget and get declined. That same discipline is what recovery rewards: core-update recovery is a months-long, volume-and-consistency problem of shipping substantive, people-first improvements and waiting for the next update to re-score them, and an engine that lets you keep producing reviewed, on-brand content through that window is doing the one thing that actually helps. Kompozy won't shorten Google's clocks — nobody can — but it makes sure they start sooner, restart more often, and never stall waiting on you. For the content-quality signals that earn citation and trust, see structured data for AI visibility; for the broader shift in how this content gets surfaced, generative engine optimization and content strategy beyond Google traffic.
Google's October 2026 timing ranges turn a years-old shrug into a plan. A new URL is typically discovered in about 20 hours and indexed in about 1.5 hours once processing runs; title and snippet edits show in 1-2 days; an existing page is recrawled on roughly a 30-day clock; a site move settles in 1-3 months; and core-update recovery takes 3-6 months, often not fully visible until the next update. Every figure has a far worse slowest case — weeks, months, or never — and Google was explicit these are reference points, not deadlines. The part you control is production: publish verified, quality pages consistently, link them well, and keep the cadence up, because the long clocks only start once the page exists, and the sites Google crawls fastest are the ones that always have something worth crawling.
Per timing ranges Google's Gary Illyes shared in October 2026, discovering a brand-new URL takes about 20 hours on average, and end-to-end indexing takes roughly 1.5 hours once the processing actually runs — so a well-linked page on a healthy site can be indexed within a day. But those are typical cases, not promises: the slowest cases stretch to weeks or months, and some pages are never indexed at all. Google advises waiting at least a week after publishing or requesting indexing before assuming something is wrong.
Google's own figure is 3 to 6 months in the typical case, and 6 months to a year in the slowest. Recovery is tied to the update cycle: core updates run roughly every three to four months, and substantive improvements you make after one update often won't be fully reflected until the next core update re-evaluates the site. Recovery is also rarely linear — rankings tend to dip, partly recover, and dip again before stabilizing, so a few weeks of steady improvement is a better signal than any single day.
They are two separate stages with separate clocks. Crawling is Google fetching the page — discovering the URL (about 20 hours for a new one) and downloading it. Indexing is Google processing that fetched page, understanding it, and storing it so it can appear in results (about 1.5 hours typical, but months or never in the slow case). A page can be crawled but not indexed — that's the 'Crawled — currently not indexed' state in Search Console — usually a quality or duplication signal, not a technical bug.
It helps Google discover the URL, but it does not guarantee indexing or jump a queue on demand. The URL Inspection tool's 'Request Indexing' signals Google to look at the page; crawling after that can still take days to weeks, and if the page has a quality or duplicate-content problem, requesting indexing won't fix it — Google may crawl it and still decline to index. Treat it as a nudge for discovery, not a lever for ranking or a cure for a page Google has chosen not to index.
No. Illyes presented them as reference points, not deadlines, and Google has not formally published them with methodology or sample sizes — the figures come from an attendee recap of a conference slide. They describe what is typical and what the slowest case looks like, and Google explicitly noted that a delay in one stage carries into the next. Use them to set expectations and spot genuine anomalies, never as a timeline anyone owes you.
Google's Gary Illyes shared typical timing ranges in October 2026: about 20 hours to discover a new URL, roughly 1.5 hours for end-to-end indexing once processing runs, 1-2 days for title and snippet changes to appear, 1-3 months for a site move to settle, and 3-6 months to recover from a core update. The slowest cases stretch to months, a year, or never — Google stressed these are reference points, not deadlines.
Get started → · ← All guides · Compare Kompozy vs other tools