Skip to content
← All articlesWeb Development

Website redesign and migration without losing SEO: a checklist

How to redesign or replatform a website without losing search traffic: URL mapping, redirects, metadata, testing and post-launch monitoring for product teams.

A redesign or replatform is one of the few projects that can undo years of organic growth in a single deployment. The new site looks better, loads faster, and yet traffic drops because old URLs return errors, titles disappear or pages are accidentally blocked from crawling. Almost all of these losses are preventable with planning that starts before design sign-off, not after launch.

This checklist is written for the CTO, founder or product manager who owns the outcome, whether the build is in-house or with an offshore partner.

Why migrations lose traffic

Search engines rank individual URLs. When a URL changes or disappears, the signals attached to it (links from other sites, history, relevance) only transfer if you tell the search engine where the page moved. The usual causes of loss are:

  • Old URLs that are not redirected, or are redirected to the home page instead of the equivalent page.
  • Content that was thinned out or removed during the redesign.
  • Titles, headings, structured data and internal links that did not make it into the new templates.
  • A staging site setting (such as noindex or a blocked robots.txt) that was carried into production.
  • A slower or more JavaScript-heavy front end than the old one.

Phase 1: Before you build

Inventory what exists. Export every URL from your sitemap, CMS, analytics and a crawl of the live site. Add pages that receive external links, which you can find in your search console and backlink tools.

Decide what is kept. For each URL, choose one outcome: keep as is, keep with a new address, merge into another page, or retire. Pages that earn traffic or links should rarely be retired.

Record a baseline. Save organic traffic, top landing pages, rankings for your main queries and Core Web Vitals before anything changes. Without a baseline you cannot tell whether a dip is normal turbulence or a real problem.

Phase 2: URL mapping and redirects

Create a spreadsheet with old URL, new URL, redirect type and owner. This document is the heart of the migration.

Situation What to do
Page keeps the same URL No redirect needed; check it still returns 200
Page moves permanently Single 301 redirect to the closest equivalent
Pages merged 301 each old URL to the merged page
Page genuinely removed Return 404 or 410, or redirect to a truly relevant parent

Rules worth enforcing:

  • Redirect to the most relevant page, not blindly to the home page.
  • Avoid redirect chains (A to B to C). Point old URLs straight to the final destination.
  • Keep redirects in place for a long time, ideally permanently for pages with external links.
  • Keep URLs short, lowercase and stable. If you can avoid changing them, do.

Phase 3: Carry over the on-page essentials

Check that every template in the new design supports:

  • Unique title tags and meta descriptions for each page.
  • One clear h1 and a logical heading structure.
  • Canonical tags pointing to the preferred URL.
  • Structured data (schema markup) where you had it before.
  • Image alt text and descriptive link text.
  • Internal links to your key pages, so authority flows where you want it.
  • An XML sitemap that lists only indexable, final-URL pages.
  • Hreflang tags, if you serve several languages or regions.

If the new front end renders content with JavaScript, confirm that search engines receive meaningful HTML. Server-side rendering or static generation is usually the safer choice. Our comparison of Next.js and Astro covers that trade-off.

Phase 4: Test on staging

Staging should be a rehearsal, protected from search engines by authentication rather than only by noindex, so nothing leaks into the index.

  • Crawl staging and compare it with the old crawl: missing pages, status codes, titles, canonicals.
  • Test the full redirect map automatically. Every old URL should return a single 301 to a 200 page.
  • Review mobile rendering, accessibility and performance. See the Core Web Vitals guide for the thresholds to aim for.
  • Check forms, analytics tags and conversion tracking, because a broken tracking tag looks exactly like a traffic drop.

Phase 5: Launch day

  • Remove any staging restrictions: noindex tags, password protection and Disallow rules in robots.txt.
  • Deploy redirects together with the new site, not afterwards.
  • Submit the new sitemap in Google Search Console and confirm the site is verified. If the domain changes, use the change of address tool.
  • Launch at a quiet traffic time, with developers and an SEO owner available for the first hours.
  • Keep a rollback plan for the case where critical templates are broken.

Phase 6: Monitor for 90 days

Expect some fluctuation as search engines recrawl. What matters is the trend against your baseline.

  • Watch crawl errors and coverage reports in Search Console daily for the first weeks.
  • Re-crawl production and look for 404s, redirect chains and unexpected noindex directives.
  • Compare landing page traffic with the baseline and investigate any important page that falls sharply.
  • Update internal links so they point to new URLs directly rather than through redirects.
  • Fix issues in small, quick releases instead of waiting for the next big sprint.

Working with an outsourced team

Make SEO requirements part of the written scope, not an afterthought. Ask that the redirect map, crawl comparisons and launch checklist are deliverables, and that someone is named as accountable for each. If the project is delivered by an offshore partner, agree a clear definition of done that includes crawl results and staging sign-off. A clear contract helps too; our MSA and SOW guide explains how to write one.

Plan your redesign with a team that checks the details

AkMo Technologies builds and rebuilds websites with SEO, performance and accessibility handled as part of delivery. Explore our web development services or get in touch to discuss your redesign or migration.

Let’s build what’s next.

Tell us about your platform, your product idea or the systems you want to modernise. Someone from our Chennai engineering team will get back to you personally.