How Long SEO Actually Takes
Your new website went live Friday. By Sunday morning, someone on the leadership team has Googled it, found the old page title, and sent you a screenshot.
“Didn’t we already fix this?”
You did. The change is live. Your team checked it. Google is still showing something else, and now Monday’s meeting includes a conversation about whether the website project actually worked.
That gap gets expensive when people make decisions inside it.
So, how long does SEO take? A visible change can happen in days. A larger improvement can take months. Some pages never make it into Google’s index at all. The useful answer starts with identifying exactly what you’re waiting for.
Google recently shared numbers that help. Read both columns before you put them in a leadership presentation.
What Google actually shared
On October 2, 2026, Google’s Gary Illyes presented timing estimates at Search Central Live Deep Dive Europe in Barcelona. John Campbell of ROAST documented the session in his Day 3 recap.
The estimates came from Google’s internal analysis and covered processes involved in crawling, indexing and showing search results. They included typical timings and a slower end of the range.
These were conference slides. They should not be treated as deadlines Google has agreed to meet.
Illyes later described the presentation as an exercise to see whether attendees could relate to the internal numbers, according to Search Engine Roundtable.
That makes the data useful for planning. It still leaves room for your site to behave differently.
The work continues after you hit publish
Google describes three stages of Search.
Crawling: Google discovers a page’s address and may visit it to download the content. Discovery and the actual visit are separate steps. Knowing your page exists doesn’t mean Google has read it.
Indexing: Google processes the content, works out what it means and decides whether to store it in its searchable index. This includes handling duplicate versions and choosing a preferred URL.
Serving: When someone searches, Google decides which indexed pages fit that particular query and how to display them.
An indexed page is eligible to appear. It still has to compete for the searches that matter to you.
Those stages also depend on one another. If Google hasn’t crawled your updated page, the later systems can’t evaluate the update.
But don’t add every number below into one giant countdown. Some rows describe overlapping work. Others describe entirely different situations, such as moving a site or recovering after a ranking update.
The timing estimates worth keeping
Here are selected estimates from the slides and Campbell’s recap. “Slowest” is the source’s label for the slower cases, including cases with no guaranteed completion.
| Process | Typical | Slowest |
|---|---|---|
| Discover a new URL | About 20 hours | Weeks to never |
| Recrawl a known URL | About 30 days | Weeks to never |
| Process a sitemap | About 24 hours | Up to 14 days, or never because of quality |
| Complete critical indexing processes | About 1.5 hours | Months, or never because of quality |
| Recognize a canonical change | 1 to 3 weeks | Months with conflicting signals |
| Process a site move | 1 to 3 months | 6 months to more than a year |
| Update a title or snippet | 1 to 2 days | Several weeks to months |
| Remove a manual action | 1 to 2 weeks | 4 to 6 weeks, or much longer for dormant sites |
| Reflect spam update changes | 1 to 2 weeks through continuous processing | Months with batch refreshes |
| Recover after a core update | 3 to 6 months | 6 months to a year, potentially the next core update |
| Process structured data updates | Hours to 1 to 2 weeks | Weeks, or never because of quality |
Sources: original recap and slide photos for crawling, indexing and serving.
The 1.5 hour indexing estimate needs particular care. It describes successful completion of critical indexing processes. It does not promise that a page published at breakfast will be searchable before lunch.
The rendering entry, sometimes shortened awkwardly in summaries, means seconds to render plus hours waiting in a queue. The slow end reaches days or weeks.
The column people skip
The summary graphic published by Search Engine Roundtable includes both columns. Keep that context when sharing it.
About 20 hours to discover a page is easy to remember. Weeks to never is harder to build a campaign around. Both belong in the conversation.
The slides don’t establish that most websites fall into the slowest cases. They also don’t make “typical” a promise to your organization.
Several slower entries explicitly mention quality. Waiting longer won’t necessarily solve those cases. Google may need better reasons to include the content.
Still, an unindexed page doesn’t automatically prove that the writing is bad. Technical restrictions, duplicate content and other indexing issues need investigation too. Google’s own documentation says it doesn’t guarantee crawling, indexing or serving.
Ask your team to identify the obstacle before deciding the answer is another month of waiting.
3 situations where this changes the plan
Publishing an event page
Imagine your team publishes a page for a big event five days before it starts. The address is correct, registration works, and everyone assumes Google will do the rest.
That leaves very little margin.
The roughly 20 hour discovery estimate is a reference point. A newer site, or a page Google rarely has reason to visit, may need more time. Google’s published recrawl guidance says crawling can take days to weeks.
Publish earlier. Link to the page from a relevant page Google already knows, include it in your sitemap, and use Search Console’s URL Inspection tool to request indexing.
That request doesn’t guarantee inclusion. Repeating it won’t speed up crawling. For a fixed event date, use email, social and paid distribution alongside search so attendance doesn’t depend on Google catching up.
Redesigning or moving your website
A redesign that keeps the same URLs is different from a migration that changes them. Changing your domain or page addresses asks Google to process relationships between old and new pages.
Google’s site migration guidance says medium sites can take a few weeks or more to show the new URLs, with larger sites taking longer. The conference recap gives a broader typical site move range of 1 to 3 months.
Protect your busiest season. I would avoid scheduling a major migration immediately before your busiest season, a major launch or a year-end campaign.
Map old URLs to their replacements, test permanent redirects, update internal links and monitor the pages responsible for sales, donations or inquiries. Include time after launch to address problems.
Recovering from a traffic drop
Start by confirming what dropped and why. A broken redirect needs a different response from a decline associated with a core update.
The 3 to 6 month recovery estimate appears on the serving slide. It wasn’t added by the infographic’s creator.
Google’s core update guidance adds the necessary nuance: some improvements can register within days, while broader reassessment can take months. Sometimes another core update is involved. Recovery isn’t guaranteed.
Agree on that expectation before work begins. Review the affected pages, improve what they offer visitors and track the changes. Rewriting everything every Friday makes it harder to tell what helped.
If a redesign is on your calendar, bring digifora’s website team into the planning while there’s still time to protect the search visibility you already have.
What your team can control
Start with access and discovery. Important pages should load reliably, be available to Google, appear in a clean sitemap and have relevant internal links pointing to them.
Then check consistency. Your redirects, sitemap and canonical tags should agree about the preferred URL. A canonical tag tells search engines which version of similar content you prefer; contradictory signals create more work for Google to resolve.
Review the page itself, too. A first-time customer needs hours, pricing, location details and a clear sense of what to expect. “We’re passionate about serving our community” leaves a lot of practical questions unanswered.
Useful detail gives someone a reason to choose your page. Publishing more versions of the same vague answer doesn’t accomplish that.
This is where SEO work should produce evidence you can review. Use Search Console to track important URLs and investigate exclusions. Keep a record of what changed and when so the next conversation starts with something more useful than a screenshot.
What leadership should hear while you wait
“SEO takes time” is a fair explanation once. After that, your team should be able to show what’s happening.
Has Google revisited the page? Is the right version indexed? Is it appearing for relevant searches? Are those visits producing inquiries, sales, registrations or donations?
I’d check technical health weekly, review indexing and visibility monthly, and use quarterly reviews to assess broader traffic and conversion trends. During a migration or an unexpected drop, check more often. Quarterly reporting shouldn’t mean ignoring a broken checkout or donation page until January.
Each review should end with the next action, who owns it and what evidence you expect to see.
Build room for slower processing into the plan. If progress stalls, investigate it. Your team needs enough time for the work to register, and leadership deserves enough evidence to know the work is moving.
Want to know where your site is getting stuck? Request a free SEO health check. We’ll review how Google is crawling and indexing your important pages and identify what to address first.
