The website redesign vs refresh decision comes down to one question: is the structure wrong, or just the surface? If your pages are organised around what you actually sell and the site is technically sound, you need a refresh — new copy, better imagery, tightened calls to action. If the structure, platform or page set no longer matches the business, you need a redesign.
Getting this wrong is expensive in both directions. A full rebuild to fix tired copy wastes money and resets whatever search equity you have. A cosmetic refresh on a broken foundation looks better for a quarter and converts the same.
What Each One Actually Means
A refresh keeps the site’s architecture and platform. You are changing words, images, layouts within existing templates, calls to action, and small technical issues. URLs stay put. Timelines are short, usually weeks.
A redesign changes the structure. New page set, new navigation, often a new theme or platform, new templates, and a migration plan for existing URLs. Timelines run longer and involve content decisions, not just design ones.
There is a third option people forget: a staged rebuild, where you redesign a handful of high-value pages on the existing site and leave the rest alone until they earn attention.
The Five Tests
Score each test honestly. Three or more pointing to rebuild means a redesign.
Test 1: Does the Page Set Match What You Sell?
List everything you sell today. Now list the pages on your site. If you sell six services and have one “Services” page, the structure is wrong and no amount of new copy fixes it. Buyers and search engines both want a dedicated page per service.
This test fails most often in businesses that have changed what they do since the site was built — which is most businesses after three years.
Test 2: Can You Add a Page Without Calling Someone?
If adding a service page, updating pricing or swapping a photo requires a developer, your site is a cost centre rather than a tool. That is a structural problem.
A site you cannot maintain goes stale by default. Stale sites lose rankings and credibility slowly enough that nobody notices until the lead count drops.
Test 3: Does It Hold Up on a Phone?
Not “does it technically load” — does it work. Tap your own navigation. Read your own hero text at arm’s length. Fill in your own form with a thumb.
If the mobile experience is a shrunk version of the desktop one rather than a designed one, you are usually looking at a theme-level problem. That is redesign territory.
Test 4: Is the Platform Still Supported and Secure?
Check what your site runs on and whether that version still receives updates. An abandoned theme, a page builder no longer maintained, or a custom build whose developer has moved on are all structural risks. Security patching is not optional, and you cannot patch what nobody maintains.
Test 5: Is Performance a Theme Problem or a Content Problem?
Oversized images, too many plugins and unoptimised media are content problems. You fix those in a refresh. A theme that loads enormous scripts on every page regardless of what the page contains is a structural problem, and you fix that by replacing the theme.
Run one page through PageSpeed Insights, then run your simplest page. If even a near-empty page scores badly on mobile, the foundation is the issue.
Side by Side
| Refresh | Redesign | |
|---|---|---|
| Changes | Copy, images, CTAs, small fixes | Structure, navigation, templates, platform |
| Keeps URLs | Yes | Needs a migration plan |
| Typical timeline | Weeks | Longer, content-dependent |
| Search risk | Low | Real, manageable with redirects |
| Right when | Structure is sound, message is stale | Page set, platform or theme no longer fits |
| Wrong when | Platform is unsupported | You only needed better copy |
What a Refresh Should Include
If the tests point to a refresh, do these in order and you will get most of the available gain:
- Rewrite the homepage above the fold. Who you help, what you do, where you do it, and one action. Most homepages fail this in the first screen.
- Give every service its own page. Problem, approach, inclusions, who it suits, price or range, and the same single call to action.
- Replace stock imagery with your own. Photographs of your work, premises and team outperform generic stock on every page that asks for a decision.
- Fix the contact path. Fewer fields, visible phone number, working notifications, a real thank-you page.
- Compress and resize every image. This alone often moves mobile load time more than anything else on the list.
- Add the answers you give on the phone. Pricing questions, timelines, service areas, what happens first. Write them as plain FAQ content on the relevant page.
What a Redesign Should Include Before Any Design Happens
The mistake in most redesigns is starting with how it looks. Start with these instead:
- A page inventory. Every existing URL, its traffic, and a decision: keep, merge, rewrite, or retire.
- A sitemap for the new site built around services and buyer questions rather than internal departments.
- A redirect map. Every retired or moved URL points to its closest live equivalent. Skipping this is the single most common way a redesign loses traffic.
- Content before layout. Write the pages, then design to the content. Designing first produces beautiful boxes nobody has words for.
- Tracking parity. Analytics, form events and search console reconnected and verified on launch day, not a month later.
- A maintenance plan. Who updates this, how often, and with what access.
Protecting What You Already Rank For
This is the part worth being careful about. If any page brings you traffic or inquiries today, treat it as an asset.
Before anything changes, export your top pages by traffic and your top queries. Keep the URLs identical where you can. Where you cannot, redirect them one to one rather than dumping everything to the homepage. Keep the headings and topic coverage of pages that already perform — improving a working page is not the same as replacing it.
After launch, check search console weekly for a month. A short dip while pages are recrawled is normal. A sustained drop means something in the redirect map is wrong and is worth fixing immediately rather than waiting it out.
A Simple Way to Choose
If you scored zero to two on the five tests, refresh. Spend the budget on copy, photography and the contact path, and keep your URLs.
If you scored three or more, redesign — but do the inventory, sitemap and redirect map before anyone opens a design tool.
If you scored three or more and cannot fund a full rebuild yet, stage it. Rebuild the homepage and your two highest-value service pages properly on the current platform, measure what happens, and let that result fund the rest.
The website redesign vs refresh question is answerable in an afternoon with the five tests above. If you want the page inventory and structural read done for you before you commit a budget either way, start with the Free Website Audit page.