Website Migration Without Losing Google Rankings

To migrate a website without losing Google rankings, keep or permanently redirect every URL that has traffic or links, preserve the content and metadata of important pages, keep the site crawlable, submit the new sitemap, and monitor Search Console closely for several weeks afterwards. Most ranking losses after a migration come from missing redirects and pages quietly removed or thinned out.

Migrations happen for good reasons: a new platform, a redesign, a new domain, merging sites, or moving to HTTPS. Each carries the same risk.

Types of migration

| Migration | Main risk | | --- | --- | | New design, same URLs | Content or metadata lost in the rebuild | | New platform (e.g. WordPress to Next.js) | URL patterns change, features lost | | New URL structure | Every changed URL needs a redirect | | New domain | All signals must transfer; highest risk | | Merging several sites | Duplicate content, many redirects |

Before the migration

1. Crawl and export everything

Use a crawler to list every URL on the current site, with titles, descriptions, headings, canonical tags and status codes. Export your top pages by clicks from Search Console and by sessions from analytics, and pages with external links.

2. Build the redirect map

For every old URL, decide the new destination:

• Same content, new URL: one-to-one 301 redirect.
• Merged content: redirect to the page that now covers it.
• Removed content with no equivalent: redirect to the closest relevant page, or let it return 410 if truly obsolete.

Avoid redirecting everything to the home page. Google treats that like a missing page.

3. Protect content parity

Important pages should keep their depth, headings and internal links. A redesign that replaces a detailed service page with a short, image-led version often loses rankings.

4. Carry over technical SEO

Titles, meta descriptions, canonical tags, structured data, image alt text, hreflang if used, and robots rules.

Launch day

• [ ] Redirects deployed and tested on a sample of old URLs
• [ ] Staging blocks removed (noindex, password, robots disallow)
• [ ] New sitemap live and submitted in Search Console
• [ ] Analytics and conversion tracking working
• [ ] Forms tested end to end
• [ ] Crawl of the new site for broken links and redirect chains
• [ ] For domain changes: Change of Address tool used in Search Console

Forgetting to remove a staging noindex is one of the most common and damaging launch errors.

After launch

• Daily for two weeks: check Search Console coverage and crawl errors, and fix any 404s from the old URL list.
• Weekly for two months: compare clicks and rankings for top pages against the baseline.
• Keep redirects in place for at least a year, ideally permanently.
• Update internal links to point directly to new URLs rather than through redirects.
• Update external listings you control, such as Google Business Profile and directory profiles.

Some fluctuation in the first few weeks is normal. Sustained drops on specific pages usually point to a missing redirect or lost content.

Special cases

• Blog and guides: often the largest source of organic traffic; migrate every post and keep its URL if possible.
• Old campaign pages: check for backlinks before retiring them.
• PDFs and images that rank or are linked: redirect or keep.

Frequently asked questions

How long does it take for rankings to settle?

Usually a few weeks for simple migrations, longer for domain changes or large restructures.

Do 301 redirects pass ranking signals?

Yes, permanent redirects pass signals to the new URL, which is why they are essential.

Can we change URLs to be more SEO-friendly during a migration?

You can, but every change adds risk. Change only where the benefit is clear, and redirect carefully.

Should we migrate and redesign at the same time?

It is common, but doing both multiplies what can go wrong. If possible, keep URLs stable during a redesign.

Migrate with confidence

Turbo Bytes Consulting plans and executes website and web application migrations with SEO protection built in. See also our website redesign checklist and Next.js vs WordPress.

Book a 30-minute scoping call before you move a single URL.