Website decision checklist
Website Redesign Checklist: When to Rebuild and When to Optimize What You Have
A redesign checklist for local businesses evaluating performance, crawlability, content, conversion paths, analytics, ownership and whether a full rebuild is actually necessary.
Direct answer
Rebuild a website when the platform, structure or code prevents the business from fixing core problems such as mobile performance, crawlability, page architecture, conversion tracking, lead capture or ongoing content expansion. Optimize the existing site when the foundation is technically sound and the problems are mostly copy, navigation, calls-to-action, local content or analytics. A redesign should solve a measurable business or search problem, not simply make the colors newer.
Key takeaways
Check the technical foundation
Review mobile performance, crawlability, indexing, HTTPS, canonical URLs, sitemap behavior, broken links and how easily new pages can be created. If basic fixes require fighting the platform every time, a rebuild may be more scalable than repeated patches.
- Mobile loading and Core Web Vitals
- Clean indexable URLs and canonicals
- Sitemap and robots behavior
- Structured data that matches visible content
- Editable service, location and case-study architecture
Check the customer journey
A redesign should make the next action easier. Test whether a mobile visitor can understand the service, trust the company and call, request an estimate or book without hunting through the site.
Track these actions before launch so the business can compare conversion behavior instead of relying on opinions about the new design.
Protect search equity during migration
Inventory the URLs that already receive search traffic or links. Keep important URLs when possible and create permanent redirects when a page must move. Do not launch a new site with a completely different URL structure and hope search engines work it out.
Decide whether content depth is the real problem
Sometimes the site does not need a rebuild. It needs better service pages, location content, case studies, FAQs, proof and internal links. If the existing CMS can publish those cleanly, improve the content layer first.
Post-launch validation
After launch, test priority URLs, forms, phone links, booking, analytics events, redirects, Search Console, sitemap output and structured data. A redesign is not finished when the homepage looks correct; it is finished when search and lead systems still work.
Frequently asked questions
Will a website redesign automatically improve SEO?
No. A redesign can improve technical and content foundations, but rankings depend on usefulness, crawlability, relevance, authority and many other signals. A careless migration can also hurt existing visibility.
Should I change every URL during a redesign?
No. Preserve useful existing URLs when practical. If a URL changes, map it to the most relevant replacement with a permanent redirect.
Do I need a new website to add CRM and automation?
Not necessarily. If the current site can reliably connect forms, calls and booking to the CRM, automation can often be added without rebuilding the public website.
What should be measured after launch?
Monitor indexing, priority keyword and page visibility, calls, forms, booking, conversion rate, mobile performance and CRM outcomes such as qualified opportunities and closed work.