1. Define the business reason for the redesign
Start with a concrete problem. The site may be attracting the wrong leads, hiding the strongest service, creating friction on mobile, ranking for irrelevant queries, or simply no longer representing the business accurately. “It looks old” can be true, but it is rarely a complete brief.
2. Audit the content before changing the sitemap
Export or list every important URL. Mark each page as keep, improve, merge, redirect, or remove. Look for overlapping pages, outdated promises, thin service pages, forgotten campaign URLs, and strong pages that should not lose their search equity.
3. Rebuild the information hierarchy
A redesign is an opportunity to reduce navigation ambiguity. Visitors should be able to answer three questions quickly: what do you offer, who is it for, and what should I do next? Group pages around user intent rather than internal departments.
4. Protect technical SEO
- Map old URLs to new URLs before launch.
- Preserve canonical intent and indexable pages.
- Keep title tags and descriptions specific to each page.
- Use one descriptive H1 and a logical heading hierarchy.
- Generate a clean sitemap and verify robots rules.
- Check structured data after templates change.
5. Design responsive behavior, not desktop screenshots
Decide how hierarchy changes across screen sizes. Navigation, CTA placement, long headings, grids, forms, imagery, and tables all need explicit mobile behavior.
6. Set performance constraints early
Large image files, unnecessary libraries, third-party scripts, and excessive motion can turn a visually polished site into a slow experience. Treat loading cost as part of the design system.
7. QA the launch like a migration
Crawl key URLs, test forms, verify analytics hooks, check canonical tags, submit the sitemap, inspect mobile layouts, and monitor 404s. A redesign is not complete when the homepage looks finished; it is complete when the full system works after launch.
Published October 2, 2026. Written by Gozin.