Stay up to date with AI tools, model releases, and developer workflows that matter.
Weekly. Free. One click to leave.
7 Day Free Trial. Cancel Anytime.
In a recent development, elementor made your site easy to build. It may also be making it slow. Here's how to move a site onto the Block Editor without breaking URLs, losing content or dropping out of Google.
It has been revealed that page builders solved a real problem. Before the Block Editor matured, they were the easiest way to give clients drag-and-drop layouts. Many of those sites are still running today, and a lot of them are slow on phones.
According to recent reports, the data backs that up. According to the HTTP Archive Core Web Vitals Technology Report for June 2026, 36.8% of Elementor sites pass Core Web Vitals on mobile. Sites built with the Block Editor pass 53.0% of the time. That's correlation, not proof, since hosting and setup matter too. But in my experience, it matches what happens when you remove the builder from a slow site.
My reason for migrating sites off Elementor is simple: **page builders make websites heavy. **Having stated that, Elementor has improved a lot. Its performance settings, Flexbox Containers, and asset-loading options cut much of the bloat, and a carefully tuned Elementor site can pass Core Web Vitals. But tuning only goes so far. Youβre still shipping the builderβs framework, wrapper markup and scripts, and every plugin or Elementor upgrade is a chance for the speed to slip again.
For small business sites that donβt need drag-and-drop editing, rebuilding the same design on the WordPress Block Editor (Gutenberg) removes that weight at the source, without changing what the client sees.
Recent findings suggest that this guide follows the order I use. It assumes you're comfortable with WordPress admin, WP-CLI and a staging site. If you need to set those up first, SitePoint's guide to the ultimate WordPress development environment covers the tooling.
Not every Elementor site needs to move. Migration makes sense when:.
It's harder to justify when the site leans on Elementor Pro features you'd need to replace, such as complex popups, dynamic loops or WooCommerce templates. Those can all be rebuilt, but the job gets bigger fast.
You can't prove a migration worked without "before" numbers. Capture these on the live site first.
Crawl the site with a tool such as Screaming Frog, and export every indexable URL with its title, meta description, H1 and canonical tag. You can also pull published pages and posts with WP-CLI:.
Run Google PageSpeed Insights, which uses Lighthouse for its lab scores, on the homepage and two or three key templates. Save the mobile lab scores and, if the site has enough traffic, the field data from real consumers.
Export the last three months of pages and queries from Google Search Console. That's what you'll compare against after launch.
Industry observers note that elementor stores each page's layout as JSON in the elementordata post meta field, and marks builder pages with elementoredit_mode. This command lists every page that uses the builder:.
Then list everything else Elementor controls, which is easy to miss:.
Industry observers note that on the small business sites I've migrated, the inventory usually turns up more than the owner expects. The pages are the easy part. The surprises are saved templates nobody remembers creating, a popup still running on every page, add-on widgets from plugins that were installed once and forgotten, and contact forms that live inside Elementor Pro rather than a form plugin. Finding those before the rebuild saves a broken launch.
Industry observers note that work on a staging copy. Install a block theme, such as Twenty Twenty-Five or a lightweight starter theme, and move the Elementor global styles into theme.json. That way colors, fonts and spacing are defined once, instead of in every widget.
Recent findings suggest that copy the hex values and font names from Elementor's Site Settings so the upcoming site matches the old one. Rebuild the header and footer as template parts in the Site Editor. If you'd rather write a theme yourself, SitePoint's series on building a WordPress theme from scratch covers the basics.
Most Elementor sites repeat the same few sections: a hero, a services grid, testimonials and a call to action. Build each one once as a block pattern, then reuse it on every page. Patterns are plain block markup, so you don't need React to write them, whatever you may have heard about React and WordPress development.
In a block theme, any PHP file in the /patterns folder with a header comment is registered automatically:.
For page content, there's a useful shortcut. Elementor saves a plain HTML copy of each page into post_content. Open a page in the Block Editor, and the old content usually appears in a Classic block. Choose Convert to blocks, then delete the leftovers and rebuild the layout with your patterns. It keeps the copy and images, so you only redo the design.
The difference reveals up in the page source. Here's typical front-end markup for a single heading on an Elementor page, using the older section and column layout:.
And the same heading as a block:.
Industry observers note that newer Elementor versions with Flexbox containers and the optimized markup settings trim some of those wrappers, but most older sites still carry all of them. Multiply that by every element on every page, and the weight adds up.
To speed up this step, I built a free Elementor to Gutenberg converter. Paste in a page's elementordata JSON from Step 2, and it returns block markup you can paste into the Block Editor's code editor. It handles headings, text, images, buttons, spacers, dividers and column layouts, and lists anything it can't convert, such as forms and popups, for you to rebuild by hand. It runs entirely in your browser, so the page data never leaves your computer.
It has been revealed that the code is rarely what holds a migration up. Content is. Once clients see their site being rebuilt, many decide it's time to rewrite their pages too, and the project ends up waiting on copywriters and approvals. My fix is to separate the two: migrate the existing content as it is, launch, then patch the copy afterwards. That keeps the speed and SEO gains on schedule, and it means any ranking change can be traced to either the migration or the upcoming copy, not both at once.
This is the step that decides whether rankings hold.
To spot-check a redirect or a status code from the command line:.
Industry observers note that when staging matches the live site, deploy it. Then:.
Sources indicate that leave the old elementordata meta in place for a few weeks, in case you need to roll back. Once you're confident, take a backup and remove it to shrink the database.
According to recent reports, run PageSpeed Insights again straight away for lab scores. Field data takes longer: the Chrome UX Report uses a rolling 28-day window, so give it a month before judging real-user results. Compare Search Console clicks for the same period before and after launch.
In my migrations, the biggest change is usually page weight and loading time, because the builder's CSS, JavaScript and wrapper markup are gone. What doesn't always improve is server response time. If the site is on slow shared hosting, the first byte still arrives late, and that needs a hosting fix, not a rebuild. Search traffic should hold steady if the URLs and metadata were protected. If it drops, the Step 5 crawl comparison is the first place to look.
In a recent development, moving off Elementor isn't a one-click job, but it isn't a full redesign either. Record a baseline, inventory what the builder controls, rebuild with patterns, and protect every URL. Most of the speed gain comes from removing code the site never needed. For what to tackle after that, see these practical web performance techniques. Most of the risk comes from rushing the SEO checks. Done carefully, the client gets the same site, a faster one, and an editor that comes with WordPress itself.
***Author Bio: ***Fahad Raza is a WordPress developer and SEO consultant based in Sydney. He has built websites since 2005, worked in SEO for more than 18 years, and spent eight and a half years on the IKEA Australia and Latest Zealand website.
7 Day Free Trial. Cancel Anytime.
