Website Redesign: Can Your Old Site Be Saved, and How

Whether to save an old site depends on three things: whether existing content and traffic have value, whether technical issues are localized, and whether the bu…

Insights:Website Redesign: Can Your Old Site Be Saved, and How

Start with an Old Site Health Check

Dimension What to Check Conclusion
Traffic Which pages receive organic traffic Pages with traffic must be retained or mapped
Content Whether there is reusable content Prioritize migrating existing content
URLs Current links and indexing status Determines the scope of 301 redirects
Technology Speed, errors, mobile responsiveness Helps decide whether it's a partial or complete overhaul
Business Can you afford to wait? Determines the migration timeline

The audit produces a page list classified as "keep / merge / remove / build new" — don't jump straight into designing the new homepage.

Three Approaches

1. Partial Optimization

Ideal for: Structure is usable; issues are concentrated around speed, styling, forms, or individual sections.

Actions: Fix performance, update navigation, add missing content, repair 404s. Lowest cost, lowest risk.

2. Progressive Refactoring

Ideal for: Outdated tech stack, but existing content and URLs still hold value.

Actions: Replace one layer first (e.g., frontend or CMS), keep URLs unchanged, migrate in batches. Longer cycle, fully controllable.

3. Full Rebuild

Ideal for: Severe technical debt, shifting business model, old site no longer viable.

Actions: Develop the new site in parallel. Plan content migration, URL mapping, 301 redirects, and canary cutover as one coordinated effort.

Migration Steps for a Full Rebuild

  1. Audit the old site's URLs and traffic-driven pages.
  2. Define the new site's information architecture and URL rules.
  • Create a 1:1 mapping table: old URLs → new URLs.
  • Migrate content, preserving titles, descriptions, and core information.
  • Set up 301 redirects; avoid mass 404s.
  • Submit the new sitemap and keep the old one live for a while.
  • Monitor crawling, indexing, traffic, and errors.
  • Keep access logs from the old site to catch any unmapped URLs.
  • Acceptance Checklist

    • All old URLs with traffic return 200 or 301.
    • No redirect chains or loops.
    • New site pages are indexable.
    • Navigation and site search work properly.
    • Forms submit successfully and emails are received.
    • Mobile-friendly and readable.
    • LCP and TTFB meet performance benchmarks.
    • Content can be edited in the admin panel.
    • Monitoring and backup systems are connected.

    Common Mistakes

    • Only applying a visual overhaul without fixing content and URL issues.
    • All old URLs returning 404.
    • 301 redirects pointing to the homepage instead of the corresponding new pages.
    • Creating mappings after going live.
    • No rollback plan in place.

    Pricing and Timeline Negotiations

    Quote based on "page inventory + migration volume + whether to preserve URLs + who writes content + acceptance criteria"—avoid giving just a single total price. The timeline should include content migration and testing, not just development.

    Scope and Limitations

    A redesign can address structural, experience, and technical issues, but cannot guarantee rankings or inquiries. Rankings depend on content, competition, and algorithms—the redesign is only responsible for building the foundation correctly.

    Related reading: