WordPress website redesign: modernise your site, keep your content

A WordPress website redesign can give you a modern site without touching your content, because WordPress keeps your pages, posts and images in a database that is separate from the design. The safe way to do it is to build the new design on a private copy of the site, keep every web address the same where you can, redirect the ones that change, and switch over only after the copy has been tested. Content and rankings are lost when one of those steps is skipped, not because redesigns are risky by nature.

I'm Mohit, a freelance WordPress and Next.js developer in Gurugram, India, working with clients in India, the UK and the US. This guide is for the business owner who has a WordPress site that looks dated and is nervous about breaking what already works. It covers the how. If you want the numbers, I've written separate cost guides for the UK, the US and India.

What does a WordPress website redesign actually change?

A WordPress website redesign changes the layer that controls how the site looks and is laid out: the theme, the page templates, the header, footer, fonts and colours. Your words, images, blog posts, products and users sit underneath in the database, and a properly run redesign leaves them where they are.

It helps to picture WordPress as two parts. One part is the content store (the database plus the uploads folder with your images). The other part is the theme, which is the set of files that decides how that content is displayed. WordPress runs 39.2% of all websites, and this split between content and design is one reason it has lasted: you can change the look many times over the life of one site.

So why do people lose things? Because over the years, bits of content and settings get stored inside the theme or inside a page builder instead of in plain WordPress. A page builder is a plugin such as Elementor or Bricks that lets you design pages by dragging blocks around. When the theme or builder changes, whatever lived inside it has to be carried over by hand.

WPBeginner has a clear list of what happens when you switch your WordPress theme. I've put its main points in a table, with what I do about each one.

A shortcode is a small tag in square brackets that a theme or plugin turns into a button, a gallery or a form. A custom post type is a content type beyond pages and posts, such as "Projects", "Team members" or "Events". Both are common places for content to go missing, and both are easy to keep if someone looks for them before the switch.

Do you need a refresh, a redesign or a rebuild?

Most business owners who ask for a redesign need one of three different jobs, and picking the smallest one that solves the problem saves money and risk. A refresh updates the look of the site you have. A redesign changes structure and layout as well. A rebuild starts again on a new theme, builder or platform.

Prices follow the same order. WPBeginner says a simple refresh using a new premium theme might only cost between $50 and $200, and that hiring a freelancer or agency for a custom design runs from several hundred to many thousands of dollars. One agency guide puts a professional WordPress redesign anywhere from $3,000 to $100,000 and beyond, depending on size and custom work. That spread is the reason to be exact about which job you're buying.

You don't always have to redo everything. For Warren House, a hotel and wedding venue in Kingston, the job I did was the homepage: a new one built in Elementor Pro, with a video at the top, the rooms shown first and Google reviews on the page. The homepage is where most first impressions happen, so that is where the work went. If your inner pages are fine and the front door is the problem, a one-page job like that is a fair place to start.

My rule of thumb: if you can still edit the site easily and it loads quickly, refresh or redesign it. If every small change breaks something, or the site is slow no matter what you do, a rebuild is the honest answer, and it's better to hear that before paying for a new coat of paint on a weak wall.

How do you redesign a WordPress website without losing content?

You redesign a WordPress website without losing content by never working on the live site: take a full backup, build the new design on a private copy called a staging site, bring across anything that changed on the live site in the meantime, then switch. The content losses described in the guides I link below come from skipping one of those four.

A staging site is a private duplicate of your website where changes can be made without visitors seeing them. Many hosts create one with a button, and plugins can do it too. Hostinger's guide describes it as a private duplicate where you can work without affecting what visitors see, and it warns that publishing the staging copy replaces the live site's files and database. That second point is the one to remember.

Here is the order I'd follow.

1. 1

   List what you have

   Export every page, post, product, form and file download into a spreadsheet. This content list is what you check the new site against.

2. 2

   Back up the live site

   Take a full backup of files and database, download it, and confirm it can be restored. Keep it until well after launch.

3. 3

   Create a staging copy

   Clone the live site to a private address that is password protected and hidden from search engines.

4. 4

   Build the new design on the copy

   Change the theme, templates and layouts there. The live site keeps running as normal.

5. 5

   Agree a content freeze

   Decide how new blog posts, edits, orders and form entries on the live site will be carried over before the switch.

6. 6

   Test, then switch

   Check the copy against your content list, take one more live backup, publish, and test again on the live address.

Why is the content freeze the step people miss?

Because the live site keeps changing while the redesign is being built. If the build takes six weeks and your team publishes four blog posts and edits the pricing page during that time, those changes exist only on the live site. Push the staging copy over the top and they're gone.

Speckyboy calls this out in its list of redesign pitfalls: when the work happens on a separate WordPress installation, there may be a discrepancy with the content on the production site, and the danger is losing new or recently edited content. "Production" is developer talk for your live site.

There are three plain ways to handle it:

• Freeze. Nobody edits the live site for the last week or so. Simple, and fine for a brochure site.
• Double entry. Anything published on the live site during the build is also added to staging. Keep a shared list so nothing is forgotten.
• Design only. The developer moves only the theme, templates and settings to the live site and leaves the live database alone. This takes more skill, and it's the right method for busy sites.

Ask your developer which one they plan to use. If they haven't thought about it, that tells you something.

What should be on your content list?

Everything a visitor or Google can reach. Pages and posts are the obvious ones. The items that get forgotten are PDFs and brochures linked from old pages, thank-you pages after a form, landing pages built for an old ad campaign, image alt text (the short description of an image that screen readers and Google read), and the form notification emails that tell you a lead has come in.

For a small site this list is quick to make. It's dull work, and it's the cheapest insurance in the whole project.

What gets lost in a WordPress redesign if nobody checks?

The things that get lost are almost never the pages themselves. They are the settings and small pieces around the pages: tracking, forms, page titles for Google, redirects set up years ago, and content locked inside the old page builder.

Here's my checklist of the usual suspects.

• Analytics and ad tracking. If your Google Analytics or Meta pixel code was pasted into the old theme's settings, it goes when the theme goes. You find out a month later when the reports are empty.
• Forms and where they send leads. A new contact form may look identical and send its emails nowhere. Test every form and check it reaches the inbox, the CRM or the Google Sheet it used to.
• SEO titles and descriptions. These usually live in an SEO plugin such as Yoast or Rank Math, so they survive a theme change. They don't survive if pages are recreated from scratch instead of being restyled.
• Old redirects. If the site has been redesigned before, there may be redirects from that time in a plugin or a server file. Carry them over.
• Page builder content. Pages built in one builder don't open in another. Moving from WPBakery or Divi to Elementor or Bricks means each page layout is rebuilt, with the text and images copied across.
• Plugins nobody remembers. One agency guide (an estimate, not a study) says the average working WordPress site runs 15 to 40 active plugins. Some do quiet jobs such as sending order emails or creating the sitemap. Remove one carelessly and a feature vanishes.
• Schema markup. This is hidden code that tells Google what a page is (a business, a product, a set of FAQs). If the old theme added it, the new one may not.

A redesign is also a good time to clear out. Unused plugins, three old sliders, a theme from 2017 that is still installed: all of it can go. Do the clearing on staging, test, and only then repeat it on live.

How do you do a WordPress redesign without losing SEO?

A WordPress redesign without losing SEO comes down to one rule and a few checks: keep every URL the same unless there is a strong reason to change it, and where a URL does change, send the old address to the new one with a permanent redirect. A redesign that keeps its addresses, titles and text gives Google very little to re-learn.

A URL is the web address of a page. A redirect is an instruction that sends anyone who asks for the old address to the new one. A 301 is the permanent kind.

Staying on WordPress gives you an advantage here. Your permalinks (the address pattern WordPress uses) don't change with the theme, so in a refresh or a redesign most URLs stay exactly as they are. The danger comes when someone tidies up: /our-services/ becomes /services/, the blog moves from /news/ to /blog/, two thin pages are merged. Each of those is fine, as long as it is written down and redirected.

Google's own guidance for moving URLs is worth knowing, because it settles several arguments:

• Permanent redirects don't cost you ranking strength. Google says 301 and other permanent redirects don't cause a loss in PageRank.
• Use the permanent kind. With a permanent redirect Google shows the new redirect target in search results; with a temporary one it keeps showing the old page.
• Keep redirects in place for as long as possible, and generally at least a year.
• Don't send lots of old pages to the homepage. Each old URL should go to the page that replaced it.
• Expect some movement. Google says to expect temporary fluctuation in rankings during a move, and that for a medium-sized site it can take a few weeks or more for the new URLs to show.

What is a redirect map and who makes it?

A redirect map is a spreadsheet with two columns: every old URL on the left, and where it should go on the right. Your developer or SEO person builds it before launch, from your sitemap, Google Search Console and analytics, so that pages with traffic and links from other websites are never left pointing at nothing.

If no URLs change, the map is short and the job is to confirm that. If the structure changes, the map is the most valuable document in the project. Ask to see it.

What else protects rankings during a WordPress redesign?

Beyond URLs, keep the things Google reads on each page:

• Page titles and meta descriptions. Export them before the work starts and compare after.
• Headings and body text. A redesign that cuts a 900-word service page down to three lines and a photo has removed what the page ranked for. Shorten with care, and keep the parts that answer questions.
• Internal links. Links between your own pages, in menus, footers and text. A new, shorter menu can leave important pages with no links pointing to them.
• Image alt text and file names.
• Speed. A heavier design loads slower, and that can cost you visitors and rankings. Google's targets, called Core Web Vitals, are a main-content load (LCP) within 2.5 seconds, a response to taps (INP) of 200 milliseconds or less, and a layout shift score (CLS) of 0.1 or less. Test the staging site against these before launch. My free Page Speed Fix Planner turns a PageSpeed report into a plain to-do list.

What is the one setting that wipes a site from Google?

It's a tick box. In WordPress, under Settings then Reading, there is an option called "Discourage search engines from indexing this site". It's correct to tick it on a staging site. WordPress's documentation explains that it adds a noindex instruction to every page, which asks search engines to ignore the site. If the staging copy is pushed live with the box still ticked, your whole site asks Google to drop it.

It takes five seconds to check and it's the first thing I look at after any launch.

If the worst has already happened, I've written a separate guide on what to do when traffic drops after a redesign.

What if your WordPress site is a WooCommerce store or takes bookings?

A store or booking site needs a different launch method, because new orders, customers and bookings arrive on the live site every day while the redesign is being built. A full push from staging would replace the live database and wipe out everything that came in after the copy was made.

WooCommerce is the plugin that turns WordPress into an online shop. Its orders and customers sit in the same database as your pages, which is why a simple "copy staging over live" is dangerous for shops. Kinsta, a WordPress host, says so in its own documentation: its push tool can't separate new orders from old ones, so it suggests pushing only files, pushing selected database tables while leaving out the WooCommerce ones, or copying the live database to staging first.

Business Bloomer, a WooCommerce specialist site, lists four ways to redesign a store without losing data: repeating the changes by hand on the live site during a short maintenance window, selective pushes from a host that supports them, two-way sync tools, and custom scripts. It calls the manual route the one often considered the safest, though it takes the most time.

For most small shops I'd combine two of them. The design work (theme files and templates) moves across as files. The few database changes are repeated by hand on the live site at a quiet hour, with a fresh backup taken minutes before. Then a real test order goes through, with a real card, and is refunded.

The same thinking applies to membership sites, course sites, sites with user accounts and anything that takes bookings or donations. If people create data on your site, tell your developer on day one.

Should you keep your page builder or switch during a redesign?

Keep your page builder if it's a current one and your team is comfortable with it. Switch only if the builder is the cause of the problems, because switching turns a redesign into a rebuild: every page layout has to be made again.

There are three common situations.

You're on Elementor, Bricks or the block editor and it works. Redesign inside it. New templates, new global colours and fonts, and tidied-up pages will get you a modern site with the least risk. Your editors keep the tool they know.

You're on an old theme with its own builder, or on WPBakery or an early Divi build. These sites often carry years of leftover shortcodes and are slow to edit. A rebuild on a current builder is usually worth it, but budget for it as a rebuild.

You want better speed above all. A lighter builder helps. I've compared the three I use most in Bricks vs Elementor vs Oxygen. Speed can also be improved a lot without switching, so don't accept "you must change builder" without a reason tied to your site.

One thing I'd push back on: redesigning and changing platform at the same time when nothing forces you to. Google's advice for site moves is to change one thing at a time where you can. A new design, new URLs, a new host and a new platform in one weekend means that if traffic drops, nobody can say which change caused it.

How long does a WordPress redesign take, and what does it cost?

A theme-level refresh takes days, and a full redesign takes weeks or months, depending mostly on how many page layouts change and how quickly decisions and content come back. WPBeginner puts it the same way: a simple theme swap takes a few days, while a full overhaul can take weeks or months.

In my experience the build is seldom the slow part. Waiting is. Waiting for new photos, for the director to approve the homepage, for someone to rewrite the About page. If you want a redesign to finish on time, name one person on your side who can say yes.

What moves the cost:

• Number of unique layouts, not number of pages. Fifty blog posts share one template. Ten service pages that each look different are ten designs.
• New design or existing design. Arriving with a finished Figma design (Figma is the tool designers use to draw websites) costs less than asking for design and build together.
• Builder change. Staying on your builder is cheaper than moving.
• Shop, bookings, memberships. Anything with live data adds care at launch.
• How much SEO care is included. A redirect map, a before-and-after crawl and post-launch checks take real hours. They should appear in the quote.

For actual price ranges with sources, use the cost guides linked at the top of this post. There is one each for the UK, the US and India.

What should you check on launch day and in the weeks after?

On launch day, check that the site can be found, that it can be used and that it is being measured. Then watch Google Search Console and your enquiries for about a month before calling the project finished.

Launch day, in this order:

1. The "discourage search engines" box is unticked.
2. A fresh backup of the old live site exists and is stored somewhere safe.
3. Every URL on your content list loads, or redirects to the right page. A crawler tool does this in minutes.
4. Every form sends, and the email or CRM entry arrives.
5. Analytics and ad tracking record a test visit.
6. The site works on a real phone, not only in a resized browser window.
7. Checkout, booking or payment works with a real transaction.
8. The sitemap (the list of pages you hand to Google) is updated and resubmitted in Search Console.
9. The 404 "page not found" page exists and offers a way back.

The weeks after:

• Look at Search Console's page indexing report every few days for new "not found" errors, and add redirects for any real pages you missed.
• Compare like with like. Hostinger's guide suggests comparing the first 28 days after the redesign with a similar 28-day period before launch, and notes that rankings can take longer than that to settle.
• Watch enquiries and sales, not only traffic. A redesign that keeps traffic flat and doubles enquiries has done its job.
• Keep the old backup and the staging copy for at least a month.

Don't judge the redesign on day three. A small dip in the first couple of weeks is common while Google re-reads the site. A steep drop that keeps going is different, and it nearly always traces back to missing redirects, the noindex box or removed content.

What should you ask website revamp services before you hire one?

Ask website revamp services how they protect your content and rankings, and judge them on how specific the answer is. Any developer or agency can show attractive screenshots. Fewer can explain their launch method in plain words.

Questions worth asking:

• Will you build on a staging copy, and who hosts it?
• Are you restyling my existing pages or creating new ones?
• Which URLs will change, and can I see the redirect map before launch?
• How will content added to the live site during the build be carried over?
• What happens to my SEO titles, descriptions and tracking codes?
• Who tests the forms and checkout, and how?
• What is the rollback plan if something goes wrong on launch day?
• What do you check in the weeks after launch, and is that in the price?
• Will I be able to edit the new pages myself, and will you show me how?
• Who owns the theme, the licences and the logins when we finish?

Red flags:

• "We'll start with a fresh WordPress install and copy the content over" with no mention of URLs.
• No staging site: "we'll do it at night on the live site".
• A quote with no line for testing, redirects or launch.
• A promise that rankings won't move at all. Nobody controls Google.
• A new theme chosen before anyone has looked at your current content.
• Reluctance to hand over admin access or backups.

A freelancer, an agency and a "website revamp" package from a hosting company can all do this well or badly. The method matters more than the size of the team.

How can I help with your WordPress website redesign?

I redesign and rebuild WordPress sites on Bricks Builder, Elementor Pro, Oxygen and custom themes, working from a Figma design or with my design partners if you need one drawn first. The details are on my WordPress websites service page.

What I'd actually do on your project is what this guide describes. I'd list your content before touching anything. I'd build on a staging copy. I'd keep your URLs unless we agree a reason to change one, and write the redirect map when we do. I handle the technical SEO side myself (redirects, sitemaps, schema, Core Web Vitals and Search Console), so nothing falls into the gap between a designer and an SEO person. I also move sites between hosts, which matters if the redesign is the moment you leave slow hosting.

Some of my past work has been exactly this kind of job: a restaurant website revamp with a new Elementor homepage and templates from Figma, a company site moved onto Elementor Pro, and an agency site rebuilt in WordPress from another platform. I've also worked as the WordPress developer behind a London agency's client sites, so I'm used to fitting into someone else's design and deadline.

Where I'm not the right fit: if you need a large in-house team on call during your office hours in another time zone, or a full rebrand with photography and copywriting under one roof, an agency will suit you better. I'm one senior developer in Gurugram with a small trusted team for design, and you deal with me directly.

What should you do next?

Start with the list. Open a spreadsheet, export your pages and posts, and mark the ten pages that bring you the most visitors or enquiries (Search Console or Google Analytics will tell you). Then write one sentence on what is wrong with the current site: looks dated, hard to edit, slow, or not bringing leads. That sentence decides whether you need a refresh, a redesign or a rebuild.

If you'd like a second opinion, send me your site address and that one sentence. I'll look at how the site is built, tell you which of the three jobs I think it needs and what I'd protect first, and you can decide from there.