OfferFree 5-page websiteWith any plan · live in 48 hoursLive in 48h

Home / Insights / SEO / Website redesign or migration without losing…

SEO

Redesign or migrate your website without losing rankings

Most traffic lost in a redesign is lost to avoidable mistakes: URLs changed without redirects, pages dropped, staging settings left switched on. Plan the move like a project, not a design launch.

ARAgile Ranker TeamSearch & AI Visibility deskPublished11 Sep 2026Read10 minReviewed bySearch & AI Visibility desk

Migration launch-day checks

  • Staging noindex and password removed
  • robots.txt allows crawling
  • Top old URLs return a single 301
  • XML sitemap lists new URLs only
  • Search Console verified on the new site

The quick answerCopy

Most ranking losses after a migration come from changed URLs without 301 redirects, removed content and launch-day technical errors. Benchmark the old site, map every important URL to its new home, test redirects on staging, and monitor Search Console daily for the first weeks after launch.

  • Every URL that changes needs a 301 redirect to its closest equivalent — not to the homepage.
  • Benchmark rankings, traffic and top pages before launch, or you cannot prove what changed.
  • Keep the content that ranks. A prettier page with half the words often ranks worse.
  • Check robots.txt, noindex tags, canonicals and sitemaps on launch day — staging settings leak into production.
  • Expect some movement for a few weeks; a sustained drop means something is broken.
01

Why do websites lose rankings after a redesign or migration?

Usually because Google can no longer find the pages it ranked, or finds weaker versions of them. Changed URLs without redirects, deleted content, blocked crawling and broken internal links are the usual causes.

Rankings belong to URLs and the content on them. When a redesign changes /services/seo-audit to /what-we-do/audit and nobody redirects the old address, Google sees a page that has disappeared and a new one with no history. Links pointing at the old URL lead nowhere, and the value they carried is wasted.

Content changes cause quieter losses. Designers often cut copy to make pages look cleaner. If the old page ranked because it answered a question thoroughly, the leaner replacement may no longer deserve its position.

Then there are technical slips: a staging site’s noindex tag carried into production, a robots.txt that blocks everything, canonical tags still pointing at the staging domain. Each is easy to fix and devastating if nobody notices for a fortnight.

02

What counts as a website migration?

Any change to domain, URL structure, platform, protocol or major content and design. A visual refresh on the same URLs is low risk; a new domain plus a new platform plus a new structure is the highest risk.

Moving from WordPress to Shopify or a custom build, from .in to .com, from subfolders to subdomains, or merging two sites into one are all migrations — even when the team thinks of the project as ‘just a new website’.

Avoid changing everything at once if you can. Each change adds risk, and when several happen together it is hard to tell which one caused a problem. If the domain must change, consider keeping the URL paths identical for the first launch.

  • Domain change: example.in to example.com
  • Platform change: WordPress to Shopify, or a builder to a custom site
  • Structure change: new URL paths or merged pages
  • Protocol change: HTTP to HTTPS
  • Content and design overhaul on existing URLs
03

How do you build a redirect map?

List every old URL with traffic, rankings or backlinks, and map each one to its most relevant new URL with a permanent (301) redirect. Pages with no equivalent should go to the closest parent page, not the homepage.

Gather old URLs from several places: a crawl of the current site, your XML sitemap, the Search Console Performance and Pages reports, GA4 landing pages and a backlink tool’s most-linked pages. Each source catches URLs the others miss — old PDFs, campaign landing pages, blog posts from years ago.

Map one-to-one wherever possible. Google tends to treat a redirect to an irrelevant page, such as the homepage, much like a missing page, so the value is lost anyway. If a page genuinely has no replacement and no traffic or links, letting it return a 404 or 410 is acceptable.

Avoid redirect chains — old URL to interim URL to new URL — by pointing every old URL straight at its final destination. Google advises keeping site-move redirects in place for at least a year, and in practice there is little reason ever to remove them.

Want this done for you?

Our SEO Services team can take it on — or start with the free AI visibility check and see where you stand on Google and five AI engines. No obligation.

Get my free check
04

What should you check before launch?

Benchmark the old site, test every redirect on staging, compare page content and metadata, and confirm the new site will be crawlable once staging protection comes off. Do it a week before launch, not the night before.

Export a baseline: organic sessions by landing page from GA4, clicks and impressions by page and query from Search Console, and rankings for your key terms. Save it with a date. Without it, a post-launch dip becomes an argument instead of an investigation.

Crawl the staging site and compare it with the old crawl. Look for missing pages, changed titles and meta descriptions, lost headings, removed structured data and internal links pointing to old URLs. Update internal links to point at new URLs directly rather than relying on redirects.

Launch in a quiet trading period — never the week before a sale or your busiest season — and make sure the developer is available for the days that follow.

05

What should you monitor after launch?

Redirects, crawl errors, indexing and organic traffic by page — daily for the first two weeks, then weekly. Search Console’s Pages report and your own crawler will show most problems before they cost much traffic.

On launch day, crawl the old URL list and confirm each returns a single 301 to the right destination. Submit the new XML sitemap in Search Console. If the domain changed, use the Change of Address tool in the old property, and keep both properties verified.

Watch for 404 errors on URLs you missed, pages reported as not indexed, and sharp drops on specific pages rather than across the whole site. Page-level drops usually point to a specific mapping or content problem.

Update everything outside the site that points to it: your Google Business Profile website link, ad final URLs, email signatures, social profiles and key directory listings. Every outdated link adds a redirect hop and can muddle your tracking.

06

How long do rankings take to settle after a migration?

For a well-executed move, fluctuations usually settle within weeks; larger sites take longer. If traffic is still well below baseline after a month or two, assume something is broken and audit rather than wait.

Google’s documentation says a medium-sized site can take a few weeks for most pages to move in its index, and larger sites longer. Some reshuffling is normal while Google recrawls and processes the new URLs.

A sustained drop is not normal. Compare post-launch top pages with your baseline, find the pages that lost the most, and check each one: is it redirecting correctly, indexed, carrying the same content and linked internally? The cause is usually specific and findable.

07

What are the common mistakes?

01Redirecting everything to the homepage

Mass homepage redirects are treated much like missing pages, so the old rankings are lost anyway. Map each URL to its closest equivalent.

02Launching with staging settings

A leftover noindex tag or robots.txt block can remove a whole site from search. Check both within minutes of going live.

03Cutting content for design’s sake

Pages that ranked on depth slip when trimmed to a headline and three icons. Keep the answering content, then design around it.

04No baseline

Without pre-launch traffic and rankings by page, you cannot tell which pages dropped or show that the migration caused it.

05Forgetting off-site links

Your Google Business Profile, ads, social profiles and directories still point at old URLs. Update them in launch week.

08

Questions people ask

Should we use 301 or 302 redirects for a migration?

Use permanent redirects — 301 or 308 — for a permanent move. A 302 signals a temporary change; Google may eventually treat a long-standing one as permanent, but there is no reason to send a mixed signal.

Can we change domain and redesign at the same time?

You can, but it raises the risk and makes problems harder to diagnose. If timing allows, move the domain with URLs and content unchanged first, let it settle, then redesign.

Do we lose backlinks when we change URLs?

Not if the old URLs redirect to relevant new ones. The links still point at the old addresses, and the redirects pass visitors and signals on. Where a valuable linking site is willing to update its link, ask it to.

Is moving from HTTP to HTTPS a migration?

Yes, treat it as one: redirect every HTTP URL to its HTTPS version, update internal links and canonicals, and list HTTPS URLs in the sitemap. Most sites have done this, but mixed setups still turn up on audits.

When should we use the Change of Address tool?

Only when moving from one domain to another. It sits in the old domain’s Search Console property and needs redirects already in place. It is not used for redesigns on the same domain or for HTTP to HTTPS moves.

Sources

  1. Site moves with URL changes — Google Search Centraldevelopers.google.com/search/docs/crawling-indexing/site-move-with-url-changes
  2. Redirects and Google Search — Google Search Centraldevelopers.google.com/search/docs/crawling-indexing/301-redirects

Cite this article: Agile Ranker Team (2026). Website redesign or migration without losing your rankings. Agile Ranker Insights. Published 11 Sep 2026.

AR

Written by

Agile Ranker TeamSearch & AI Visibility desk · Agile Ranker

The Agile Ranker team that runs search, AI visibility, paid media and content for clients in ten markets. Notes are checked against current platform documentation before publishing.

Reviewed by the Search & AI Visibility desk

Included with every plan

A free 5-page website for your business.

A fast, AI-readable site that turns the traffic we bring into enquiries — built to the same standard as our paid web work.

  • 5 pages, your choiceHome, About, Services, Key service, Contact
  • Live in 48 hoursFrom the launch checklist
  • AI-readableSchema, sitemap and llms.txt built in
  • Yours to keepDomain and hosting in your name

Free with any monthly plan from $499. Domain, hosting and paid tools are bought by you and stay in your name; shops and booking systems are quoted separately. The 48-hour clock starts once your plan is active and the launch checklist is done.

Keep reading

Three notes that pick up from here.

Each one opens with its quick answer — skim first, read if it's yours.

The monthly note

One email a month, when there's something worth sending.

No drip sequence, no sales follow-up, one click to leave.

Free · one business day

Tell us what you need. Get a real plan back.

A strategist reads your brief and replies within one business day with what we'd do first, a timeline and the real cost. No pitch deck.

  • Reply in 1 business dayFrom a strategist, not a bot
  • Free 5-page websiteIncluded with any plan
  • Never sold or sharedYour details stay with us

Prefer a call? Book an AI growth call

Get your plan

Replies within one business day. Never sold, never shared.
Chat on WhatsAppUsually replies within the hour