What to remember
- Do not redesign only because the site looks old.
- Protect search equity, analytics and conversion paths during the rebuild.
- Use the redesign to remove business friction, not add decoration.
Before design starts
- Define the business objective and primary customer actions.
- Inventory existing URLs, organic landing pages and conversion points.
- Document analytics events, forms, tags and integrations that must survive the migration.
- Identify the pages that actually influence revenue or qualified leads.
During structure and content
- Build a sitemap around buyer needs and search intent, not internal departments alone.
- Give important services dedicated pages when the intent and content justify them.
- Plan internal links between services, proof, articles and conversion pages.
- Write page titles and meta descriptions that accurately describe each page.
During design and development
- Design mobile journeys intentionally.
- Keep critical content as accessible HTML text rather than hiding it inside images or canvas elements.
- Use semantic headings and descriptive link text.
- Compress images, reserve image dimensions and avoid unnecessary scripts.
Before launch
- Map old URLs to the best new equivalents using 301 redirects.
- Test forms, calls, bookings and analytics events.
- Check canonical tags, robots rules and sitemap URLs.
- Review page titles, descriptions, Open Graph data and structured data.
- Crawl the live site for broken links and accidental noindex tags.
After launch
Submit the sitemap in Google Search Console, monitor indexing and watch important organic landing pages for unexpected drops. A redesign is a release, not the end of the project.
Protect what already works
A redesign should preserve useful equity. Before changing URLs, export the current sitemap, top organic landing pages, backlinks if available, conversion pages and any pages sales teams regularly send to prospects. Those assets tell you what must be preserved, improved or intentionally retired.
When pages are consolidated, redirect old URLs to the closest relevant replacement-not automatically to the homepage. Keep a redirect map as part of the launch checklist and test it after deployment.
Redesign handover checklist
- Final sitemap and URL map documented.
- Redirects tested.
- Forms and integrations tested with real submissions.
- Analytics events confirmed in production.
- Sitemap and robots.txt reviewed.
- Page titles, descriptions and canonical tags checked.
- Mobile layout and core journeys reviewed on real devices.
Redesign decision framework
What business problem is the redesign solving?
What traffic, leads and pages matter today?
What should stay, merge, move or disappear?
What must become clearer or easier?
What events and outcomes must survive launch?
How will redirects, QA and indexing be verified?
Example: redesign without losing the useful parts
A service page may look visually dated but still attract qualified organic traffic. Instead of deleting it, preserve the URL or redirect carefully, improve the content and conversion path, and verify performance after launch.
Frequently asked questions
Can a redesign hurt SEO?
Yes, especially when important URLs disappear, content is removed or redirects are mishandled. Good migration planning reduces that risk.
Should we keep every old page?
No. Keep, merge or redirect pages based on usefulness, search demand, links and business relevance-not nostalgia.