How To Redesign A Wordpress Website

Don't have time to read this? Schedule a 30-minute call and we will walk you through exactly how this applies to your business. Book a call

Key Takeaways

• A WordPress redesign is not a theme swap. It is a structured rebuild that requires SEO baseline documentation, content migration planning, and pre-launch testing before anything goes live.
• The most common mistake is launching the new design directly on the live site. Always build on a staging environment.
• Plugins that power your current site's functionality must be audited before the redesign begins, many carry security vulnerabilities, performance costs, and compatibility risks.
• If your WordPress site is showing its age in performance, maintenance burden, or editor experience, this is also the right time to evaluate whether WordPress is still the right platform.

Redesigning a WordPress website is more complex than updating a theme. The existing content, URL structure, SEO equity, integrations, and plugin dependencies all carry forward into the new design, and each one needs a deliberate plan.

Here is the full process for doing it correctly.

Step 1: Audit Before You Touch Anything

Before redesigning a single page, document the current state of the site.

What to audit:

• URL inventory: Export every indexed URL from Google Search Console and run a crawl with Screaming Frog. This list becomes the input for your redirect map.
• SEO baseline: Export keyword rankings from Semrush or Ahrefs. Document which pages rank for which terms. These rankings must survive the redesign.
• Plugin audit: List every active plugin. For each one, confirm: Is it still maintained? Is there a security vulnerability in the current version? Is it actually in use, or left over from a previous team?
• Analytics baseline: Screenshot or export GA4 data for top landing pages, conversion rates, and bounce rates. This becomes the comparison benchmark post-launch.
• Content inventory: List all pages, blog posts, and custom post types. Mark each as keep, update, consolidate, or delete.

This audit prevents discovering problems after the new site is live.

Step 2: Define the New Site Architecture

Use the content inventory to build the new sitemap.

Questions to answer before wireframing:

• Which pages are being redesigned vs. migrated as-is?
• Are any pages being merged or removed?
• Are new pages being added to the sitemap?
• Are URL slugs changing? (If yes, every changed URL needs a redirect.)

The sitemap defines the redirect map. Build both at the same time in a Google Sheet: column A is the old URL, column B is the new URL. Start populating it now.

Step 3: Choose Your Build Approach

WordPress redesigns can be executed three ways. Each has trade-offs.

The platform migration question:

WordPress's maintenance burden is real. The average production WordPress site runs 15 to 40 active plugins. Each plugin is a dependency that requires updates, can conflict with other plugins, and represents a potential security vulnerability.

If the reason for the redesign includes "our site is slow," "we're constantly dealing with plugin issues," or "our editor is hard to use," the redesign is the right moment to evaluate alternatives. The WordPress vs. Webflow comparison covers when migration makes more sense than rebuilding on the same foundation.

Step 4: Set Up a Staging Environment

Never build the redesign on the live site.

Staging environment options for WordPress:

• WP Staging plugin: Clones the live site to a staging subdomain within the same hosting account
• Duplicator Pro: Creates a full site copy you can install on a development subdomain
• Local by Flywheel: Runs WordPress locally on your computer for development without a live server
• Your hosting provider's staging feature: WP Engine, Kinsta, SiteGround, and most managed WordPress hosts offer one-click staging environments

Set up the staging environment, install a maintenance mode plugin or password-protect the staging URL, then build the entire redesign there.

Do not touch the live site until the new design is ready to launch.

Step 5: Choose Your Theme or Build Custom

If staying on WordPress, the theme decision shapes everything downstream.

Page builder options:

• Elementor Pro: Largest user base, most plugin integrations, good for marketing teams managing their own content
• Bricks Builder: Better performance than Elementor, cleaner code output, growing rapidly among developers
• Kadence Blocks + FSE: Full site editing with the native block editor, no third-party page builder dependency
• Custom theme: Best performance and control, requires developer expertise, no drag-and-drop editing

For performance: Avoid themes with heavy pre-loaded demo content, dozens of bundled plugins, and global scripts that load on every page. A clean theme or a minimal starter theme with only what you need will perform better.

Step 6: Migrate Content

Content migration is where most WordPress redesigns create problems.

Approach options:

1. Manual migration: Copy and paste content into new templates. Slow but clean. Best for sites under 50 pages.
2. Plugin-assisted migration: For blog posts and custom post types, export/import via the WordPress built-in export or a plugin like WP All Import. Preserves metadata, categories, and custom fields.
3. Rewrite during migration: For sites with outdated content, the redesign is an opportunity to update copy, trim thin pages, and consolidate duplicate topics. Do this with a content plan, not ad hoc.

Content migration checklist:

• [ ] All page content entered on staging
• [ ] Blog posts migrated with correct categories, tags, and publish dates
• [ ] Images compressed and properly sized (use Smush or ShortPixel)
• [ ] Internal links updated to reflect new URL structure
• [ ] Author metadata preserved on blog posts

Step 7: Rebuild Integrations

Every integration on the existing site must be re-verified in staging.

Common WordPress integrations to rebuild:

• Contact forms (Gravity Forms, WPForms, Contact Form 7)
• CRM connection (HubSpot, Salesforce, ActiveCampaign via Zapier or native plugin)
• Chat tools (Intercom, Drift, HubSpot Chat)
• Ecommerce (WooCommerce, if applicable)
• Marketing automation (Mailchimp, ConvertKit, ActiveCampaign)
• Analytics and tracking (Google Analytics 4 via GTM, Meta Pixel)

Test every form submission on staging. Confirm that CRM data routes correctly. Verify that tracking events fire on the actions you need to measure.

Step 8: Pre-Launch SEO Checklist

This is the most critical step for protecting your organic traffic.

Pre-launch SEO tasks:

• [ ] Redirect map complete: every old URL mapped to new URL
• [ ] Redirects tested on staging: all old URLs resolve to correct new destinations
• [ ] Meta titles and descriptions reviewed for every page
• [ ] H1 present on every page, not duplicated
• [ ] XML sitemap generated and correct (Yoast, Rank Math, or All in One SEO)
• [ ] Robots.txt confirms staging domain is not being accidentally disallowed
• [ ] Canonical tags configured correctly on all pages
• [ ] No accidental noindex tags on public pages
• [ ] Image alt text present on key images
• [ ] Core Web Vitals tested on staging via PageSpeed Insights

For the complete redesign SEO process, the WordPress redesign cost breakdown covers how much SEO infrastructure work typically adds to a WordPress project budget.

Step 9: Test Before Launch

Run a complete pre-launch test on staging before touching DNS.

Testing checklist:

• [ ] All pages load correctly at expected URLs
• [ ] All forms submit and route correctly
• [ ] Navigation works on desktop, tablet, and mobile
• [ ] All integrations confirmed functioning
• [ ] 404 page is custom and includes a return-to-home link
• [ ] No console errors in Chrome DevTools
• [ ] Cross-browser test: Chrome, Safari, Firefox, Edge
• [ ] Core Web Vitals within acceptable range (LCP under 2.5s, CLS under 0.1)
• [ ] All redirects confirmed

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

Step 10: Launch and Monitor

When staging is fully approved, execute the launch.

Launch sequence:

1. Set the new site live (update DNS or push staging to production, depending on your setup)
2. Immediately test live redirects: spot-check 10 to 20 high-traffic old URLs
3. Submit updated sitemap to Google Search Console
4. Test all live forms
5. Confirm GA4 and GTM are firing on live domain
6. Monitor Search Console for crawl errors over the next 48 hours
7. Check Core Web Vitals in Search Console after one to two weeks of live traffic data

Ranking fluctuations in the first two to four weeks after a redesign are normal. A clean redirect map and proper SEO transfer minimize the drop and accelerate recovery.

Redesigning on WordPress is manageable with the right process. If the maintenance overhead of your current setup is part of the reason you are redesigning, this is the moment to consider whether the new site should still be WordPress.

LOW/CODE Agency is a leading AI product team for SMBs and startups. We have run this process on sites of all sizes, including migrations off WordPress to higher-performance platforms for clients who needed a cleaner, faster, more maintainable foundation.

Website projects start at $10,000+. Let's talk