Divi fix
Divi Shortcodes Showing After a Theme Change? What to Do
You activated a new theme and every page now reads like a ransom note of square brackets: et_pb_section, et_pb_row, et_pb_text. Nothing has been deleted. Your words are still there, wrapped in instructions only Divi can read, and the way out depends on whether you are leaving Divi for good.
What you are seeing
- Pages show [et_pb_section] and [et_pb_row] tags around the text
- Images, buttons and columns are gone, leaving one long block of words
- The header, footer and logo reverted to the new theme's defaults
- Search snippets in Google begin to show bracketed fragments
- Analytics and ad tracking numbers drop to zero the same day
Why it happens on Divi
Most common first.
- 1
The new theme has no idea what et_pb means
Divi 4 and earlier save a page as shortcodes wrapped around your text: a tag for each section, row, column and module. WordPress prints any shortcode it has no handler for. Switch themes and the handlers leave with Divi, so the instructions show up as content.
- 2
Half the content lives inside the tags
Paragraph text sits between the tags. Image addresses, button labels, link targets and blurb headings are stored as attributes inside them. Any tool that strips the brackets keeps the first group and throws the second away, which is why a stripped page comes out as one gray column of text.
- 3
The header and footer were Theme Builder templates
Headers, footers and post templates built in the Theme Builder are stored apart from your pages and rendered only by Divi. The new theme supplies its own defaults instead, so the logo, the menu layout and the footer all change at once.
- 4
Site-wide settings lived in Divi's Theme Options
The logo, the color palette, custom CSS and any code pasted into the Integration tab belong to Divi. That last one matters most. If your analytics or ad tracking snippet was added there, it stopped loading the moment the theme changed.
- 5
Forms and other working parts were Divi modules
A contact form built with Divi's Contact Form module is a shortcode like everything else. Without Divi it does not render and does not send. Divi's Projects post type disappears from the admin menu too, though the entries remain in the database.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Switch back to Divi before anything else
Go to Appearance, Themes and activate Divi again. The pages return as they were, because switching themes deleted nothing. Visitors and search engines stop seeing brackets, and you can plan the exit without an audience.
- 2
Decide whether you are leaving the theme or the builder
If you only wanted a different theme around your pages, Elegant Themes offers the Divi Builder as a standalone plugin that renders these layouts inside other themes. It keeps the pages working and keeps the dependency. If the goal is to be free of Divi, continue.
- 3
List everything Divi does besides page layouts
Check Divi, Theme Options, Integration for tracking code, and the custom CSS box under General. Count the Theme Builder templates, the saved items in Divi, Divi Library and every Contact Form module. Each one needs a new home before the switch.
- 4
Rebuild the pages that matter on a staging copy
Clone the site, activate the new theme there and rebuild the top pages in its editor: home, services, contact and whatever ranks. Copy text from the rendered page, not from the shortcode view. Keep every URL identical.
- 5
Bulk-strip only what is plain text
For a few hundred blog posts made of single text modules, removing the tags in bulk is reasonable. Try it on the staging database first and compare a dozen posts by eye. Never run it on pages with images, buttons or columns, since those live in attributes.
- 6
Switch for real, then verify
When staging is right, repeat the switch on the live site with a fresh backup. Search the content for et_pb to catch stragglers, submit a test through each form and confirm the analytics tag is firing. Watch Search Console for a few weeks.
Keep it from coming back
- Rehearse any theme change on a staging copy, never on the live site
- Search your content for et_pb before the switch so you know how many pages are involved
- Keep tracking code in a tag manager or a small plugin so it does not depend on the theme
- Once an exit is planned, write new posts in the block editor instead of in Divi
The permanent fix
A faster Next.js build, with a CMS made for your business
Leaving Divi means touching every page once, whichever direction you go. If the content has to be lifted out of shortcodes anyway, that is the cheapest moment to ask whether it should land in another WordPress theme or in a Next.js site with a custom CMS, where content is stored as plain structured fields and no later redesign has to unwrap it again. Much of the conversion work is shared; the destination is the real choice.
| On Divi today | On Next.js with a custom CMS | |
|---|---|---|
| What you keep updated | WordPress, the theme, its builder and every bundled plugin, all in step | Nothing on a schedule. There is no theme or plugin stack to fall out of step |
| How a page is served | Built from the database on each visit, through the theme and its builder | Built ahead of time and served as finished files from servers near the visitor |
| How you edit it | A general-purpose builder with every option the theme ships | A CMS built around what your business actually changes: services, prices, photos, posts |
| What can break it | An update to any one of those parts, or a license that lapses | A change someone makes on purpose, tested before it goes live |
Your content, your addresses and your rankings come with you: every page is moved, every old address is redirected, and you get a login to an editor that only shows what you need. A repair is still the right call for many sites, and we will say so when it is.
Want this fixed on your Divi site?
Tell us what you are seeing. We look at the site, tell you plainly what is wrong and what it takes, and quote a fixed price before any work starts.
Which of these sounds like you? (pick any)
Frequently asked
No. The layouts are still stored in each page exactly as before; the new theme just cannot interpret them. Reactivate Divi and they render again. The same holds for Divi 5, which stores layouts in a newer format but still needs Divi present to display them.
Yes. It is a separate plugin from Elegant Themes that brings the builder to other themes, and existing Divi layouts render through it. It needs an active membership for updates, and the pages remain Divi pages. It solves the brackets, not the lock-in.
Tools exist that strip the shortcodes or attempt a conversion, and results vary widely. Plain text survives. Columns, images and styled modules mostly do not arrive in usable shape. Plan on rebuilding the important pages by hand and automating only the simple posts.
They can if they stay up. Google indexes what the page shows, and a page of shortcodes is a worse page. A few hours rarely matters. If the brackets were live for days, switch back, then use URL Inspection in Search Console to request a fresh crawl of the main pages.
Keep reading
- ServiceWebsite Migration ServicesMove off WordPress, a page builder, an e-commerce platform or a slow host without losing rankings, forms or tracking — inventoried, redirected, watched.
- ServiceReplacing WordPressWhen WordPress becomes the thing you fight instead of the thing that works, it's time to move. We migrate you without losing rankings.
- ServiceWebsite Redesign ServicesA redesign either pays for itself or quietly costs you the traffic you spent years earning. How to know which one you are about to buy.