Website Redesign Checklist: 18 Questions Before You Rebuild
A redesign should fix more than the color palette. These questions will help you protect what already works, uncover what is missing, and build a site your team can live with after launch.
Strategy and audience
1. What must be different after launch?
“Modernize the site” is less helpful than “make our services easier to compare,” “generate better-fit inquiries,” or “support new locations without duplicating every page.”
2. Who are the priority audiences?
Customers may not be the only audience. Partners, candidates, referral sources, vendors, and internal staff may need straightforward routes too.
3. Which offers matter most?
Priority should reflect the business’s actual capacity, direction, and the customers it wants—not only search volume.
4. What questions appear before the first contact?
Ask sales and service teams what people misunderstand. Those questions often reveal the most important missing content.
Content and trust
5. What is worth keeping?
Inventory pages, downloads, team bios, videos, FAQs, and high-performing resources before deleting anything.
6. Who owns accuracy?
Assign responsibility for service details, claims, team information, and future updates.
7. Are trust signals specific?
Experience, process, credentials, real examples, policies, and specific business details are better evidence than unsupported labels like “best.”
8. Does a mobile visitor know what to do next?
Important actions should be visible, appropriately worded, and realistic for the offer.
Search and migration
9. Which URLs currently earn visibility or links?
Use analytics and search data to identify pages worth preserving. Changing every URL without redirects can discard years of value.
10. Does each priority offer deserve a focused page?
A strong service page explains the problem, who the service is for, how it works, what supports the claim, and what to do next.
11. Are services, locations, and team relationships clear?
People and search systems both benefit when the website shows how these parts connect.
12. What is the redirect and validation plan?
Map old URLs, check links, test forms, validate analytics, submit the sitemap, and monitor crawl issues after launch.
Technology and operations
13. Who will update the site?
Choose tools around the real team. A powerful platform nobody can safely use is not a practical system.
14. Which integrations are truly required?
List forms, scheduling, CRM, call tracking, analytics, maps, recruiting, ecommerce, and other systems. Separate launch needs from future improvements.
15. What accessibility standard guides the work?
Accessible design depends on semantic structure, keyboard support, focus visibility, contrast, labels, readable content, and ongoing publishing habits.
16. What information should forms collect?
Collect only what the team needs to give a helpful first response, and decide where submissions go and who can access them.
Measurement and ownership
17. Which actions will be measured?
Decide which calls, forms, purchases, bookings, quote requests, and campaign sources should count. Not every click is an equal conversion.
18. Who owns each launch responsibility?
Write down ownership for content approval, domain and hosting access, redirects, analytics, form delivery, integrations, quality assurance, and monitoring.
Start with the decision, not the theme
Agree on what customers should understand, what the website should help the business accomplish, and what the team can realistically maintain. The theme comes later.