Redesigning an Outdated WordPress Website
A redesign that keeps what already works. URL mapping, content triage, and the checks that stop a rebuild costing you traffic.
This is an implementation example, not a client case study. It describes how this work is actually carried out — the method, the sequence and the reasoning. No client is named and no result is claimed, because inventing either would make it worthless as evidence.
Most redesign damage is self-inflicted. The new site looks better, launches, and traffic drops — because URLs changed without redirects, pages that were quietly ranking got 'consolidated', and nobody checked the before-and-after because analytics was reinstalled on launch day.
- Project type
- Redesign of an existing WordPress site
- Sector
- Retail and services
The challenge
The existing site is dated and hard to edit, but it is not worthless. Some pages have years of accumulated search visibility. A redesign that treats the old site as a blank slate throws that away, and the loss is invisible until the following month's enquiries do not arrive.
The objective
A site that is better in every respect the business cares about, while preserving every bit of search equity the old one had earned.
Approach
Audit before designing. Find out what the old site is actually doing well — which pages get traffic, which URLs have links pointing at them — and treat those as constraints on the redesign rather than as things to be tidied away.
Implementation
1. Establish the baseline
Before anything changes:
- Export every URL from the existing site
- Export Search Console performance by page, 12 months
- Record current Core Web Vitals from field data
- Note which pages have external links pointing at them
- Screenshot analytics so there is a genuine before
You cannot tell whether a redesign helped if you did not measure what preceded it.
2. Content triage
Every existing page gets one of four decisions:
| Decision | When |
|---|---|
| Keep as-is | Getting traffic, still accurate |
| Improve | Getting traffic, content is weak |
| Merge | Two pages competing for the same intent |
| Remove | No traffic, no links, no purpose |
Removing is fine. Removing something that was quietly bringing in enquiries is not, and the only way to tell the difference is the data from step one.
3. URL mapping
Every old URL maps to exactly one new URL, or stays where it is.
Keeping URLs is always better than redirecting them. Where a change is genuinely necessary, it is a single 301 — never a chain, never a redirect to the homepage, which Google treats as a soft 404.
4. Rebuild on a proper content model
The same sequence as a new build: content types, templates, then design against real content. The redesign is the opportunity to fix the structural problems that made the old site hard to extend.
5. Pre-launch verification
- Every mapped redirect tested, checking for chains
- Internal links updated to point at final URLs, not through redirects
- Schema carried across
- New site measured against the old site's performance baseline — a redesign that ships slower is a downgrade with a new logo
6. Launch and watch
- Submit the new sitemap; keep Search Console continuous
- Watch the Pages report daily for the first fortnight
- Watch for a spike in 404s, which means a mapping was missed
- Compare Core Web Vitals field data after four weeks, once it has accumulated
Technology
- WordPress
- Custom theme
- Screaming Frog
- Google Search Console
Decisions worth explaining
Keep existing URLs wherever possible
Every redirect is a small tax and a chance to lose something. A tidier URL structure is rarely worth the risk on pages that already rank.
Audit before design, not after
Design decisions made without knowing which pages matter will quietly remove the ones that do. The audit is what turns the redesign into a constrained problem rather than a blank page.
Keep analytics and Search Console continuous through launch
Reinstalling tracking on launch day destroys your own before-and-after, which is the only way to tell whether the redesign helped.
What it produces
A rebuilt site on a maintainable structure, with existing URLs preserved or mapped one-to-one, and a measured baseline to compare against. No traffic change is claimed — the point of this method is that traffic should not change downward, and whether it improves depends on work beyond the redesign itself.
What it teaches
- Most redesign traffic loss is caused by URL changes without redirects, not by the design.
- 'No traffic' is only a reason to delete a page if you have actually checked the data.
- A redirect to the homepage is treated as a soft 404. Map to the closest equivalent page or let it 404 honestly.
- If tracking is reinstalled at launch you lose the ability to prove anything either way.
Related services
Related guides
WordPress
WordPress Website Development: What Businesses Actually Need
The decisions that determine whether a WordPress site earns its keep are made in the first week, not the last. Here is what they are.
WordPress
WordPress Website Redesign: When Should You Rebuild?
Rebuilds are sold more often than they are needed. Here is how to tell which side of that line you are on.
SEO
Why Is My Website Not Ranking on Google?
Work through these in order. Most sites that are not ranking fail at step one or two, and never find out.
