Redesigning an old WordPress site isn’t “just a new theme”: my process from audit to launch

Many business owners come with a simple request: “we just need a redesign to make it look nicer.” In reality, “just applying a new theme” is the fastest way to break SEO, distort your content, and increase maintenance costs.

When I redesign or fully rebuild a WordPress site, I look beyond the visual layer into the technical health, structure, content, and current traffic. My goal is not only to refresh the look, but to make the site faster, more stable, and easier to maintain – without crashing your organic traffic after launch.

In this article I’ll show how I distinguish a light facelift from a full rebuild, what I analyse before we start, and which risks I plan for so that, after launch, you get a predictable result instead of unwanted surprises.

Facelift vs full rebuild

When a light facelift is enough

A facelift means we keep the existing site structure, content, and CMS in place, while focusing on the visual layer and some UX improvements.

Signs that a facelift is the right choice:

• Your current theme is reasonably stable, but looks dated: typography, colours, cards, forms.

• The site structure, URLs, and main templates work for you – it’s the interface that needs attention, not the logic.

• The site already has organic traffic, and radically changing the architecture would be risky for SEO.

• You have limited budget and tight deadlines, and the main goal is to improve look and conversion without touching the foundation.

Typical facelift work:

• Unifying typography, colour palette, buttons, and blocks so the site feels consistent.

• Improving readability, spacing, mobile responsiveness, and contact forms.

• Carefully adjusting layouts without changing URLs or heading hierarchy, to avoid harming SEO.

When you really need a full rebuild

A rebuild is not “cosmetics”, it’s rebuilding the site almost from scratch: theme, structure, and sometimes even the wider CMS stack.

I recommend a rebuild when:

• The site is slow, unstable, and full of plugin conflicts and recurring errors.

• The theme is overloaded with legacy customisations, and it’s cheaper and safer to design a new structure than patch the old one.

• Your business goals have changed: you need new logic, content types, integrations, languages, or better scalability.

• The current architecture blocks growth: changes are hard or expensive, and the admin area is painful for your team.

In rebuild projects I typically:

• Design a new structure (navigation, taxonomies, custom post types, fields) with a 2–3‑year horizon in mind.

• Build a lean theme or child theme, often custom, avoiding heavy page builders where possible.

• Plan content, SEO‑metadata, and redirect migration to preserve or improve existing traffic.

What I analyse before we start

Before touching design or code, I run an audit of your current site to decide whether we’re doing a facelift, a rebuild, or a hybrid.

1. Structure and navigation

• Sitemap: which page types exist, how they connect, and whether there are duplicates or “dead branches”.

• Menus and internal links: how easy it is to reach key sections, and whether important content is buried.

• URL structure and heading hierarchy h1–h3: whether they match how people actually search for your services.

2. Content and conversions

• Content quality and relevance: whether texts match your current offer and where outdated or duplicated pages appear.

• Pages that drive traffic and leads: what already works and should be touched very carefully, if at all.

• User journey and UX: where people most often drop off, and whether forms, CTAs, and FAQs are clear enough.

3. Technical health and performance

• Load speed (PageSpeed, Core Web Vitals) on mobile and desktop.

• Core technical aspects: valid HTML, functioning sitemap, robots.txt, 404 page, redirects, HTTPS.

• Hosting and caching: whether the site can handle expected traffic and how CDN and image optimisation are set up.

4. Traffic and SEO

• Which pages attract organic traffic and which queries bring people to the site.

• Current metadata: titles, descriptions, schema, canonicals, pagination.

• Risk areas: pages without metadata, duplicate URLs, and technical indexing issues.

Typical risks – and how I plan for them

SEO: keeping what already works

The main risk of any redesign is losing rankings and traffic, especially when structure, URLs, or HTML templates change carelessly.

My approach:

• Lock in current URLs and high‑traffic pages and plan minimal, controlled changes for them.

• Keep key SEO elements (title, description, h1, internal links) intact or strengthen them, instead of starting from zero.

• If we must change URL structure, prepare and test a full 301 redirect map before launch.

Content: avoiding gaps, duplicates, and lost meaning

In rebuilds, it’s tempting to “throw away all old content and rewrite everything”. That only works if we don’t simultaneously remove pages that already rank and convert.

So I:

• Group content into “works well”, “needs an update”, and “can be merged or removed”.

• Update texts based on search demand and real user questions, not just style preferences.

• Plan space for future blocks – FAQs, case studies, articles – so the site can grow without chaotic patchwork.

Plugin zoo and technical debt

Older WordPress sites often run on dozens of plugins, many of them outdated or overlapping in functionality. This affects security, speed, and stability.

I handle this by:

• Auditing every plugin: what it does, whether it’s still needed, and if we can replace it with a lighter or native solution.

• Removing duplicates: multiple SEO plugins, form plugins, or caching plugins is a classic scenario that needs cleanup.

• Consolidating critical features (forms, SEO, multilingual setup) into robust, well‑maintained tools so the site can be safely updated.

Short anonymised case

A small service‑based agency came to me with an old WordPress site built on a purchased theme with a heavy builder and more than 40 active plugins. The site looked outdated, and every change in the builder risked breaking another part of the site.

Audit highlights:

• Around 70% of contact forms failed on mobile.

• Most traffic landed on 4–5 blog posts and 3 service pages, which were buried in the navigation.

• Several plugins hadn’t been updated for over 2 years, and some duplicated theme and builder functionality.

We decided that a simple facelift would be a band‑aid solution; a controlled rebuild with careful SEO and content migration was the right path.

Process:

• Captured current URLs, key metadata, and high‑traffic pages, and drafted a redirect map “if something changes”.

• Designed a clearer structure: distinct “Services”, “Case studies”, and “Blog” sections, simplified menus and internal linking.

• Built a lean custom theme with a defined set of reusable blocks: hero, benefits, case studies, FAQ, contact forms.

• Cleaned up plugins: reduced the total count by roughly half, moved some features into the theme or one universal plugin.

• Ran a pre‑launch checklist: performance, mobile UX, forms, redirects, analytics, SEO tags.

Outcome:

After launch, the site was not only visually modern, but also more stable, faster, and easier to maintain. Organic traffic was preserved, and clearer structure plus functioning forms led to a gradual increase in enquiries.

For the client, this was not “just a new look”, but a reliable tool they could grow – adding services, case studies, and content without fear of breaking the system.