bricks migrate
Home / Blog / Elementor to Bricks

Elementor to Bricks

How to Move a WordPress Site to Bricks Without Losing SEO

Rebuilding in Bricks changes how your pages are built, not what Google should see. Here is how to keep it that way.

Jesús SiscoBy Jesús Sisco·11 November 2026·3 min read
Key takeaways
  • The builder doesn’t affect rankings. Changed URLs, titles and content do.
  • Inventory every page and its SEO data before you rebuild.
  • Rebuild on staging, keep URLs the same where you can, and redirect any that change.
  • Compare old and new with a crawl before launch, then watch Search Console for a few weeks.

Moving from Elementor, Divi or WPBakery to Bricks is a rebuild: pages are recreated in the new builder rather than converted. Google doesn't care which builder you use. It cares whether the same URLs still exist, whether they say the same things, and whether they load well. Keep those three under control and the move is safe.

Step 1: Inventory the current site

  • Crawl the site and export every URL with its title, meta description, H1, canonical and status code.
  • Pull the top pages and queries from Google Search Console for the last year.
  • List templates, popups, forms and any dynamic content built with the old builder.
  • Note which plugins exist only to support the old builder (add-on packs, extra widgets).

Step 2: Decide what stays the same

The safest migration keeps every URL identical. On WordPress, that's usually possible: the page slugs live in WordPress, not in the builder. If you're also changing structure (merging pages, new categories), write down every change and plan a 301 redirect for each. The general process is the same as any migration; Tormet Labs has a full website migration SEO checklist.

Step 3: Rebuild on staging

Work on a copy of the site, never live. Set up global styles, classes and templates first, then rebuild page by page. Keep headings and body text the same unless you have a reason to change them, and recreate structured data, alt text and internal links.

Step 4: Clean up old builder content

Divi stores layouts as shortcodes inside your posts, and other builders leave their own data behind. If old blog posts were built with the previous builder, convert them so the content is still readable once that builder is switched off. Check a sample of old posts with the old builder disabled on staging.

Step 5: Compare before you launch

  • Crawl staging and compare against the original crawl: same URLs, titles, H1s and indexability.
  • Check word counts on key pages haven't dropped sharply.
  • Test PageSpeed on the main templates. This is where you should see the gain.
  • Test forms and any dynamic content by hand.

Step 6: Launch and watch

Go live, remove any staging blocks, confirm redirects work, and deactivate the old builder and its add-ons once you're sure nothing depends on them. Then watch Search Console for a few weeks for errors or pages losing clicks.

Start small if you prefer

You don't have to move everything at once. Building one landing page or service page in Bricks inside your current site is a low-risk way to compare. If you're moving from Divi specifically, see Divi to Bricks migration; from Elementor, the Elementor to Bricks service. Still deciding? Read Bricks vs Elementor first.

Jesús Sisco

Jesús Sisco

WordPress and technical SEO specialist. I move sites from Elementor and Divi to Bricks, build new ones in Bricks, and make sure the rankings come along. Based in Madeira.

Elementor to Bricks migration →

Ready to move to Bricks safely?

Send me your site and what's going on. You get one reply, from me, within one working day. No call needed.

Get a free site check