WordPress Website Redesign: When to Redesign and How to Do It Without Losing SEO
A redesign is one of the bigger projects an agency can sell, and one of the easier ones to get wrong. When it goes well, the client ends up with a site that’s faster, clearer and better at turning visitors into enquiries. When it goes badly, years of search rankings disappear the week after launch.
So the first question is whether the site needs a redesign at all. The second is how to do one without losing what already works.
When a site needs a redesign
Look at it next to the client’s competitors and their current brand. Does it look like it belongs to another decade? Is it slow, with a theme or page builder that makes speed hard to fix? Does the client avoid editing it and call you for every change?
Other signs are less visual. Traffic is fine but leads or sales aren’t. The business has new services, a new audience or a new pitch that the site doesn’t reflect. Or the foundation is shaky: abandoned plugins, a theme edited directly for years, no version control.
Redesign or fix?
One of those signs on its own rarely calls for a full redesign. If the structure and design still hold up, targeted work may be enough: a speed optimization project, better calls to action, a plugin cleanup.
When several signs show up together, or when the foundation itself is the problem, a redesign starts to make sense. A website audit is the honest way to decide.
Step 1: find out what already works
Before anyone opens Figma, pull the numbers. Which pages get the most traffic, conversions and backlinks? Which search queries bring people in? Which paths through the site end in an enquiry or a sale? And which content does the client want to keep, merge or drop?
Whatever ranks and converts today has to make it through the redesign.
Step 2: plan the structure
Write the new sitemap and content model. Decide what stays, what merges and what goes. Note every URL that changes as you go. That list becomes your redirect map.
Step 3: design for the goals
Design around what you learned in step 1: clear messages, obvious calls to action, simple navigation. Build the design from reusable sections so the site can grow later. Our guide to the designer–developer handoff covers preparing designs for WordPress.
Step 4: rebuild the foundation
A redesign is the natural moment to swap a heavy multipurpose theme for a lightweight custom theme with editable blocks. Build it on staging and leave the live site alone until launch.
Step 5: protect search traffic
This is the step where most redesigns lose traffic. Keep URLs the same wherever you can, and set up a 301 redirect for every one that changes. Carry over titles, meta descriptions and structured data. Don’t cut the content that makes a page rank just because it doesn’t fit the new layout. Update internal links and the XML sitemap. And on launch day, check that the new site isn’t still blocking search engines, because staging sites usually are.
Step 6: test
Run a full QA pass on staging: design, responsive layouts, forms, integrations, speed and redirects. Our WordPress QA checklist has the details.
Step 7: launch and watch
Launch at a quiet time with a fresh backup. For the following weeks, keep an eye on Search Console for 404s and crawl errors, compare traffic and conversions with the old site, and fix what comes up quickly.
Step 8: keep going
Launch day isn’t the end of the project. Offer ongoing work through a care plan or a development retainer, so the site keeps improving instead of slowly ageing again.
Building redesigns with a partner
If your team does the strategy and design and wants someone else to do the build, that’s what we do: we build the redesigned site from Figma, keep the SEO intact through the switch and never talk to your client. See Figma to WordPress development, or tell us about the redesign.
