A redesign usually changes how a website presents and organizes information while retaining much of its underlying platform. A rebuild replaces more of that foundation, which may include templates, content structures, integrations, or the platform itself.
The terms are not standardized, so ask a provider to describe exactly what will change. The right choice depends on the problem, not which label sounds more comprehensive.
Choose a redesign when the foundation still supports the work
A redesign may suit a site whose platform is maintained and whose important functions work, but whose presentation no longer serves customers. The navigation might be confusing, service pages inconsistent, or mobile layouts awkward.
For example, a business with reliable forms and editable content may need a clearer service structure and new page templates. Replacing the entire system could add migration work without addressing an additional business need.
Consider a rebuild when the foundation is the constraint
A rebuild may be appropriate when routine changes are fragile, required integrations cannot be supported sensibly, or the current setup is difficult to maintain. A new business model may also require a different content or transaction structure.
Investigate before deciding. A slow site might need better images or fewer scripts rather than a new platform. An editing problem might need training or a corrected template. Identify the cause and compare a repair with replacement.
Inventory what the existing site already does
Before either project, list important pages, forms, downloads, accounts, analytics, integrations, and ongoing business processes. Record which URLs attract useful visits or have links from other websites. Identify content that should be kept, improved, combined, or retired.
Ask staff what they depend on. A quiet page used by existing customers may be operationally important even if it receives little search traffic. A redesign brief should not be based only on the most visible pages.
Compare the scope in concrete terms
- Content: what will be reused, rewritten, or migrated?
- Design: which templates and components will change?
- Function: which forms and integrations must be retested?
- Operations: who will maintain the result and with what training?
- Transition: what is the launch and rollback plan?
A rebuild generally involves more transition work, but the actual scope varies. Compare written deliverables and ongoing responsibilities instead of assuming one approach is always cheaper.
Protect useful URLs and working processes
Keep existing addresses where they still fit the content. When a URL must change, map it to the relevant replacement and use an appropriate permanent redirect. Sending unrelated retired pages to the homepage is not a useful substitute for a migration plan.
Google's site migration guidance covers URL mapping, redirects, and monitoring. Test forms, internal links, canonical URLs, and indexing settings before and after launch. Prepare a backup and a recovery route if a critical function fails.
Decide from evidence
Use our six signs a website needs attention to document the problems first. Then ask for a proposal that connects each change to a specific outcome. Web Design Just For You's redesign services can help you evaluate the scope without assuming that every older site needs to start over.
