Updated September 23, 2026 · Editorial review by Iron Digital MI
Start a redesign with a documented problem: customers cannot find the right service, the main action fails on phones, content is out of date or your team cannot maintain the site. The age of a design alone does not establish the need for a rebuild.
Record what is working now
Save the existing page list, search performance, inquiry volume and important external links. Identify the pages customers use to make decisions. Keep useful content and working URLs when possible; a redesign should not discard evidence simply to create a blank canvas.
Prioritize the customer’s task
Write down the main journey and where visitors get stuck. Inspect forms, menus and mobile layouts. Decide whether a focused fix, content update or broader redesign addresses the problem. A broken notification may need an integration repair rather than a new homepage.
Protect established routes
When a URL must change, map it to the closest relevant replacement and test the redirect. Update internal links, canonical tags and the sitemap. Do not redirect unrelated old pages to the homepage just to avoid an error screen.
Review before launch
Check desktop and mobile pages, keyboard access, image loading and form error states. Test notifications and analytics with labeled test submissions. Compare titles and important content with the old site. Give the business owner a way to correct operational details before publishing.
Evaluate after launch
Watch indexing reports, errors and completed inquiries. Compare results with a suitable baseline while accounting for seasonal demand, campaigns and changes in the offer. A redesign does not have a standard bounce-rate improvement or a guaranteed ranking outcome.
Explore the details
Plan the next improvement.
Tell us what your customers need to do and where the current experience gets in their way.
Start a project →
