Latest
Hiring a Ghostwriter for a Family Business History BookHiring a Ghostwriter for a Retired General’s or Admiral’s Leadership BookHiring a Ghostwriter for a Sheriff’s or Police Chief’s BookWhat the AI Writing Survey Says About Jobs, Freelancers and Fiction AuthorsHow Long Does Google Take? Crawling, Indexing and Recovery TimesLife of Pi50 Years of Duty: One Police Officer’s Compelling Journey from State Trooper to County SheriffBreaking Rank: A Top Cop’s Exposé of the Dark Side of American PolicingBlack in Blue: Lessons on Leadership, Breaking Barriers, and Racial ReconciliationCalled to Rise: A Life in Faithful Service to the Community That Made MeVigilance: My Life Serving America and Protecting Its Empire CityTurnaround: How America’s Top Cop Reversed the Crime EpidemicCollaborate or Perish! Reaching Across Boundaries in a Networked WorldThe Profession: A Memoir of Community, Race, and the Arc of Policing in AmericaSTEP-UP and LEAD: A Guide for Dynamic, Innovative Leadership in Law EnforcementStriving for Justice: A Black Sheriff in the Deep SouthThe Diagram GalleryGar Travis: A Tribute to One of the Best Faire PhotographersReverse Tropes: Six Ways to Turn a Tired Trope Inside OutA Hiker Used AI to Find a Waterfall. The Forum Sent Her to Hell.Did We Miscount the World’s Population? What the Rural Undercount MeansFrankenstein’s Creature Has Worn Many Faces. Only One Is Mary Shelley’sIs Consciousness Quantum? Penrose Is Half RightAI Companies Are Preparing for a Catastrophe. Which One?Petty Motivations Make Characters HumanAnatomy of a Writer: The Parts That Do the Real WorkGuillermo del Toro’s Writing Advice: Love Your MonstersFree Book Marketing: Seven Ways That Cost Time Instead of MoneyMy Sister Built the Family We Never HadShould Your AI Report You to the Police?Anthropic Bans Cruelty Toward Claude: What It Means for WritersWork-for-Hire Contracts: What the Asimov’s Cover Fight Teaches FreelancersGenre Fiction vs Literary Fiction: Don’t Confuse Taste With SkillFlorida Hurricane Prep Rituals: The Grocery Run, the Water Pallet and the Generator in the BoxThe Most Insulting Line of Dialogue Ever Written for the ScreenLoki Through the Ages: From Norse Myth to Marvel, The Mask and Dogma“You Are Utterly Disgusting”: A Book Festival, an AI Cover Ban and a Pile-OnWho Rewrote the Sligachan Legend: AI or the Tour Buses?Layers: How I Ride Out Florida Power Outages in My ApartmentWhy I Don’t Like Reedsy for Ghostwriting: The NDA ProblemThe Enshittification of AmazonPublishers Cancel Books Over AI While Using It in SecretI Was Getting 100 Spam Emails a Day. $4.50 a Month Fixed It.World Mental Health Day: Nothing Was Wrong With MeKessler Syndrome: How Space Debris Could Close Earth’s OrbitAmazon Is Blocking Real Readers From Book ReviewsShould a Novella Get a Paperback, or Go Ebook Only?BookFunnel Download Problems: Fixes, Scams and AlternativesSir Sean Connery: A TributeHow to Find Plot Holes in Your Novel (Most Are Character Holes)
The Writing King Your Ethical Ghostwriter. Your Story, Done Right.

How Long Does Google Take? Crawling, Indexing and Recovery Times

TL;DR: Google finally hung a clock in the waiting room. In October 2026, Gary Illyes shared typical and worst-case times for crawling, indexing and recovery: about 20 hours to find a new page, about 30 days to recrawl a known one, a day or two for a title change, three to six months to recover from a core update. The slow end of many of those ranges is “never,” and never comes down to quality. Fix the thing, tell Google once, then wait the right amount of time.

Fixing a website is fast. Then comes the wait, and the wait wears people down.

You change a title, remove a block in robots.txt or move the whole site to a new domain, and then you sit in a waiting room with no clock on the wall. Nobody calls your number. You refresh Search Console, you check the rankings, you wonder whether anything happened at all, and after a week or two you start changing things again. Every new change resets the wait you were already in.

For years Google’s answer was “it depends.” It still depends.

What changed in October 2026 is that Google finally hung a clock on the wall of that waiting room.

Read it before your next change.

Where do Google’s crawling and indexing times come from?

On October 2, 2026, Gary Illyes of Google’s Search team presented a set of timing ranges at the Search Central Live Deep Dive in Barcelona. He gave a typical time and a slowest time for more than twenty processes, from finding a brand-new URL to recovering after a core update. The numbers reached the rest of us secondhand. John Campbell of the agency ROAST published a detailed recap of the session, and Search Engine Journal and others reported from it. Google hadn’t posted the slides when those stories ran.

So treat everything below with that in mind. “Typical” was never defined, and no sample size or time period was given. The recap labels them reference points. Treat them that way.

How long Google takesA hand-drawn range chart titled How long Google takes, with a logarithmic time axis marked 1 hour, 1 day, 1 week, 1 month, 3 months and 1 year, and a shaded zone past the end labeled the void, where never lives. A dot marks the typical time and a bar runs to the slowest; arrows into the void mean the slow case includes never. Crawling: discovery of a new URL about 20 hours, slowest weeks to never; refresh of a known URL about 30 days, weeks to never; sitemap processing about 24 hours, up to 14 days or never; robots.txt update about 24 hours, slowest 25 hours. Indexing: rendering takes hours in the queue, slowest days to weeks; indexing end to end about 1.5 hours, months or never; canonical change and removal 1 to 3 weeks, slowest months; site move 1 to 3 months, slowest 6 months to over a year. Serving: Search Console removal about 2 hours, slowest 24 hours; title update 1 to 2 days, several weeks to months; manual action removal 1 to 2 weeks, 4 to 6 weeks; core update recovery 3 to 6 months, 6 months to 1 year, the next core update. A note says never is almost always about quality. Subtitle: dot equals typical, bar equals slowest, reference points not deadlines. Source: attendee recap of Gary Illyes, Search Central Live, October 2, 2026.How long Google takesdot = typical, bar = slowest. Reference points, not deadlines.1 hour1 day1 week1 month3 mo1 yearthe void(never)CrawlingDiscovery of a new URL~20 hrs / weeks to neverRefresh of a known URL~30 days / weeks to neverSitemap processing~24 hrs / up to 14 days, or neverrobots.txt update~24 hrs / 25 hrsIndexingRenderinghours in the queue / days to weeksIndexing, end to end~1.5 hrs / months, or neverCanonical change1 to 3 weeks / monthsRemoval1 to 3 weeks / monthsSite move1 to 3 months / 6 months to 1 year+ServingSearch Console removal~2 hrs / 24 hrsTitle update1 to 2 days / several weeks to monthsManual action removal1 to 2 weeks / 4 to 6 weeksCore update recovery3 to 6 months / 6 months to 1 yearsee you next core update(weirdly punctual)"Never" is almost always about quality, not patience.Source: attendee recap of Gary Illyes, Search Central Live, Oct. 2, 2026.
How long Google takesA hand-drawn range chart titled How long Google takes, with a logarithmic time axis marked 1 hour, 1 day, 1 week, 1 month, 3 months and 1 year, and a shaded zone past the end labeled the void, where never lives. A dot marks the typical time and a bar runs to the slowest; arrows into the void mean the slow case includes never. Crawling: discovery of a new URL about 20 hours, slowest weeks to never; refresh of a known URL about 30 days, weeks to never; sitemap processing about 24 hours, up to 14 days or never; robots.txt update about 24 hours, slowest 25 hours. Indexing: rendering takes hours in the queue, slowest days to weeks; indexing end to end about 1.5 hours, months or never; canonical change and removal 1 to 3 weeks, slowest months; site move 1 to 3 months, slowest 6 months to over a year. Serving: Search Console removal about 2 hours, slowest 24 hours; title update 1 to 2 days, several weeks to months; manual action removal 1 to 2 weeks, 4 to 6 weeks; core update recovery 3 to 6 months, 6 months to 1 year, the next core update. A note says never is almost always about quality. Subtitle: dot equals typical, bar equals slowest, reference points not deadlines. Source: attendee recap of Gary Illyes, Search Central Live, October 2, 2026.How long Google takesdot = typical, bar = slowest.Reference points, not deadlines.1h1d1wk1mo3mo1yrvoidCrawlingNew URL found~20 hrs / weeks to neverKnown URL recrawled~30 days / weeks to neverSitemap processed~24 hrs / up to 14 days, or neverrobots.txt update~24 hrs / 25 hrsIndexingRenderinghours in the queue / days to weeksIndexed, end to end~1.5 hrs / months, or neverCanonical change1 to 3 weeks / monthsRemoval1 to 3 weeks / monthsSite move1 to 3 months / 6 months to 1 year+ServingSearch Console removal~2 hrs / 24 hrsTitle update1 to 2 days / several weeks to monthsManual action removal1 to 2 weeks / 4 to 6 weeksCore update recovery3 to 6 months / 6 months to 1 year"Never" is almost alwaysabout quality, not patience.Source: attendee recap of Gary Illyes,Search Central Live, Oct. 2, 2026.

How long does Google take to find and crawl a new page?

Discovery of a new URL takes about 20 hours in the typical case. The slowest case is weeks, or never.

Google comes back to pages it already knows about roughly once a month. The typical refresh for a known URL is about 30 days. That’s the number that matters when you’ve fixed an old page and want Google to notice, because a month is normal and nothing is broken.

Sitemaps help, within limits. Google processes a sitemap in about 24 hours in the typical case. The slow case runs up to 14 days, and the recap adds “or never” with quality in parentheses.

A sitemap tells Google a page exists. It doesn’t make Google want the page.

Robots.txt is the most punctual thing on the list: about 24 hours typical and 25 hours at the slowest. Google’s own documentation agrees, putting the robots.txt cache at up to 24 hours. It’s why a bad Disallow line can do so much damage in a single day, and why a robots.txt mistake is still the most dangerous file error on a website.

Your server matters too. The recap says crawl capacity can drop within seconds when Google backs off a struggling server, and recovering that capacity takes one to three weeks. A slow host costs you weeks of crawling, long after the outage itself is fixed.

How long does Google take to index a page after crawling it?

Indexing from end to end takes about an hour and a half in the typical case, once Google has the page. The recap defines end to end as the point where “all the critical processes finish successfully.” The slowest case is months, or never, and again the reason given is quality.

Several smaller clocks run inside that one. Rendering takes seconds of work but can sit for hours in a queue, or days to weeks at worst. Meta annotations take 45 to 90 minutes. Structured data updates take hours to a couple of weeks. Canonical changes are slower. Telling Google which of two similar pages is the real one takes one to three weeks, or months if your signals conflict. Google’s canonicalization guide, updated in July 2026, says a page can stay in a duplicate cluster for up to two weeks after you fix it.

Removal of a page from the index takes one to three weeks, and months at the slow end.

Every stage waits on the one before it. A page can’t be indexed until it’s crawled, and it can’t be crawled until it’s discovered, so a delay early in the pipe carries all the way through.

The Google pipeline, as plumbingA hand-drawn diagram titled The Google pipeline, as plumbing. A pipe runs through five joints: Discovered, about 20 hours; Crawled; Rendered, hours in the queue; Indexed, about 1.5 hours; and Shown in results, where titles update in 1 to 2 days. Near the start a hairball clog sits in the pipe, labeled your server was slow: crawl capacity drops in seconds, recovers in 1 to 3 weeks. Four leaks drip from the pipe into a bucket labeled Never, quality: not worth crawling; spam, about 40 billion pages filtered a day; not worth indexing; and duplicate, another page chosen as canonical. The caption reads: Every stage waits on the one before it. Fast technical fixes can't push a page Google doesn't think is worth it.The Google pipeline, as plumbingYour server was slow:crawl capacity drops in seconds,recovers in 1 to 3 weeks(the tricklethat makes it)Discovered~20 hrsCrawledRenderedhours in queueIndexed~1.5 hrsShown in resultstitles: 1 to 2 daysNEVER (quality)not worthcrawlingspam: ~40 billionpages filtereda daynot worthindexingduplicate: anotherpage chosen ascanonicalEvery stage waits on the one before it. Fast technical fixescan't push a page Google doesn't think is worth it.
The Google pipeline, as plumbingA hand-drawn diagram titled The Google pipeline, as plumbing. A pipe runs through five joints: Discovered, about 20 hours; Crawled; Rendered, hours in the queue; Indexed, about 1.5 hours; and Shown in results, where titles update in 1 to 2 days. Near the start a hairball clog sits in the pipe, labeled your server was slow: crawl capacity drops in seconds, recovers in 1 to 3 weeks. Four leaks drip from the pipe into a bucket labeled Never, quality: not worth crawling; spam, about 40 billion pages filtered a day; not worth indexing; and duplicate, another page chosen as canonical. The caption reads: Every stage waits on the one before it. Fast technical fixes can't push a page Google doesn't think is worth it.The Google pipeline,as plumbingYour server was slow:crawl capacity drops in seconds,recovers in 1 to 3 weeksNEVER (quality)Discovered~20 hrsCrawledRenderedhours in queueIndexed~1.5 hrsShown in resultstitles: 1 to 2 daysnot worthcrawlingspam: ~40 billion pagesfiltered a daynot worthindexingduplicate: anotherpage chosen ascanonicalEvery stage waits on the one before it.Fast technical fixes can't push a pageGoogle doesn't think is worth it.

Why do so many of Google’s timelines end in “never”?

Because never is Google’s verdict on the page.

Five of the slowest times in the full recap include the word never, and three of them carry “quality” in parentheses. Google isn’t slow on those pages. It looked, decided the page wasn’t worth the effort and moved on. No amount of resubmitting changes that.

The scale explains the attitude. According to the recap, Illyes said Google filters out around 40 billion spam pages a day. He also said scaled content is now a bigger problem than link spam. A search engine wading through that much junk can’t afford to index every page somebody submits. That’s the uncomfortable part for anybody publishing thin pages and waiting for Google to come around. It won’t. The fix is a better page, and the wait starts over when you publish it.

How long do title and snippet changes take to show up in Google?

Google’s typical time is one to two days. The slow case is several weeks to months.

That’s faster than most people expect, and it’s the reason a title rewrite is one of the cheapest experiments you can run. Change it, wait a few days, look at the result. An image change in a text result takes longer, about one to two weeks.

The fastest item on the whole list is the one you control most directly. A removal request filed by the site owner in Search Console takes about two hours, and 24 hours at worst. When something private ends up in search results, that’s the tool, and it works the same day.

How long does a site move take to settle in Google?

The typical site move takes one to three months. The slow end runs six months to more than a year. The recap notes that a small site can finish a move in a few weeks, and Google’s own site-move documentation says the same thing: a few weeks for most pages on a small or medium site, longer for big ones. Three months is where a stuck move starts to look stuck. Before then, a wobble in traffic is the move doing its work.

How long does it take to recover from a core update?

Three to six months is the typical recovery time. The recap lists the slowest case as six months to a year, with a note that reads “next core update.”

Core updates themselves take two to four weeks to roll out. The December 2025 update ran 18 days and the March 2026 update ran a little over 12. Google’s documentation says some effects of your improvements can show within days. Confirming a real recovery can take several months. Some recoveries wait for the next update. Illyes also said core updates judge pages one at a time. So in a single update, some pages on a site can rise while others on the same site fall. Recovery is page by page too.

Manual actions are faster. A reviewed manual action comes off in one to two weeks in the typical case. The slow end is four to six weeks, and much longer for dormant sites. Spam updates roll out in a day or two, and recovering from one takes one to two weeks when the change is continuous and months when it waits for a batch refresh.

Google finally hung a clock in the waiting room. About 30 days to recrawl a page it already knows. Three to six months to recover from a core update. And “never” isn’t a speed. It’s a verdict on quality. – Richard Lowe
Share on X

Can you make Google crawl and index your site faster?

A little. Not as much as the tools imply.

The URL Inspection tool in Search Console has a Request Indexing button. Google’s help page says requests are capped each day. It also says a request doesn’t guarantee the page gets indexed. Indexing can take anywhere from a day to a week or two. Use it for the handful of pages that matter, once each. Google’s Indexing API is not a shortcut for blogs. Google restricts it to pages with job postings or livestream video, and using it for anything else is a waste of an afternoon.

What does help is boring. Keep the sitemap clean. Link to new pages from your busiest pages. Run a server that stays fast when it’s busy. Most of all, publish pages worth indexing in the first place.

Nothing else turns a never into a yes.

When to check (and when to stop refreshing)A hand-drawn waiting room ticket board titled When to check, and when to stop refreshing, with the line take a number, Google will call you. A dark board reads Now serving: your title change. Seven numbered tickets list checkpoints after you change something: 2 hours, Search Console removal should be done, slow case 24 hours; 1 to 2 days, titles and snippets usually updated, slow case weeks to months, breathe; 2 weeks, sitemap processed even in the slow case, canonical fixes recognized, manual action reviews back; 1 month, known pages typically recrawled, your edit has probably been seen; 3 months, site move typical upper end, you can stop checking daily; 6 months, core update recovery typical upper end, maybe take up a hobby; 1 year, the slow case, the next core update, see you then. Sticky notes say: refreshing Search Console every 10 minutes speeds up nothing; changing it again before Google sees the first change restarts the clock; stuck at never, that is a quality problem, not a patience problem. Source: attendee recap of Gary Illyes, Search Central Live, October 2, 2026.When to check (and when to stop refreshing)Take a number. Google will call you.TICKET NO.2 hrsSearch Console removal should be done.(Slow case: 24 hours.)TICKET NO.1 to 2 daysTitles and snippets usually updated.(Slow case: weeks to months. Breathe.)TICKET NO.2 weeksSitemap processed, even in the slow case.Canonical fixes recognized. Manual actionreviews back.TICKET NO.1 monthKnown pages typically recrawled.(Your edit has probably been seen.)TICKET NO.3 monthsSite move: typical upper end.(You can stop checking daily.)TICKET NO.6 monthsCore update recovery: typical upper end.(Maybe take up a hobby.)TICKET NO.1 yearThe slow case: the next core update.(See you then.)NOW SERVINGyour title changePlease remain seatedRefreshing Search Consoleevery 10 minutes:speeds up nothing.Changing it again beforeGoogle sees the firstchange:restarts the clock.Stuck at "never"?That is a quality problem,not a patience problem.Source: attendee recap of Gary Illyes, Search Central Live, Oct. 2, 2026.
When to check (and when to stop refreshing)A hand-drawn waiting room ticket board titled When to check, and when to stop refreshing, with the line take a number, Google will call you. A dark board reads Now serving: your title change. Seven numbered tickets list checkpoints after you change something: 2 hours, Search Console removal should be done, slow case 24 hours; 1 to 2 days, titles and snippets usually updated, slow case weeks to months, breathe; 2 weeks, sitemap processed even in the slow case, canonical fixes recognized, manual action reviews back; 1 month, known pages typically recrawled, your edit has probably been seen; 3 months, site move typical upper end, you can stop checking daily; 6 months, core update recovery typical upper end, maybe take up a hobby; 1 year, the slow case, the next core update, see you then. Sticky notes say: refreshing Search Console every 10 minutes speeds up nothing; changing it again before Google sees the first change restarts the clock; stuck at never, that is a quality problem, not a patience problem. Source: attendee recap of Gary Illyes, Search Central Live, October 2, 2026.When to check(and when to stop refreshing)Take a number. Google will call you.NOW SERVINGyour title changePlease remain seatedTICKET NO.2 hrsSearch Console removal should be done.(Slow case: 24 hours.)TICKET NO.1 to 2 daysTitles and snippets usually updated.(Slow case: weeks to months. Breathe.)TICKET NO.2 weeksSitemap processed, even in the slow case.Canonical fixes recognized. Manual actionreviews back.TICKET NO.1 monthKnown pages typically recrawled.(Your edit has probably been seen.)TICKET NO.3 monthsSite move: typical upper end.(You can stop checking daily.)TICKET NO.6 monthsCore update recovery: typical upper end.(Maybe take up a hobby.)TICKET NO.1 yearThe slow case: the next core update.(See you then.)Refreshing Search Console every 10 minutes:speeds up nothing.Changing it again before Google sees the firstchange:restarts the clock.Stuck at "never"?That is a quality problem, not a patience problem.Source: attendee recap of Gary Illyes,Search Central Live, Oct. 2, 2026.

What the waiting looks like on my own site

I’ve pushed hundreds of thousands of changes through this site with my own bulk-update tooling: titles, headings, internal links, whole sections. I’ve cut author and actor archives out of the sitemap when they pushed it past 10,000 URLs, and I clear 404s through redirect batches every few days. With that much in flight, the clock is the difference between waiting and panicking. A title change deserves a few days before anybody judges it. A page that hasn’t been recrawled in three weeks hasn’t been forgotten, because the typical refresh is a month.

And a page that never gets indexed doesn’t need resubmitting. It needs rewriting.

The worst habit in technical SEO is the second change. You fix something, see nothing for ten days and change it again, and now Google has two versions to reconcile and you have no idea which one worked. One change, then the right amount of waiting.

Read the clock, then sit down

Every one of these numbers is a reference point, reported secondhand, with no sample size behind it. They’re still the best map anybody has had of how long Google really takes, and they come from the people who run the systems.

Make your change and tell Google once. Write down the date, look up the typical time for that kind of change, then sit down and let the clock run.

More on the technical side of running an author’s website lives in the Technology of Writing hub, including Core Web Vitals and how AI crawlers differ from search crawlers. And if you’d rather somebody else watched the clock, my WordPress service handles this kind of work for authors and small businesses. Google calls your number eventually. It just never says when, until now.

Frequently Asked Questions

Do new pages show up in Google within a day?
Gary Illyes put typical discovery of a new URL at about 20 hours in October 2026. The slowest case is weeks, and some pages are never found.
How long until Google recrawls a page I fixed?
About every 30 days in the typical case. The slowest case is weeks or never, so a fixed page can take a month to be seen with nothing wrong.
How long does a robots.txt change take to reach Google?
About 24 hours, and no more than about 25 hours in the slowest case. Google’s documentation puts the robots.txt cache at up to 24 hours.
How long do title tag changes take to show in Google search results?
One to two days in the typical case, and several weeks to months in the slowest case.
Do you have to wait for the next core update to recover?
Not always. Typical recovery is three to six months. The slow case is six months to a year, and the recap ties it to the next core update.
Does Request Indexing in Search Console guarantee a page gets indexed?
No. Google says requests are limited per day and a request does not guarantee indexing. Indexing can take a day to a week or two.
Why does Google never index some pages?
Most of the never outcomes in Google’s timing ranges come down to quality. Google decided the page was not worth crawling or indexing, and resubmitting it does not change that.

Categories and tags
CategoriesSEOTechnology
About the Author
Richard Lowe, professional ghostwriter

Richard Lowe is a professional ghostwriter and author with 113+ books authored and 54+ ghostwritten. Before writing full time he spent 33 years in enterprise technology, including 20 years as Director of Computer Operations and Technical Services at Trader Joe's. He writes nonfiction, fiction and memoir, and works with executives and experts on books that build authority.

More about Richard Lowe →

Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.

0 comments

No comments yet. Yours can be the first.

Was this useful?

Leave a comment