How Long Does Google Take to Reindex a Website After URL Changes?

What happens after a URL changes?

When an existing page moves, Google must:

• Recrawl the old URL
• Discover its redirect
• Crawl the new URL
• Process its content and canonical signals
• Transfer applicable signals
• Replace the old URL in search results

These steps do not necessarily happen simultaneously.

Reindexing speed depends heavily on your technical SEO, including crawlability, redirects and internal links.

One page may move within several days while another old URL continues appearing for weeks. Google needs to process both sides of the change before it can confidently understand the relationship.

Reindexing should not be confused with ranking recovery. A new URL may become indexed before its previous visibility fully stabilises.

How long should different changes take?

Google provides broad guidance rather than fixed deadlines.

Typical expectations are:

• One or two important URLs: several days to a few weeks
• Small or medium website migration: a few weeks for most pages
• Large website migration: several weeks or longer
• Low-authority or infrequently crawled websites: potentially longer

The speed can depend on:

• Number of changed URLs
• Website crawl frequency
• Server performance
• Redirect quality
• Internal-link updates
• Sitemap accuracy
• Content quality
• Conflicting canonical signals
• The number of errors Google encounters

Repeatedly requesting indexing does not force Google to process a URL immediately.

How should old URLs redirect?

Every old URL should permanently redirect to its closest equivalent new URL using a server-side 301 or 308 redirect.

Use direct one-to-one mappings:

Old service URL → New version of that service

Avoid:

• Redirecting every page to the homepage
• Sending unrelated pages to one generic destination
• Temporary 302 redirects for permanent moves
• Multiple redirect steps
• Redirect loops
• Allowing old and new versions to remain live unnecessarily

Google states that permanent redirects do not cause an automatic loss of PageRank. However, an inaccurate redirect can still provide a poor experience and may be treated as a soft 404.

Keep migration redirects in place for at least one year. Retaining useful redirects indefinitely may benefit visitors following old bookmarks or external links.

What signals should point to the new URLs?

Redirects are only part of the migration.

If old URLs linger, check why Google may index the wrong canonical URL, and update important posts so there is a reason to recrawl them, as covered in how often to update old blog posts.

Make sure the new URLs:

• Return a 200 OK response
• Have self-referencing canonical tags
• Appear in the XML sitemap
• Receive updated internal links
• Are not blocked by robots.txt
• Do not contain a noindex directive
• Appear in breadcrumbs and navigation
• Are referenced correctly in structured data
• Use consistent hreflang annotations where applicable

Remove old URLs from normal navigation and the current XML sitemap. The fewer conflicting signals Google encounters, the easier the move is to interpret.

If Google continues selecting an older version, read why Google may index the wrong canonical URL.

Should you request indexing in Search Console?

Use URL Inspection to request indexing for a small number of important new URLs, such as:

• The homepage
• Main service pages
• Important category or hub pages
• High-traffic pages that changed address

For a larger migration, submit the new XML sitemap in Search Console.

Google warns that requesting indexing repeatedly will not make crawling happen faster. The request joins a processing queue and still does not guarantee indexation.

How can you monitor the migration?

Use Search Console to inspect representative old and new URLs.

Look for:

• New URLs becoming indexed
• Old URLs showing the correct redirect
• Google-selected canonicals matching the new URLs
• Impressions shifting from old URLs to new ones
• Unexpected 404, blocked or duplicate statuses
• Sitemap processing
• Changes in organic clicks and impressions

If available, server logs can confirm whether Googlebot has visited both versions.

Traffic on the old URLs should gradually fall as impressions and clicks transfer to the new ones.

When should you become concerned?

Do not assume the migration has failed after a few days.

Investigate more closely when important new URLs remain undiscovered or the old versions are still preferred after several weeks.

Common causes include:

• Missing or incorrect redirects
• Old URLs returning 200 OK
• Canonicals pointing backwards
• Old internal links
• Incorrect sitemap entries
• New pages blocked from crawling
• Redirect chains
• Substantially changed or missing content
• Server errors

A technical SEO audit can identify these conflicting signals.

Frequently asked questions

Allow time, but verify the setup

A few weeks is a realistic expectation for most small and medium website migrations, but progress should be monitored rather than assumed.

Correct permanent redirects, self-referencing canonicals, updated internal links and a clean sitemap give Google the clearest possible instructions. Once those elements are aligned, avoid repeatedly changing the migration and allow Google time to recrawl the site.