ujans
Blog
Web and software

Redesigning a website without losing SEO: a migration and redirect guide

The redesigned site looks good but search traffic can suddenly fall. The problem is usually not the design but how the old pages are handled on the new site.

ujans team··5 min read

A common scenario in website redesign projects: the new design goes live, everyone is happy; a few weeks later organic traffic and enquiries have fallen. Why? Because pages, addresses and links that search engines learned over years have changed, and the new structure has not inherited the old one's value. With proper planning this loss can be largely avoided.

Why does traffic fall?

  • Addresses (URLs) change and old addresses are not redirected; the old page gives 404.
  • Content is shortened or deleted; pages that ranked disappear.
  • Titles, meta descriptions and heading structure break.
  • The internal link structure changes.
  • The site becomes slow or works poorly on mobile.
  • Technical errors: wrong blocking (robots/noindex), missing sitemap, canonical errors.
  • On multilingual sites, language version relationships (hreflang) break.

1. First determine what is valuable

Record the current state before redesigning:

  1. Page inventory: Extract all addresses with crawler tools.
  2. Performance data: Impressions, clicks and rankings by page and query from Search Console; organic traffic and conversions from analytics; see the Google Analytics 4 guide.
  3. Link data: Which pages receive external links?
  4. Technical baseline: Speed, mobile fit, error pages.
  5. Prioritisation: Put the pages bringing the most traffic, conversions and links on the "protect" list.

This record is the only way to compare after the move.

2. Plan the new structure and address plan

  • Keep addresses if possible. The safest approach is not to change the URL structure on pages that perform.
  • If they must change, define the new counterpart for each old address (a mapping table).
  • Logical hierarchy and clean URLs: Short, readable, consistent.
  • Pages to delete: Identify only those that are truly worthless, to be redirected to the nearest relevant page.
  • Multilingual structure: Language paths, hreflang and canonical plan; see the multilingual SEO guide.
  • If domain or server changes: Plan the DNS and SSL move beforehand; see the domain and DNS guide.

3. Preserve and improve content

  • Do not shorten content that ranks; when renewing, only deepen it.
  • Keep or improve the title tag, meta description, H1 and subheading structure.
  • Keep image alt texts and file names.
  • Avoid the mistake of the new design hiding content (for example in tabs or closed accordions) or reducing it to images.
  • Rebuild internal links in the new structure; see the content marketing plan.

4. Redirects (301)

A permanent redirect (301) from the old address to the new passes value and takes the user to the right page.

  1. Define a 301 for every old address in the mapping table.
  2. Avoid redirect chains (go directly from A to C rather than A to B to C).
  3. Use blanket redirect to the home page only when there is no alternative; redirect to the most relevant page.
  4. Redirect HTTP to HTTPS and www and non-www versions into one form.
  5. Keep redirects for a long time after the move (at least a year).

5. Technical preparation

  • Speed and mobile: The new site must not be slower than the old; see speeding up your website.
  • Crawlability: Check robots and noindex settings. Indexing blocked on the test environment and forgotten on, or left blocked on live, is the most frequent disaster.
  • XML sitemap: Include the new addresses; submit to Search Console.
  • Canonical tags and structured data: Correct and complete; see the structured data guide.
  • Accessibility and quality: The quality bar of the new site should be higher than the old; see website accessibility.
  • Security: HTTPS, current software, MFA on admin accounts.
  • Backup: Take a full backup of the old site before the move; see backup strategy.

If the technology choice changes, assess the SEO effect too; see WordPress or custom development?.

6. Validate on a test environment

Before going live, on the test environment (closed to search engines):

  1. Run a redirect test of all old addresses against their new counterparts.
  2. Compare title, meta, H1 and content.
  3. Test speed and mobile.
  4. Crawl for internal and broken links.
  5. Test hreflang and the language switcher on multilingual pages.
  6. Do forms, payments and integrations work? Are analytics and conversion tracking set up?

Use the new website checklist for general checks.

7. Launch day

  • Choose a low-traffic time: weekend or night.
  • Activate redirects and verify robots and noindex settings.
  • Submit the sitemap.
  • Check key pages by hand; do URL inspection in Search Console.
  • Have a quick rollback plan (see the disaster recovery plan).
  • Keep the team and agency reachable.

8. Post-launch monitoring

Monitor daily in the first weeks, weekly in the following months:

  1. Search Console: Coverage report (errors, excluded pages), crawl stats, rankings and clicks.
  2. Analytics: Organic traffic and conversions; compare with before the move.
  3. 404 report: Find old addresses whose redirects were forgotten and redirect them.
  4. Ranking tracking: Critical keywords.
  5. Speed and errors: Real user data.

Temporary fluctuation is normal; if there is no recovery within a few weeks, run a technical audit. The most common post-move problems: forgotten redirects, wrong canonicals, noindex and a broken multilingual structure.

9. If the brand name, domain or structure changes

A domain change needs a more careful process: change-of-address notice in Search Console, 301 for all addresses, updating external links, updating map profiles and social accounts. See Google Business Profile and local SEO.

Common mistakes

  • Starting design without an inventory of old addresses,
  • Forgetting redirects or redirecting everything to the home page,
  • Shortening content and breaking heading structure,
  • Leaving noindex or robots blocking on live,
  • Overlooking speed and mobile quality on the new site,
  • Leaving the move unmonitored,
  • Breaking multilingual relationships,
  • Changing domain, design, content and technology at once and being unable to isolate the fault.

Summary checklist

  1. Record current performance and addresses.
  2. Keep addresses as far as possible; prepare a mapping table.
  3. Preserve or improve content.
  4. Apply 301 redirects.
  5. Verify technical SEO and speed.
  6. Run comprehensive checks on a test environment.
  7. Switch at a low-traffic time with backup and rollback plan ready.
  8. Monitor closely in the first weeks and fix errors.

To manage the project, how to manage a software project and, for cost, website cost help.

ujans runs SEO inventory, redirect planning, technical validation and post-launch monitoring together in website redesign projects.

Looking for help with this?

Tell us what you need and our team will get back to you within one business day.

Get a quote