Changing Your WordPress Theme: What Breaks

The new theme looked brilliant in the demo. Clean photography, a bold booking button, a layout that made the old site look like 2015. Twenty minutes after clicking Activate, the menu had vanished, the testimonials page was a wall of square-bracket code, and the sidebar with the opening hours was simply gone.

That scene is a composite, not one customer's story. Consider it a typical case: a driving instructor in Cavan takes on a second instructor, decides the website needs a fresh look to match, buys a premium theme in an online sale and activates it on the production site one evening. Nothing in the content was deleted. Every page, every post, every photo was still in the database. But to a pupil landing on the homepage the next morning, the site was broken, and the button that used to say Book a Lesson led nowhere at all.

I have watched variations of this play out for two decades. A theme change is the single most common way a business owner breaks their own website without touching a line of code. It is also one of the most avoidable. So let me walk through what actually happened on that Cavan site, why, and the order of operations that stops it happening on yours.

Why a Theme Change Feels Like a Paint Job but Behaves Like a Rewire

WordPress itself describes a theme as something that "modifies the way the site is displayed, without modifying the underlying software." That is the theory, and for your actual words and pictures it holds. Your pages and posts live in the database, not in the theme, and they come with you.

The trouble is everything else. Menus, sidebars, header settings, logo placement, colour choices and a surprising amount of functionality are tied to the specific theme that was active when you set them up. Switch theme and you are not repainting the house. You are moving into a different house and carrying your furniture through the door, and some of it was built into the walls of the old one.

This matters more than it used to, because the theme market has grown well beyond the free directory. The official WordPress.org theme directory currently lists close to 8,700 themes, and every one of those has passed a review against published rules. Premium marketplace themes are a different story, as our driving instructor found out.

What Survives a Theme Switch and What Does Not

Before the story continues, here is the inventory. Every row below gets its own section further down.

Part of your site	After switching theme	What you do about it
Pages, posts and media	Survive intact	Verify layout on key pages
Navigation menus	Survive, but unassigned	Reassign to the new theme's locations
Widgets (sidebar, footer)	Usually moved to Inactive Widgets	Drag back into new areas, or rebuild as blocks
Customiser settings (logo, colours, header)	Stay behind with the old theme	Re-enter in the new theme
Theme-bundled features (shortcodes, portfolios, testimonials, SEO fields)	Stop working or vanish	Move to a plugin before switching

Your content stays in the database. The theme is the structure built around it, and parts of your site are attached to that structure.

Pages, posts and media: the part that is safe

Start with the good news. On the Cavan site, every lesson description, every price, every photo of the dual-control car was still there after the switch. WordPress stores them separately from the theme, which is the whole point of the design.

Safe does not mean identical. A page built with a theme's own layout options can look quite different under a new theme: columns collapse, image sizes change, a full-width hero becomes a narrow box. The content is there. Whether it still looks like a business worth booking is a separate question, and one you can only answer by verifying each key page in the new design.

Menus: present, but pointing nowhere

The vanished menu was the first thing pupils noticed. It had not been deleted. WordPress's own documentation on the Menus screen explains that a menu appears on the site only when it is assigned to one of the active theme's Theme Locations, under Menu Settings, Display location. The old theme called its main slot one thing. The new theme called it something else. So the menu sat, fully intact, in the dashboard, attached to a location that no longer existed.

The fix takes two minutes once you know it. Appearance, Menus, select the menu, tick the new theme's primary location, Save Menu. The consequence of not knowing it is a homepage with no way to reach the booking page, the prices or the contact details, which is how a visitor decides your business has closed.

Block themes complicate this slightly. WordPress's documentation on block themes says navigation is handled by blocks, and the Navigation block offers an "Import classic menus" option to convert an old menu. Your menu still exists. It just needs bringing across by hand.

Widgets: the sidebar that quietly emptied

The opening hours, a small map and a "Pass rate" badge all lived in a sidebar widget. After the switch they were gone from the page, though not from the site. WordPress keeps an Inactive Widgets area precisely so that widgets can be parked "and keep your settings" until you place them again. When the new theme's sidebars do not match the old theme's, that is where your widgets usually end up.

If the new theme is a block theme, there is no Widgets screen to drag them back into. WordPress's block theme documentation is blunt about it: "Instead of widgets, a block theme relies on blocks." The content of those widgets has to be rebuilt as blocks in the Site Editor. Not difficult. But it is work, and it is better done before customers see the gap than after.

Customiser settings: they stay with the old theme

The logo looked tiny. The header colour was a default grey. The tagline had reverted. None of that was a bug.

WordPress stores most design settings per theme. The developer reference for get_theme_mods() shows the mechanism: settings are saved under an option named after the active theme's folder. A new theme reads its own, empty, set of settings. The upside is that if you switch back, your old settings are waiting for you. The downside is that every logo upload, colour choice and header setting has to be entered again in the new theme. Also note that the Customiser is hidden entirely in block themes unless a plugin needs it, so the place you used to make these changes may simply not be there.

The Part That Actually Costs Money: Theme-Bundled Features

Everything above is an inconvenience. This section is where the real damage was done.

The premium theme the instructor originally used had come bundled with extras: a testimonials section, a pricing table and a few layout shortcodes, the little codes in square brackets that tell a theme to draw a box or a button. When that theme was deactivated, the code that understood those brackets went with it. WordPress does what it always does with a shortcode nobody recognises. It prints the raw text on the page. So pupils saw [testimonial id="4"] where the reviews should have been. And the testimonials themselves, stored as a custom post type registered by the old theme, disappeared from the dashboard menu entirely.

WordPress.org has a name for this. Its Theme Handbook lists, as required rules for any theme in the official directory, a set of "plugin territory" features that themes must not include, among them custom post types, custom blocks, shortcodes, SEO options, contact forms, analytics and social sharing buttons. The reasoning is exactly what happened in Cavan. If a theme owns your functionality, leaving the theme means losing the functionality.

Marketplace themes sold elsewhere are not bound by that rule, and many advertise the opposite as a selling point. Everything built in. One purchase. Early in my career I told more than one client that a bundled, everything-included theme was good value. It was, right up until they wanted to leave it, and then it was a hostage situation.

Two theme-bundled features deserve particular attention because they cost money when they disappear:

SEO fields. If page titles and meta descriptions were entered through the theme's own options rather than an SEO plugin, they can vanish on the switch. Google then writes its own snippets for your pages, and they are rarely the ones you would have chosen.
Page builders. W3Techs' current data shows Elementor alone on roughly three in ten WordPress sites. Content built in a page builder generally survives a theme change as long as the builder plugin stays active. Content built with a builder that shipped inside the theme does not.

How to Change Your Theme Without a Repeat of Cavan

None of this is an argument against changing theme. A dated design costs you enquiries, and owning a WordPress site means owning the right to redesign it whenever you like, without asking an agency's permission or paying an hourly rate for the privilege. WordPress runs roughly four in ten of all websites according to W3Techs precisely because it lets you do this. The point is to do it in the right order.

Take a backup first, and know how you would restore it

A theme change is a significant production change. Before anything else, take a fresh manual backup, not last night's. If you have not thought through how backups and restores fit together on your site, the complete guide to WordPress security and backups covers the fundamentals. A backup is what turns a disastrous theme switch into an annoying one.

Make the change in staging, not on the production site

WordPress's Themes screen offers a Live Preview button, and it is worth using to judge looks. It is not a substitute for a staging environment. A preview shows you the design. It does not let you reassign menus, rebuild widgets, re-enter settings and click every page as a customer would before anyone else sees it.

That is what a staging copy is for. We have written before about how a staging environment stops a bad change reaching paying customers, and a theme switch is the textbook case. Activate the new theme on the staging copy. Break it there. Fix it there.

Do the messy part of a redesign on a staging copy, then deploy the finished version.

Audit what the old theme was doing for you

Before activating anything, list every feature on the current site and ask where it lives. Testimonials, portfolio items, pricing tables, sliders, contact forms, SEO titles. Anything that turns out to belong to the theme needs moving to a plugin first, while the old theme is still active and can still show you the content.

Verify every page a customer actually uses

After the switch on staging, click through the site the way a customer would: homepage, services, prices, booking or contact page, on a phone as well as a laptop. Look specifically for raw square brackets, missing menus, empty sidebars and a logo that has gone back to text. Submit your own contact form and confirm the email arrives.

Deploy, then verify again on production

Only when staging looks right do you deploy. Then repeat the key checks on production, because the production site has today's real enquiries and orders in it and the staging copy does not.

What Staging Cannot Do for You

An honest limit is worth stating plainly. A staging environment is a copy taken at a moment in time. If enquiries, bookings or orders arrive on the production site while you spend two evenings perfecting the new design on staging, those do not exist in the staging copy. Pushing the entire staging database over the top of production would wipe them out. For a design change, the safer route is usually to treat staging as your rehearsal and then repeat the theme activation and settings on production, or to push files and design only, never a stale database.

There is also a scale question. If your website is a three-page brochure with no menu worth mentioning, no sidebar and no bundled features, you can switch theme on almost any host, staging or not, and fix the fallout in ten minutes. Cheap shared hosting without staging is genuinely sufficient for that. The case for doing it properly grows with how much your site actually does: bookings, a shop, a portfolio built up over years.

Where the Hosting Fits In

Strip the story back and the safe process needs four things from the platform underneath: a backup you can take on demand, a restore you can trust, a staging copy you can create without a developer, and someone to ring if it still goes sideways. Most budget hosts sell some of these as add-ons, and some do not offer staging at all, which is how owners end up activating new themes on production in the first place.

Web60 includes all four in the base price. One-click staging, automatic nightly backups plus manual on-demand backups, one-click restore, and pre-update and pre-restore safety snapshots taken automatically, all on Irish infrastructure built for exactly this kind of change, with an Irish-based support team answering the phone. It is full WordPress, so the entire theme ecosystem is open to you, and the €60 a year covers the lot. If you are building from scratch, the AI builder gives you a designed WordPress site in under a minute, and you are free to change the theme yourself whenever the business outgrows it.

Conclusion

A theme change does not delete your content. It disconnects things: menus from their locations, widgets from their sidebars, settings from the design, and theme-bundled features from the code that drew them. Every one of those is fixable, and most are fixable in minutes, provided you find them on a staging copy rather than hearing about them from a customer.

So audit what the old theme was doing, move anything it owned into a plugin, take a fresh backup, rehearse the switch in staging and verify every page your customers rely on. Then the new look goes live as a fresh look, not as a broken site.

Frequently Asked Questions

Will I lose my content if I change my WordPress theme?

No. Your pages, posts and media library are stored in the WordPress database, separately from the theme, so they survive a theme change. What can be lost or disconnected are things tied to the old theme: menu assignments, widget placements, design settings such as logo and colours, and any features the theme itself provided, such as shortcodes, testimonials or portfolio sections.

Why did my menu disappear after changing theme?

The menu still exists, but it is no longer assigned to a location in the new theme. In a classic theme, go to Appearance, then Menus, select your menu, tick the new theme's main display location and click Save Menu. In a block theme, edit the header in the Site Editor and use the Navigation block's Import classic menus option.

Where do my widgets go when I switch WordPress themes?

Widgets that do not fit the new theme's widget areas are usually moved to the Inactive Widgets section of Appearance, Widgets, with their settings kept, so you can drag them back into place. Block themes do not use widgets at all, so their content needs rebuilding as blocks in the Site Editor.

What are square-bracket codes showing on my pages after a theme change?

They are shortcodes that belonged to your old theme. When the theme is deactivated, WordPress no longer knows what they mean and prints them as plain text. The fix is to switch back on a staging copy, move that feature into a plugin that provides the same shortcode or an equivalent block, and then change theme again.

Can I preview a new WordPress theme before activating it?

Yes. The Themes screen in WordPress has a Live Preview button that shows how your site would look in the new theme. It is useful for judging the design, but it does not let you fully set up menus, widgets and settings, so for a business site the safer approach is to activate the new theme on a staging copy first.

Changing Your WordPress Theme: What Breaks, What Survives and How to Switch Safely