Planning a Website Redesign Without Losing Your SEO Rankings
Start With a Full Crawl Before You Touch the Design
A website redesign is exciting, but it is also one of the fastest ways to destroy organic visibility if you treat content and URLs as an afterthought. Before a single mockup is approved, crawl your current site with tools such as Screaming Frog or Sitebulb and export every URL, title tag, meta description, heading and internal link. That export becomes your migration checklist and your safety net. At Design Logix we treat this crawl as the single source of truth for the entire project.
Group the crawl by template type, such as service pages, blog posts, category pages and contact pages. This grouping-desigxd lets you map old URLs to new ones in batches rather than page by page. It also reveals thin or duplicate content that should be consolidated instead of blindly copied into the new design. The clearer this inventory is, the fewer surprises you will face after launch.
Map Every URL and Decide What Happens to It
Every existing URL needs a destination. Create a spreadsheet with three columns: old URL, new URL and action. The action will usually be keep, redirect, merge or retire. Keep the same slug whenever the page survives with the same intent, because an unchanged URL is the cheapest form of SEO preservation. When a page moves, use a 301 redirect to the closest equivalent, never to the homepage.
- Keep: same content, same URL, new design.
- Redirect: same content, new URL, one-to-one 301.
- Merge: several old pages become one stronger page.
- Retire: no replacement, so return a 410 rather than a soft 404.
Redirect chains and loops waste crawl budget and dilute link equity, so point old URLs directly at the final destination. Avoid redirecting everything to the homepage, because search engines may treat that as a soft 404 and drop the original rankings entirely.
Migrate Content Without Losing Its Value
Copy should move with its structure intact. Preserve heading hierarchies, internal links, image alt text and schema markup, because these signals tell search engines what each page is about. If the redesign changes copy, keep the primary topic and search intent stable; a refresh is fine, but a complete rewrite of every ranking page is risky. Move one section at a time and compare the live version against the staging version.
A redesign should change how a page looks, not what it is about.
Update canonical tags, hreflang attributes and XML sitemaps as part of the migration, not after it. If you use a CMS, confirm that the new templates output the same semantic HTML elements the old ones did. For ecommerce or large sites, an HTML table mapping old to new URLs helps developers and reviewers verify each step before launch.
| Old URL | New URL | Action |
|---|---|---|
| /services/web-design | /services/website-design | 301 redirect |
| /blog/seo-tips | /blog/seo-tips | Keep |
| /old-landing-page | /services/ | Merge |
Test Redirects, Then Monitor After Launch
Once the redirect map is built, test it in staging with a crawler that follows redirects and flags chains, loops and broken targets. Check that every old URL returns a single 301 to a live, relevant page. Then run a full crawl on the new site to catch orphaned pages, missing canonicals and accidental noindex tags before real users and bots arrive.
- Crawl the staging site and compare it with the baseline export.
- Verify each redirect resolves in one hop to a 200 status page.
- Submit the updated sitemap and watch coverage in Search Console.
- Track rankings, organic traffic and conversions weekly for at least a month.
After launch, keep the old sitemap available for a while and monitor server logs for 404s hitting retired URLs. Fix any unexpected errors quickly, because early signals shape how search engines treat the new design. A careful migration protects the visibility you already earned while giving the brand a fresh, faster experience.
