How I fix it · 01 / 04

Map every page and template.

A full crawl: every URL, template, widget, shortcode, form and redirect, plus the pages that bring traffic and leads.

Measure what the builder costs.

Mobile LCP, CSS and script weight per template, and the plugins you can’t remove without breaking the site.

Rebuild as native blocks.

Custom Gutenberg blocks that match your design, content moved page by page on staging, so editors keep working the way they do now.

Launch with every URL kept.

Redirect map, meta and schema checked before launch, then Search Console watched daily for 30 days.

Inventory of every template0 issuesMapping
Step 1 · map0 / 5 migrated
  • HomepageMapping…
  • Service pagesMapping…
  • Blog postsMapping…
  • Landing pagesMapping…
  • Case studiesMapping…
  1. 01 / 04

    Map every page and template.

    A full crawl: every URL, template, widget, shortcode, form and redirect, plus the pages that bring traffic and leads.

  2. 02 / 04

    Measure what the builder costs.

    Mobile LCP, CSS and script weight per template, and the plugins you can’t remove without breaking the site.

  3. 03 / 04

    Rebuild as native blocks.

    Custom Gutenberg blocks that match your design, content moved page by page on staging, so editors keep working the way they do now.

  4. 04 / 04

    Launch with every URL kept.

    Redirect map, meta and schema checked before launch, then Search Console watched daily for 30 days.

  5. Launch day0 issuesNative
    Step 4 · launch5 / 5 migrated
    • Homepage✓ Native blocks
    • Service pages✓ Native blocks
    • Blog posts✓ Native blocks
    • Landing pages✓ Native blocks
    • Case studies✓ Native blocks
    Launched: every URL kept, mobile LCP 1.8 s, rankings stable after 30 days.
Mapping: 0
What’s covered

Six things a migration must keep.

Each one planned before the first block is built, with what usually goes wrong.

KeepWhat I planWhat usually goes wrong
URLsEvery indexed URL kept or redirectedBlog moved to /blog/ with no redirects
Meta and schemaTitles, descriptions, canonicals, structured dataMeta reset to defaults on launch
ContentPages, posts, custom post types and mediaShortcodes left as raw text
DesignSame look, rebuilt as reusable blocksPixel-perfect copy with builder bloat kept
Forms and trackingEvery form, event and conversionThank-you page conversions lost
EditorsA workflow your team already understandsEditors locked out of their own pages
Pricing

Fixed scope. Fixed price.

Before you sign, we agree the page list and a mobile LCP target. You see it measured at handover.

Small$2,400Up to 15 pages · 3 weeks
  • Custom Gutenberg blocks
  • Every URL and meta kept
Get a fixed quote
Migration + growthComplete$7,500Full site · 6–8 weeks · faster and found
  • Everything in Fullblocks, content, redirects, CWV target
  • Technical SEO auditindexing, canonicals, internal links
  • Schema and AI readabilityOrganization, Service and FAQ markup
  • Tracking rebuiltGA4, GTM and consent on the new site
  • Leak watch for 3 monthsweekly checks after launch
Get a fixed quote
Prices exclude VAT · WooCommerce and multilingual sites quoted separately

Why page builders slow you down

Elementor, WPBakery and Divi load CSS and scripts for every widget they offer, on every page, whether you use them or not. Nested containers add thousands of extra elements.

You can optimize around it, but there’s a ceiling. On most builder sites I see, mobile LCP won’t go much below three seconds without removing the builder.

When migration is worth it

Migrate when speed is costing you leads, when the builder blocks a redesign, or when every new page needs a developer anyway.

Stay when the site is small, traffic is low and nobody edits it often. Then speed optimization is the cheaper fix.

Keeping rankings through a migration

Rankings drop when URLs change without redirects, when meta and headings get reset, or when internal links break. All three are preventable.

I crawl the old site first, map every URL, keep titles and descriptions, and compare both crawls before launch.

Editing after the move

Native Gutenberg blocks look like the old sections, but they’re lighter and harder to break. Your team picks a block, fills in fields, and the design stays consistent.

Most editors find it simpler than the builder within a week. A short recorded walkthrough is included.

How launch day works

Everything is built and tested on staging. On launch day, redirects and the new theme go live together, and I check the top pages and forms straight away.

For 30 days after, I watch Search Console for errors and ranking changes, and fix anything that slipped through.

Not sure where your site stands?The free scan checks your speed, meta and schema on your real pages, in a few minutes.Run the free scan
Migration FAQ

Migration, answered.

Rankings, design, editors and how long it takes.

Something else?Write a line about your site. You’ll get a reply from me within one business day.

Not if URLs, meta and internal links are kept. I map every URL before launch and watch Search Console for 30 days after.

It looks the same unless you want changes. The design is rebuilt as blocks, not redesigned.

Yes, in Gutenberg with custom blocks. Most editors find it simpler than the builder.

Three weeks for a small site, four to eight for larger ones. The old site stays live until launch.

Yes, that’s a separate service with its own page. Gutenberg is usually cheaper if your team knows WordPress.

Both are possible. They add scope, so I quote them after a short look at the site.

Often done together