The website redesign vs rebuild decision depends on where the problem lives. If visitors are put off by how the site looks and reads but the platform is sound, redesign. If the site is slow, fragile, hard to update or impossible to extend because of how it is built, you need a rebuild, or at least a re-platform. Often it is a mix.
What the problem actually is
Teams often say "the site needs a redesign" when they mean several different things. Sort your complaints into three buckets before you talk to anyone:
- Presentation: dated look, unclear messaging, weak calls to action, poor mobile layout.
- Structure and content: confusing navigation, thin or duplicated pages, content that no longer matches your offer.
- Platform: slow pages, frequent breakages, plugins nobody dares update, security worries, a content system staff dislike, or features the platform cannot support.
Back each complaint with evidence: analytics, support questions, speed tests, staff feedback. A redesign fixes the first bucket and partly the second. A rebuild addresses the third, and usually lets you fix the others at the same time.
Redesign: what it can fix
A redesign changes the visual layer and often the page layouts, while keeping the underlying platform, content structure and URLs largely as they are. It can reasonably fix:
- Brand and visual consistency, and clearer hierarchy on key pages.
- Mobile layout problems, where the platform already supports responsive templates.
- Clarity of messaging, calls to action and forms.
- Basic accessibility issues such as contrast and focus states.
It will not fix slow hosting, a tangled database, abandoned plugins or a content model that cannot express what you sell. A common failure is a beautiful new theme on a platform that is still slow and fragile, so the problems return within months.
Rebuild: what it can fix
A rebuild replaces the underlying system, whether by moving to a different content management system or building custom. It makes sense when:
- The codebase or theme is so tangled that small changes are slow and risky.
- Performance problems are structural and have not responded to tuning; see our notes on fixing Core Web Vitals.
- Security updates cannot be applied because everything depends on outdated components.
- You need integrations, account areas, or workflows the current platform cannot support.
- Editors cannot manage content without developer help.
The platform choice itself is a separate decision; for that comparison, see custom eCommerce versus Shopify and WooCommerce for stores, or the WordPress-versus-custom discussion for brochure and lead-generation sites. A rebuild is a larger undertaking, so it needs a clearer business case.
SEO risks of changing URLs
Will a redesign hurt my SEO?
Not necessarily. A redesign that keeps URLs, headings, page content and internal links largely intact carries limited search risk, though changes to layout and speed can still shift results in either direction. The danger comes from changing things search engines rely on without a plan.
How do I preserve rankings in a rebuild?
- Inventory the existing site: export all URLs, titles, headings and the pages that bring in traffic or links.
- Keep URLs where you can. Where they must change, map every old URL to the most relevant new one.
- Use permanent redirects for each mapping, and test them before launch.
- Carry over on-page elements: titles, meta descriptions, headings, structured data, image text and internal links.
- Preserve content that performs. Do not delete useful pages just because the new design is simpler.
- Launch with monitoring: check indexing reports, crawl errors and traffic daily for the first weeks.
Expect some turbulence after a major change even with good preparation, and avoid launching during your busiest season. Results are never certain, so treat these steps as risk reduction, not a promise.
Content and data migration
Content is often the hidden cost of a rebuild. Decide early what moves, what is rewritten and what is retired. Audit pages and sort them into keep, improve, merge and remove. Then list the data that is more than pages: users, orders, form submissions, media files, comments and redirects already in place. Test a sample migration early to find formatting problems and broken links, and plan a content freeze, so nothing is edited on the old site while the new one is being finished. If the site is an online store, our guide on website performance checks can also help you set a baseline before and after.
Budget and timeline implications
Redesigns are usually smaller than rebuilds, but the gap depends on scope, not labels. The main drivers are the number of templates and page types, the amount of content to migrate, integrations, custom functionality, accessibility work and how many rounds of review your team needs. We do not quote figures here because they vary too much; ask for a breakdown that separates design, build, migration, testing and launch support. The principles in our article on what drives custom software costs apply here too.
Can I do it in phases?
Yes, and it is often wise. You can redesign the highest-impact templates first, rebuild one section such as the blog or checkout on a new platform, or run old and new side by side during a transition. Phasing lowers risk, though it means living with some inconsistency in the meantime and managing redirects and navigation carefully.
Website redesign vs rebuild: a decision flow
- Is the platform fast, secure, maintainable and able to support your next two years of plans? If yes, redesign.
- Is the content structure the problem? Restructure content and navigation, which may be possible within a redesign.
- Are the issues structural, such as performance, security, features or editing? Plan a rebuild.
- Is the risk to search traffic high? Phase it and protect URLs.
- Unsure? Commission a short audit of performance, security, content and analytics before choosing.
Putting it together
Name the problem first, collect evidence, and let that decide the scale of the work. If you would like a second opinion on whether your site needs a refresh or a rebuild, our US software development page explains how we start, and the packages page shows typical engagement shapes.
Frequently asked questions
Will a redesign hurt my SEO?
Not necessarily. If URLs, headings, content and internal links stay largely the same, search risk is limited, although layout and speed changes can still move results either way. Risk rises when pages are deleted, URLs change without redirects or content is rewritten heavily. Monitor indexing and traffic closely after launch.
How do I preserve rankings in a rebuild?
Inventory every existing URL and its performance, keep URLs where possible, map and permanently redirect any that change, and carry over titles, headings, structured data and internal links. Keep pages that perform. Test redirects before launch and monitor crawl errors and traffic afterwards. No process removes all risk.
Can I do it in phases?
Yes. You can redesign the highest-impact templates first, rebuild one section on a new platform, or run old and new in parallel. Phasing spreads risk and spend, but it needs careful navigation, redirects and design consistency during the transition. A short audit helps you pick the order.