How Long Does SEO Actually Take? Google’s Own Timelines for 23 Crawling, Indexing and Serving Processes

“How long before I see results? or How Long Does SEO Take?” is the question every SEO, marketer, and business owner has asked at some point. For years, the honest answer was “it depends”, which is true, but not very useful when a client wants a date.

Now Google has put numbers on it.

At the Google Search Central Live Deep Dive event in Europe, Google analyst Gary Illyes presented internal data on how long Google typically takes to complete individual processes across crawling, indexing and serving, according to Search Engine Roundtable. Each process was given a typical time and a slowest time, based on Google’s internal analysis.

This guide breaks down all 23 processes, explains why your changes may take far longer to appear than any single number suggests, and gives you a practical playbook for each situation.

[IMAGE: “How long SEO actually takes (according to Google)” infographic]
Alt text: Infographic showing Google’s typical timelines for 23 crawling, indexing and serving processes, from discovering a new page (~20 hours) to recovering from a core update (3–6 months).

Key Takeaways

• Google discovers a new page in about 20 hours, but recrawls an existing page roughly every 30 days.
• Once a page is crawled, end-to-end indexing can take only about 1.5 hours.
• Title and description updates usually appear in search in 1–2 days after processing.
• A site migration typically takes 1–3 months, and can run past a year in the slowest cases.
• Recovering from a core update typically takes 3–6 months.
• These are process times, not “change to result” times. The steps stack, so real-world delays are the sum of several stages.
• These are estimates, not guarantees. Some processes can take much longer or never happen at all.

First, How Google Search Works (in 60 Seconds)

Every change you make to a website has to travel through three stages before anyone sees it in search. Google’s own guide to how Search works describes them as:

1. Crawling: Googlebot finds URLs and downloads the page’s text, images and videos.
2. Indexing: Google analyses that content and stores it in the Google index, a very large database.
3. Serving: When someone searches, Google returns the most relevant results from the index.

A page can’t be indexed until it has been crawled, and it can’t be served until it has been indexed. That dependency is the single most important idea in this article, and we’ll come back to it.

The Full List: All 23 Google Timelines

The table below includes both the typical time and the slowest time Google reported for each process, as recorded by Search Engine Roundtable. The slowest column matters as much as the typical one, because it tells you what is still “normal”.

Stage 1: Crawling (6 processes)

#	Process	Typical time	Slowest time
1	Discover a new page (new URL)	~20 hours	Weeks to never
2	Recrawl an existing page (known URL)	~30 days	Weeks to never
3	Process a sitemap	~24 hours	Up to 14 days, or never (quality)
4	Pick up robots.txt changes	~24 hours	25 hours
5	Adjust crawl capacity	4 hours to 1–2 weeks	1–3 weeks (in recovery)
6	Adjust crawl demand (how often it crawls)	~20 hours	Weeks to months

Stage 2: Indexing (10 processes)

#	Process	Typical time	Slowest time
7	Render a page	Seconds to render, hours in the queue	Days to weeks
8	Process meta tags (meta annotations)	45–90 minutes	1–4 days
9	Process links (link annotations)	Minutes to 1–3 weeks	Months
10	Complete indexing (end-to-end)	~1.5 hours	Months, or never (quality)
11	Remove a page from the index	1–3 weeks	Months
12	Change the canonical URL	1–3 weeks	Months (conflicting signals)
13	Process a site migration (site move)	1–3 months	6 months to 1 year+
14	Process structured data	Hours to 1–2 weeks	Weeks, or never (quality)
15	Process images	Hours to days	Weeks to months
16	Process videos	Hours to days	Weeks to months (deep analysis)

Stage 3: Serving Results (7 processes)

#	Process	Typical time	Slowest time
17	Hide a result via Search Console (owner removal)	~2 hours	24 hours
18	Update a search result description (snippet)	1–2 days	Several weeks to months
19	Update a search result title	1–2 days	Several weeks to months
20	Update a search result image	1–2 weeks	Several weeks to months
21	Remove a manual action (penalty)	1–2 weeks	4–6 weeks, or much longer for dormant sites
22	Recover from a core update	3–6 months	6 months to 1 year (next core update)
23	Reflect spam update changes	1–2 weeks (continuous)	Months (batch refreshes)

Two extra details from the same presentation: core updates themselves take 2–4 weeks to roll out, and spam updates roll out in 1–2 days (Search Engine Roundtable).

The Most Important Insight: SEO Delays Stack Up

It is tempting to read “indexing takes ~1.5 hours” and expect your updated page to rank by lunchtime. That is not how it works.

These timelines describe how long each individual process takes once it starts. They are not the time from making a change to seeing a result. Gary Illyes made this caveat himself: many of these processes are linked, a page can’t be indexed until it has been crawled, so delays stack up (Search Engine Roundtable).

A worked example

Say you rewrite the title tag and first 300 words of an existing service page.

Step	What happens	Time
1	Google waits for its next scheduled recrawl of that URL	Up to ~30 days
2	Page sits in the rendering queue, then renders	Seconds to hours
3	Meta tags are processed	45–90 minutes
4	End-to-end indexing completes	~1.5 hours
5	New title appears in search results	1–2 days
	Realistic total	Roughly 1 day to 5 weeks

Google could process your change in an afternoon. But if it doesn’t come back to crawl the page for another 30 days, your change stays invisible for a month. And that’s before any ranking movement, which depends on how Google evaluates the new content against competitors.

The lesson: when a change “isn’t working”, the most common reason is that Google simply hasn’t seen it yet.

Stage-by-Stage: What Each Timeline Means for You

Crawling: Discovery is fast, recrawling is slow

The contrast between the first two numbers is the most useful insight in the whole dataset. Google finds brand-new URLs in about 20 hours, but takes around 30 days to revisit a URL it already knows.

This means new content is often noticed faster than updates to existing content. If you refresh an old blog post, expect a longer wait than publishing a new one, unless you actively prompt Google.

What speeds up crawling:

• Strong internal links from pages Google crawls often (homepage, category hubs, popular posts)
• An accurate XML sitemap with correct lastmod dates
• Fast, reliable server responses
• Regular, meaningful content updates that build crawl demand

What slows it down:

• Orphan pages with no internal links
• Server errors and slow response times (crawl capacity can drop within seconds when Google backs off from a struggling server, per Search Engine Roundtable)
• Large volumes of low-value, duplicate or parameter URLs
• Low-quality sitemaps (Google may take up to 14 days, or never process them)

Robots.txt is the exception to the “slow” rule. Changes are typically picked up in about 24 hours, with a slowest case of 25 hours. So if you accidentally block your site, fix it fast, because Google will notice within a day either way.

Indexing: Quick when signals are clear, slow when they conflict

Indexing itself is fast. About 1.5 hours end to end, provided all the critical processes finish successfully. Meta tags are processed in under two hours.

The slow items are the ones that involve consolidating signals:

• Links (minutes to 3 weeks): New backlinks or internal links don’t pass value instantly. Give link-building campaigns at least a few weeks before judging them.
• Canonical changes (1–3 weeks, or months with conflicting signals): If your canonical tag says one thing but your internal links, sitemap and redirects say another, Google will take longer to decide. Keep every signal pointing at the same URL.
• Removals (1–3 weeks): Adding noindex or deleting a page doesn’t remove it from the index immediately. Google has to recrawl it first.
• Structured data (hours to 2 weeks, or never for quality reasons): Valid schema doesn’t guarantee rich results. Google may decide not to show them at all.
• Images and videos (hours to days): Videos can take weeks to months when Google performs deeper analysis.

Note the repeated phrase “or never (quality)”. Several indexing processes may simply not happen if Google judges the content to be low quality. No amount of waiting fixes a quality problem.

Serving: The visible layer has its own delays

Even after indexing, what users see in search results updates on its own schedule.

• Titles and descriptions: 1–2 days. Google may also rewrite them, so a change in your HTML doesn’t guarantee a matching change in the SERP.
• Search result images: 1–2 weeks.
• Search Console removals: ~2 hours. The fastest process on the list. Use it for urgent issues such as accidentally published private information, remembering it hides results temporarily rather than deleting the page.
• Manual action removal: 1–2 weeks after a successful reconsideration request.
• Spam update recovery: 1–2 weeks when continuous, months when Google relies on batch refreshes.
• Core update recovery: 3–6 months. In the slowest cases, you may need to wait for the next core update, which can be 6 months to a year.

The Practical Playbook: What to Do in 4 Common Situations

1. “I updated a page and nothing changed”

Before assuming your changes failed, confirm Google has actually seen them.

1. Open Google Search Console > URL Inspection and enter the URL.
2. Check the last crawl date. If it’s before your update, Google is still looking at the old version.
3. If the crawl is older than your change, click Request Indexing. Keep in mind Google says crawling can take anywhere from a few days to a few weeks, there’s a quota for submissions, and requesting a recrawl multiple times won’t make it faster (Google Search Central).
4. Add a contextual internal link to the updated page from a frequently crawled page.
5. Update the lastmod value in your sitemap.
6. Wait at least 2–4 weeks after the recrawl before evaluating ranking impact.

2. “My new pages aren’t getting indexed”

New URLs are typically discovered in ~20 hours, so if a page has been live for weeks without being indexed, something is usually blocking it. Check these in order:

• Internal links: Is the page linked from at least one relevant, crawlable page? Orphan pages are the most common cause.
• Sitemap: Is the URL in your submitted XML sitemap? Does the Sitemaps report show “Success”?
• Crawlability: Is the page blocked by robots.txt, a noindex tag, a login wall or a JavaScript rendering issue?
• Canonical: Does the page point its canonical to itself, or to another URL?
• Content quality: Is the page thin, duplicated or very similar to another page on your site? Look for “Crawled – currently not indexed” or “Discovered – currently not indexed” in the Page indexing report.

If it’s a quality issue, improve the page rather than repeatedly requesting indexing.

3. “We’re migrating our website”

A site migration typically takes Google 1–3 months to process, and 6 months to over a year in the slowest cases. A small site move can be completed in a few weeks (Search Engine Roundtable). Plan for the long version.

Before the migration

• Build a complete URL-to-URL redirect map (one-to-one, not everything to the homepage)
• Benchmark rankings, traffic and indexed pages
• Crawl the staging site for broken links, noindex tags and canonical errors

On launch day

• Implement 301 redirects
• Update canonicals, internal links and hreflang to the new URLs
• Submit the new XML sitemap and, for domain changes, use the Change of Address tool in Search Console

For the next 3–6 months

• Monitor redirects for chains, loops and 404s
• Track indexing of old vs new URLs in the Page indexing report
• Watch canonical selection in URL Inspection
• Keep redirects in place long term

Set expectations with stakeholders early: temporary fluctuations are normal, and not a sign the migration has failed.

4. “We’ve been hit by a core update”

Recovery typically takes 3–6 months, and in some cases only happens with the next core update. Quick fixes won’t bring traffic back next week.

• Don’t panic-edit during the rollout. Core updates take 2–4 weeks to roll out. Wait until it’s complete before analysing.
• Diagnose at page level. Identify which pages, queries and content types lost visibility in Search Console.
• Compare with what now ranks. Look at the pages that replaced yours. What do they do better for the searcher?
• Improve substantially, not cosmetically. Focus on depth, originality, first-hand experience, accuracy and user satisfaction. Rewriting titles alone rarely moves the needle.
• Prune or consolidate weak content that drags down overall site quality.
• Be patient. Judge your changes over months, not days.

A Quick Diagnostic Checklist

Use this before reporting “SEO isn’t working” to a client or manager.

Question	Where to check
Has Google crawled the page since the change?	URL Inspection > Last crawl
Is the page indexed?	URL Inspection / Page indexing report
Which canonical did Google choose?	URL Inspection > Google-selected canonical
Is the sitemap processed without errors?	Sitemaps report
Are there server or crawl errors?	Settings > Crawl stats
Is there a manual action?	Security & Manual Actions
Did a core or spam update roll out recently?	Google Search Status Dashboard
Has enough time passed for this process?	The 23-process table above

What These Timelines Mean for SEO Reporting and Client Expectations

For agencies and in-house teams, this data is a powerful expectation-setting tool.

• Build timelines into proposals. A content refresh campaign should be reported on over 4–8 weeks, not 7 days. A migration needs a 3–6 month monitoring window.
• Report leading indicators first. Crawl dates, indexed pages and impressions move before clicks and conversions do.
• Pair SEO with paid search during slow phases. If a new landing page needs traffic immediately, Google Ads can cover the gap while organic visibility builds.
• Keep a change log. Record the date of every significant change so you can match it against crawl dates and performance shifts later.

Important Caveats

• These are estimates, not guarantees. Google has long said it can’t predict or guarantee when, or if, URLs will be crawled or indexed (Google Search Central Community).
• Some processes never happen. Several items carry a slowest time of “never”, usually linked to quality.
• The data came from a live presentation. Gary Illyes noted it was an exercise to see whether the audience could relate to numbers Google pulled internally and put on slides (Search Engine Roundtable). Treat them as directional benchmarks, not an SLA.
• Processing isn’t ranking. Getting indexed quickly doesn’t mean ranking well. Ranking depends on relevance, quality and competition.

Frequently Asked Questions

Final Thoughts

SEO feels slow because it’s a chain of processes, not a single switch. Google can process a change in under two hours, but if it hasn’t recrawled your page, nothing will move for weeks.

So the next time your SEO changes aren’t showing up, don’t rush to undo them. Check the crawl date, confirm indexing, compare against the timelines above, and give each process the time it needs.

Save this guide and the infographic for the next time someone asks, “Why isn’t it ranking yet?”

Need help building an SEO plan with realistic timelines? Talk to the MagDigit team about content strategy, technical SEO, and campaigns that keep your business visible while organic growth builds.

Sources

• Search Engine Roundtable, “Google Search Data On Crawling, Indexing & Serving Timelines”: https://www.seroundtable.com/google-crawling-indexing-serving-data-42225.html
• Google Search Central, “In-Depth Guide to How Google Search Works”: https://developers.google.com/search/docs/fundamentals/how-search-works
• Google Search Central, “Ask Google to Recrawl Your URLs”: https://developers.google.com/search/docs/crawling-indexing/ask-google-to-recrawl?hl=en
• Search Console Help, “Page indexing report”: https://support.google.com/webmasters/answer/7440203?hl=en
• Google Search Central Community, “Google Search Indexing and Ranking FAQ”: https://support.google.com/webmasters/community-guide/368537385/google-search-indexing-and-ranking-faq?hl=en