Redesign when the site is fast, secure and easy to edit but looks dated or converts poorly. Rebuild when pages stay slow after optimization, updates keep breaking things or the platform can’t do what you need. Either way, keep every URL that ranks or redirect it one-to-one, or the new site starts with lost traffic.
Redesign and rebuild are different jobs
A redesign changes what visitors see: layout, branding, images, navigation and copy. The platform and most of the code stay. A rebuild replaces the foundation: the CMS or framework, the code and often the structure of the site. A redesign is usually quicker and cheaper; a rebuild removes problems a new design can’t reach.
The expensive mistake runs both ways: a fresh theme on a site that is slow and fragile underneath, or a full rebuild of a site that only needed better pages. Decide from evidence, not taste.
The checklist
Answer each question honestly. Mostly yes in the first group points to a redesign; any yes in the second group points to a rebuild.
A redesign is probably enough if…
- Pages load quickly on a phone, or get there after images and caching are fixed.
- Your team can edit pages without a developer.
- Updates install without breaking the site.
- The platform can add the features you need in the next two to three years.
- The real complaint is how the site looks, reads or converts.
A rebuild is probably needed if…
- Pages stay slow on mobile after the usual speed fixes.
- Plugin, theme or framework updates regularly break something.
- The site runs on software that is no longer supported or patched.
- You can’t export your own content from the builder you are on.
- You need features, such as bookings, a customer portal or AI chat, that the current setup can only fake.
Measure before you decide
Two numbers settle most debates. First, speed from real visitors: Google’s Core Web Vitals report in Search Console and PageSpeed Insights show Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift, with good scores at 2.5 seconds, 200 milliseconds and 0.1 or better. Second, what the site earns today: export every URL with its clicks and impressions from Search Console, and note which pages bring enquiries in your analytics.
If the pages that earn traffic and enquiries are also the slow, fragile ones, a rebuild pays for itself. If they work and only look dated, protect them and redesign around them.
What each one costs you in time and risk
| Redesign | Rebuild | |
|---|---|---|
| Typical length | Weeks: a simple site often takes four to eight | Longer: content, data and redirects have to move |
| Disruption for your team | Low: same editor, new templates | Higher: new editor, training, content migration |
| SEO risk | Rewritten headings and deleted copy on pages that rank | Changed URLs, lost pages and redirect mistakes |
| What it fixes | Looks, messaging, calls to action, conversion | Speed, security, editing pain, missing features |
The SEO steps that protect your rankings at launch
- Crawl and export every current URL, with its traffic and links, before anything changes.
- Keep URLs that work. If a URL must change, map it one-to-one to its closest new page with a permanent (301) redirect. Don’t send everything to the home page.
- Carry over what ranks: titles, headings, the main copy and structured data of the pages that bring traffic.
- Block the staging site from search engines, then remove that block, and any noindex tag, before launch.
- Submit the new sitemap in Search Console and check the most important URLs with the URL Inspection tool.
- Keep the redirects for as long as possible; Google’s site-move guidance says generally at least a year, so it can pass all signals to the new URLs.
- Watch Search Console for the first weeks: indexing, crawl errors and 404s on old URLs that someone forgot.
A short wobble in rankings while Google recrawls a moved site is normal. A drop that lasts usually traces back to redirects, deleted pages or a forgotten noindex tag, so check those first.
How we approach it
Every project starts with an audit of speed, the CMS, security and the pages that earn traffic, and ends with a written recommendation: redesign, rebuild or targeted fixes. If only parts of the site are failing, targeted fixes may be all you need. If not, see our website redesign and rebuild service, or start with a free website audit.
Frequently asked questions
How often should a business redesign its website?
There is no fixed cycle. Redesign when the site no longer reflects the business, converts poorly or looks out of date next to competitors; rebuild when the platform holds you back. Many small businesses refresh every few years, but evidence such as speed, conversion and editing pain should drive it, not the calendar.
Will a redesign hurt my SEO?
Not if the pages that rank keep their URLs, headings and main content, or are redirected one-to-one to new pages that cover the same topic. Most ranking drops after a relaunch come from changed URLs without redirects, deleted pages or a staging noindex tag left on.
Can I keep my domain when I rebuild?
Yes, and you usually should. Keeping the same domain and as many URLs as possible is the safest way to rebuild. Only redirect what has to change.