What to ask for before a website rebuild
The fastest rebuilds start with clear constraints: what stays, what changes, and how success will be measured.
A rebuild is not only design and development. It is decision making. The best projects move quickly because the goals and constraints are clear from day one.
The questions that save time later
- What is the primary outcome
Leads, sales, bookings, hiring, investor trust, or support reduction. - Who is it for
The top audiences and the top user paths they need. - What content stays
Pages that must be kept, merged, rewritten, or removed. - What must not break
SEO, forms, analytics, payments, integrations, or internal workflows. - What is the launch deadline
A date, plus what is in scope for that date.
A simple rebuild plan
- Audit: current pages, traffic, and conversion paths
- Structure: navigation and page hierarchy
- Design: templates and reusable components
- Build: SSR pages, clean CSS, fast performance
- Ship: redirect map, QA, and post launch fixes
Most rebuild delays come from unclear content and unclear ownership, not from code.
How to know it worked
Pick a few measurements before you start. For example: faster load time, fewer support requests, higher form completion, and clearer navigation.
When the rebuild is tied to real outcomes, the decisions become easy.
Figures
