Live Free Software logo: mountains and a pine tree under a crescent LiveFreeSoftware Free Trial
0%

Website Redesign or Rebuild? How to Decide Which You Need

By Giles CollinsPublished November 15, 2026Updated November 15, 20267 min read

Short answer

Redesign it if the bones are good: it loads fast, works on phones and you can edit it yourself, but it looks dated or says the wrong things. Rebuild it if the platform is the problem, like a slow theme, a broken mobile layout or a site nobody can log into. Either way, keep your old web addresses or redirect them so Google doesn't lose track of you.

I've moved from Vermont to Florida to New Hampshire, so I know the feeling of staring at a box in the garage and asking, "Is this even worth packing?" Your website deserves the same question.

Think about a kitchen. If the cabinets are ugly but the plumbing works, you paint and swap the handles. If the pipes leak behind the walls, new paint won't save you. Websites work the same way. Some need fresh paint, and some need new pipes. This article will help you tell which one you've got. If you'd rather have us look, that's what our website redesign service is for.

What's the difference between a redesign and a rebuild?

People use these words loosely, so here's how I use them:

  • Redesign (or refresh): same platform, and mostly the same web addresses. You change the look, rewrite pages, swap photos and tidy up the menu.
  • Rebuild: a new platform or new code from scratch. Every page gets rebuilt, and the web addresses often change too.

A redesign is usually faster and cheaper. A rebuild is more work, but sometimes it's the only fix that sticks.

When is a redesign enough?

If most of these sound like your site, a refresh is probably all you need:

  • It loads quickly on a phone.
  • You can log in and change your hours without calling anyone.
  • Google already sends you visitors, and you'd just like more of them to call.
  • The problem is mostly how it looks or what it says.
  • Your services changed and the pages never caught up.

Say you run a landscaping company and added snow plowing two winters ago, but the site still only talks about mowing. That's a writing problem. Add a plowing page, fix the home page, put up recent photos, and you're done.

When do you need a full rebuild?

These are the signs the problem is behind the walls:

  • It's slow because of the theme or platform itself, and shrinking a few photos didn't help.
  • Menus, buttons or forms break on phones.
  • Nobody can edit it. The person who built it moved on, and you don't have the logins.
  • It runs on old software that hasn't had a security update in years.
  • You need tools it can't add, like online booking or a CRM that keeps every lead in one place.
  • Every small change turns into a developer invoice.

Say you own an auto repair shop, and your nephew built the site on his laptop years ago. He's in college three states away now, the login lives in an email account nobody remembers, and the site still lists a mechanic who retired. You could chase down the logins and patch it, but at some point starting fresh on something you control is the faster road.

That last bullet sneaks up on people. A $75 change here and a $150 change there can quietly add up to the price of a new site.

How do you check your site's health?

Before you decide, get some facts. Google grades page experience with three measures it calls Core Web Vitals. For a good score, the main content should show up within 2.5 seconds, the page should react to a tap within 200 milliseconds, and the layout shouldn't jump around while it loads (a shift score of 0.1 or less). Those numbers come from Google's Core Web Vitals guide, and they're based on real visitors' phones and computers.

You don't need to memorize any of that. Run your site through our free Website Grader and look at the phone score first, since that's the version Google ranks. Write the scores down. After the change, you'll want something to compare against.

Then do the human test. Open your site on your phone, pretend you're a customer, and try to call you or ask for a quote. Count the taps. If it takes more than three or four, write that down.

How do you keep your Google rankings when you change things?

This is where most redesigns go wrong. Every page has a web address, and Google has learned which addresses to show for which searches. Change the addresses without telling Google, and those pages can drop out of the results.

The fix is a redirect. A 301 redirect is a permanent forward from the old address to the new one, like forwarding your mail after a move. Google's guide to moving a site with URL changes says to:

  • List every old address and where it should point.
  • Use permanent redirects (301 or 308), and send each old page straight to its new page instead of through a chain of hops.
  • Keep the redirects for at least a year, and longer if you can.
  • Submit your new sitemap in Google Search Console.

Google also says to expect rankings to bounce around for a while during a move. For a small or medium site, it can take a few weeks for most pages to settle. So don't panic in week one.

Timing matters here in New England. If your work is seasonal, like plowing, landscaping or heating and cooling, launch during your slow months, not the week before the phones should start ringing.

With a redesign that keeps the same addresses, you skip most of this. That's one more point in favor of refreshing when you can.

Can you redesign in pieces?

Yes, and for a small business it's often the smartest way to do it. You don't have to change everything on one scary launch day.

Start with the pages that matter most: the home page, your main services page and your contact page. Fix those, watch your calls and form fills for a month, then move on to the next batch. You learn what works as you go, and if something dips, you know exactly which change caused it.

A full rebuild is harder to do in pieces, because the new platform has to be ready before anything moves. Even then, you can launch with your core pages first and add the extras, like a blog or a photo gallery, after the dust settles.

What should a rebuild plan include?

If you do go for a rebuild, whether you do it yourself or hire it out, the plan should cover these before anyone touches a template:

  1. A list of every page on the old site, with notes on which ones get visitors.
  2. The redirect list: each old address and the new address it points to.
  3. The words, written before the design. It's much easier to design around real text.
  4. A test on real phones, both iPhone and Android, before launch.
  5. A plan to leave the old site running until the new one is checked.
  6. Someone watching Search Console and your lead numbers for the first month or two after launch.

What should you keep from the old site?

  • Pages that already get visitors. Google Search Console shows which pages earn clicks. Keep them and make them better.
  • Real reviews and testimonials, with your customers' permission.
  • Your best photos of real jobs.
  • Your domain name. Changing it is a much bigger move than changing the design.
  • Any page that other websites link to.

Let the rest go without guilt. Nobody will miss the stock photo of two people shaking hands.

Common mistakes

  • Launching without redirects and losing pages Google used to show.
  • Rewriting everything at once, so you can't tell what helped and what hurt.
  • Falling for a template before listing what the site actually needs to do.
  • Forgetting the small stuff: where the contact form sends, your hours, the little icon in the browser tab and your tracking code.
  • Cancelling the old hosting before the new site is live and tested.

When isn't a rebuild worth it?

If your site is only a few months old, give it time. New sites often take a while to show up in searches, and tearing it down just adds more change while Google is still figuring it out.

The same goes if the real problem is outside the site, like no reviews or a half-empty Google profile. A shiny new site won't fix those. I wrote about that side in why your website isn't getting leads, and if you're weighing doing the work yourself, see DIY website builder or hire a pro.

Whichever way you go, our Website Launch Checklist covers the testing before go-live, and website maintenance keeps the site from going stale again.

FAQ

Redesign and rebuild questions.

What owners want to know before they tear anything down.

Not sure what your site needs?

Tell us what's bugging you about it, and we'll answer in plain English.

Contact us

How often should a small business redesign its website?

There's no fixed schedule. Refresh it when your services, prices or photos are out of date, or when it fails the phone test. Small updates every few months usually beat a big overhaul every five years.

Will a redesign hurt my SEO?

It can if web addresses change without redirects, or if pages that ranked get deleted. Keep addresses where you can, redirect the rest with 301s, and expect some ups and downs for a few weeks.

Can I keep my domain name if I rebuild?

Usually, yes. The domain and the website are two separate things, so you point the domain at the new site when it's ready. Check first that the domain is registered in your name.

Should I switch platforms while I redesign?

Only if the platform is the problem. Changing the platform and the web addresses at the same time is the riskiest kind of move, so have your redirect list ready before launch day.

See all FAQs

About the author.

Giles Collins, founder of Live Free Software

Giles Collins

Giles founded Live Free Software in Manchester, NH, in 2026. Before that he worked in the music industry and ran a pressure washing business, so he writes from the owner's side of the counter.

Connect on LinkedIn

Ready to fix the site you have?

Try every tool free for 5 days, or book a call and we'll tell you if it needs a refresh or a rebuild.