Nov 3, 2026 · By Chris Holtzlander
Website redesign vs new website: which one do you need?
Refresh, redesign or rebuild? How to tell which job your site needs, what moves the cost, and how to change it without losing the Google traffic you already have.
A lot of calls I get start the same way: "I think I need a new website." Sometimes that is right. Often the site needs a smaller job than the owner fears, and every so often it needs a bigger one than they hoped. The words people use for these jobs are loose, so here is how I would sort it out with a friend, plus the one part of a redesign that can quietly cost you customers if nobody handles it: the Google traffic you already have.
Signs your website needs work
None of these alone means "start over." Count how many apply.
- It is hard to use on a phone. Tiny text, a menu you cannot tap, a phone number you cannot press to call. Google mainly looks at the mobile version of your site, so this one hurts twice.
- It is slow. Run it through PageSpeed Insights. I explained the numbers to look for in how to choose a website designer.
- It says the wrong things. Old prices, services you stopped offering, the one you are now known for missing entirely.
- You cannot change it yourself. Every small edit is an email and an invoice, so it never gets done.
- It does not bring in calls or forms, even though people clearly visit.
- Nobody can update it safely. An old theme or plugin that cannot be updated without breaking, or a builder you no longer have the login for.
- It no longer looks like your business. New logo, new van wrap, old website.
Refresh, redesign or rebuild: three different jobs
These get used as if they mean the same thing. They do not, and the price gap between them is large.
A refresh
Same site, same structure, same platform. You update the words, swap in real photos, fix the contact form, tighten the home page and maybe update colors to match a new logo. This is the right call when the site works and is easy to edit but has drifted out of date. It is the cheapest of the three, and it carries almost no risk to your search traffic because the pages and addresses stay where they are.
A redesign
New look and new layout, usually on the same platform and the same domain. Pages get rewritten, merged or split. The menu changes. This is the right call when the bones are fine but the site does not explain what you do, or does not work well on a phone. Most of the risk lives here, because a redesign is when page addresses change without anyone noticing.
A rebuild (a new website)
A new site from scratch, often on a new platform, sometimes on a new domain. This is the right call when the platform itself is the problem: it cannot be updated, it is too slow to fix, you cannot edit it, or it cannot do something you now need, like booking or selling online. A rebuild is also a chance to organize the site around what people actually search, with one page for each service you want to be found for.
A quick way to decide: if the problems are mostly about words and pictures, refresh. If they are about layout and clarity, redesign. If they are about the platform, the speed or what the site can do, rebuild.
What a website redesign costs
The honest answer depends on four things, and they are the same four that move the price of a brand new site:
- Page count. Rewriting fifteen service pages is more work than five.
- Selling online. Products, shipping rules, tax and payments.
- Booking or scheduling, especially when it has to match a calendar you already use.
- Content migration. Moving years of existing pages and posts without breaking the links Google already knows about.
That last one is the line item people forget, and it is the one that protects your traffic. A quote that does not mention old pages at all is a quote that will probably skip it.
One thing that surprises owners: a redesign is not always cheaper than a rebuild. If the old site is built on something slow or hard to update, patching it can cost nearly as much as starting fresh, and you end up with a nicer coat of paint on the same problem. I broke down what the market charges for a new build, and what moves the price, in what a website costs in Phoenix, which is a useful yardstick for any redesign quote.
How to redesign without losing your Google traffic
This is the part that goes wrong most. The new site launches, it looks great, and a month later the phone is quieter. Usually the cause is simple: the old page addresses stopped working, so every link Google had for you now leads to an error page. Google publishes a guide to site moves with URL changes, and the steps below follow it.
1. Make a list of every old page before you touch anything
Google says it is important to "map your old site's URLs to the URLs for the new site." In practice, that means a simple spreadsheet: old address in one column, new address in the other. Pull the old addresses from your sitemap and from the Performance report in Google Search Console, which shows which pages actually get clicks. Those are the pages you cannot afford to lose.
2. Keep the addresses that already work
The safest redirect is the one you never need. If /roof-repair ranks well, the new roof repair page should live at /roof-repair too. Change an address only when there is a real reason.
3. Redirect every address that changes, permanently
When a page does move, the old address should send visitors and Google to the new one with a permanent, server-side redirect, usually a 301. Google's redirects guide says a permanent redirect is a signal that "the redirect target should be canonical", which is Google's word for the version it shows in results. Two rules from Google's move guide matter most:
- Do not send many old pages to one unrelated page, like the new home page. Google says this can confuse users and may be treated as a soft 404, an error in disguise.
- Keep the redirects "for as long as possible, generally at least 1 year."
If you are genuinely removing a page and nothing replaces it, Google says it should return a proper 404 or 410 error, not a redirect to somewhere random.
4. Update your own links and your sitemap
Change the links inside the new site to point straight at the new addresses, so nothing runs through a redirect it does not need. Then submit the new sitemap in Search Console.
5. Only use the Change of Address tool if the domain changes
Search Console has a Change of Address tool, and people reach for it when they should not. Google says you only need it "when moving from one domain or subdomain to another." A redesign on the same domain does not need it, and neither does a switch to https or from www to no www.
6. Watch it for a few weeks, and expect a wobble
Google is upfront that you should "expect temporary fluctuation in site ranking during the move." Watch the page indexing and Performance reports in Search Console, and look for old addresses showing up as errors. A small dip that recovers is normal. A steady slide usually means redirects are missing.
If you are only changing hosting and every address stays the same, that is a different and smaller job. Google covers it separately in its guide to changing your web hosting, which suggests lowering your DNS settings' cache time, the TTL, about a week before the move.
What to keep from the old site
- Your domain. Years of links point at it. Do not change it for a redesign unless you must.
- The pages that rank. Improve them. Do not delete them.
- Your name, address and phone, written exactly as they appear on your Google Business Profile.
- Reviews and testimonials, with permission, and the photos of real jobs.
- Your analytics. Keep the same Google Analytics property so you can compare before and after.
- Form destinations. Make sure the new forms go to the same inbox, and test them.
Website redesign questions to ask before you sign
- Is this a refresh, a redesign or a rebuild, and why that one?
- Will any page addresses change? Who builds the redirect list, and can I see it?
- Is moving my existing content in the price?
- Will the domain, hosting and site files stay in my name?
- Who writes the new words?
- How will you test it on phones, and for speed, before launch?
- Who checks Search Console in the weeks after launch?
- What is the fixed price, and what is not included?
A short redesign checklist
- Export your top pages from Search Console and save a copy.
- Build the old to new address list.
- Keep every address that does not need to change.
- Set up 301 redirects for the rest, one old page to its closest new page.
- Test the new site on a phone and in PageSpeed Insights.
- Launch, submit the new sitemap, and test every form.
- Check Search Console weekly for a month, then monthly.
- Leave the redirects in place for at least a year.
How I work
When someone asks me for a redesign, the first thing I do is work out which of the three jobs it really is, and I will tell you if it is the small one. Every site I build is custom, designed and built from scratch, front end and back end, with no templates. It is quoted after a short conversation as one fixed figure before work begins, with half to start and the rest after you sign off, and payment plans are available. Moving existing content is one of the things that can move a quote, because doing it without breaking the links Google already knows about takes real time, and I would rather name that up front. Every site I build has a CMS, so you can change prices and photos yourself afterward. If your site is moving to my hosting, I move the site, the email and the DNS at no charge.
If you are weighing a redesign against starting over, here is what a site from me includes, you can see live examples in my portfolio, or tell me about the site you have now for a free quote, and I will tell you straight which job it needs. If you want to see where you stand on the map before and after, here is how to check your Google Maps ranking.
Sources
- Google Search Central, Site moves and migrations (with URL changes)
- Google Search Central, Redirects and Google Search
- Google Search Central, Changing your web hosting and SEO
- Google Search Central Blog, Mobile-first indexing has landed (October 2023)
- Google, Google Search Console
- Google, PageSpeed Insights