Most businesses reach for a redesign when what they actually need is a rebuild. The two solve different problems, and choosing the wrong one wastes both budget and time.
A redesign changes how your site looks: layout, colors, typography, imagery. A rebuild changes what your site is made of: the codebase, the database structure, the hosting environment. If your problem is that customers find the site ugly or dated, a redesign solves it. If your problem is that the site is slow, breaks on mobile, cannot be updated without a developer, or is invisible in search results, no amount of visual polish will fix it.
Here are seven signs pointing to a rebuild:
1. Page load times exceed three seconds on mobile. 2. Your last three redesigns were on the same underlying codebase, and each one felt harder than the last. 3. Content updates require a developer for even simple text changes. 4. Your site is not indexed properly, or key pages do not appear in search at all. 5. It cannot support features you actually need, like online payments or account logins. 6. Security patches are months or years behind. 7. Your hosting provider cannot explain why uptime is inconsistent.
If three or more of these apply, start the conversation with a technical audit before a design conversation. It is the only way to know what you are actually paying to fix.