Migrating From Tilda (or Wix) to WordPress Without Losing SEO

Every builder site I’ve moved off Tilda or Wix hit the same wall: the platform was fine until the business outgrew it. You want a custom checkout, a proper quiz, server-side logic, or you just want to stop paying a monthly ransom for pages you already designed. The fear that stops most owners is simple. «I’ll lose my Google rankings.» You won’t, if you treat the move as a URL and content problem first and a design problem second. That’s the whole game when you migrate from Tilda without losing SEO.

I’m Ilya Litau, a solo web and AI developer. I’ve run this migration enough times to have a checklist that holds up. Below is exactly how I do it, what tends to break, and the numbers from a real project where the site came out faster, cleaner, and converting 46% better.

Why do website builders eventually cap your growth?

Tilda and Wix are good up to a point. They get a business online fast with a decent design. The ceiling shows up in four places.

• Logic you can’t build. A real multi-step quiz, conditional pricing, a webhook into a CRM, a payment flow that branches by plan. On builders you bolt on third-party embeds that load slow and break on you.
• Page weight and speed. Builder output ships a heavy DOM and blocking scripts. Core Web Vitals suffer, and mobile LCP is often the ranking factor you’re quietly losing on.
• Cost that scales the wrong way. More pages, more members, more features push you into a higher tier every year, and you never own the code.
• Ownership. You can’t move a Tilda «Zero Block» into another system. A redesign means rebuilding from scratch anyway.

None of that means you switch on a whim. If your builder site converts and you don’t need custom logic, stay put. I wrote a longer breakdown of that call in hiring a solo full-stack developer versus an agency, since the «who does the work» question usually lands at the same moment as «should I move platforms.»

Will I lose my Google rankings if I move off Tilda?

Not if you preserve three things: URLs, content, and metadata. Google ranks a URL based on its content and the links pointing at it. Change the platform underneath while keeping those three stable, and Google barely notices the swap. The migrations that tank are the ones where someone «cleaned up» the URL structure, rewrote all the copy, and dropped the page titles on the same day.

Here’s what actually moves the needle, ranked by how badly it hurts when you get it wrong.

Element	Risk if changed carelessly	Safe approach
Page URLs	High: lost rankings, 404s, broken backlinks	Keep identical, or 301-redirect old to new
Title tags and meta descriptions	High: CTR and relevance drop	Copy them over exactly, then improve later
H1/H2 headings and body text	Medium: relevance signals shift	Rebuild with the same headings and copy
Internal links	Medium: crawl paths and equity flow	Recreate the same link structure
Image alt text and filenames	Low to medium: image search traffic	Carry alt text over
Page load speed	Positive if improved	WordPress done right beats builder output

The pattern is clear. Nothing about the platform switch itself loses rankings. Sloppy handling of URLs and content does.

How do I map old Tilda URLs to the new site?

URL mapping is the spine of a safe migration. Do it before you write a line of the new site.

1. Export the full URL list. Pull your existing pages from Google Search Console (the Pages report) and from your sitemap. Crawl the live site with a tool like Screaming Frog to catch anything the sitemap missed. You want every indexed URL, including old blog posts and landing pages you forgot existed.
2. Decide keep or change for each URL. Default to keeping. If your Tilda slug is /page12345.html-style garbage, that’s the one case where changing earns its keep, but then you owe it a redirect.
3. Build a mapping table. Two columns: old URL, new URL. This doubles as your redirect map and your QA checklist.
4. Match the trailing slash and the case. /services and /services/ are different URLs to Google. Pick one, enforce it site-wide, then redirect the other form.
5. Flag external backlinks. Check which old URLs have inbound links (Ahrefs, or the free GSC Links report). Those URLs must resolve. A 301 to the equivalent page preserves most of the link equity.

If most of your slugs are already clean, the best outcome is zero redirects because every URL stays identical. That’s the target I aimed for on the Club 365 project below, and it’s why the transition was invisible to search engines.

How do 301 redirects protect your SEO during a migration?

A 301 is a permanent redirect. It tells Google «this page moved here for good» and passes almost all ranking signals to the new URL. This is your safety net for every URL you can’t keep identical.

Rules I follow:

• 301, never 302. A 302 (temporary) does not pass equity reliably. Use 301 for permanent moves.
• One hop, no chains. The old URL redirects straight to the final new URL. Chains of redirects (A to B to C) waste crawl budget and slow the page.
• Redirect to the closest equivalent, not the homepage. Dumping every dead URL onto the homepage reads as a soft 404. Map each one to the most relevant new page.
• Keep old redirects live for at least a year. Google revisits URLs on its own schedule. Pull the redirects too early and you drop the equity you just preserved.

On WordPress I set these up with a lightweight redirect plugin or directly in the server config. Both work. The config route is faster because it fires before WordPress even boots.

How do I keep content and metadata intact?

Content parity is the boring part that decides whether rankings hold. Rebuild each page so a search crawler sees the same thing it saw before.

1. Carry over titles and meta descriptions verbatim. Set them in your SEO plugin. Match them one-to-one against the old pages first, optimize afterward once rankings are stable.
2. Preserve the heading hierarchy. Same H1, same H2s, same order. That’s a strong relevance signal and it costs nothing to keep.
3. Keep the body copy. Improve design and layout all you want. Don’t gut the words on the same day you switch platforms. Change one variable at a time.
4. Recreate structured data. If Tilda gave you any schema (Organization, FAQ, Breadcrumb), rebuild it. WordPress makes richer schema easy, so this is an upgrade, not just parity.
5. Regenerate a clean XML sitemap and keep the same canonical rules.

For content-heavy sites this is exactly where a builder hurts you. I ran into it building the 40-plus page site for Nexora Legal, where hand-built static pages gave far tighter control over headings and schema than any builder would. The same principle applies to a migration: the more pages you have, the more disciplined your content mapping needs to be.

What’s the safest way to launch without downtime?

Parallel build, single DNS cutover. Never touch the live site’s DNS until the new one is fully built and tested.

1. Build the new WordPress site on a staging domain (a subdomain or temp URL). The old Tilda site stays live and serving traffic the whole time.
2. QA against the mapping table. Click through every old URL’s new equivalent. Check titles, headings, forms, payments, tracking.
3. Set up all redirects on staging so they’re primed to fire the moment DNS points over.
4. Lower your DNS TTL a day before (to 300 seconds) so the cutover propagates fast.
5. Point DNS to the new host. This is the only moment anything actually switches. Because both sites were already complete, there’s no gap. Users hit the old site, then the new one, with no error page in between.
6. Test forms, payment, and analytics immediately on the live domain.
7. Resubmit the sitemap in Search Console and run the URL Inspection tool on your top pages to prompt a recrawl.
8. Watch GSC coverage and rankings for 30 days. Expect minor wobble in week one, then a return to baseline.

Payment and quiz flows are the parts that most often break silently on migration day, so I test those first and last.

Real result: migrating Club 365 from Tilda to WordPress

Club 365 is a subscription yoga school. Their Tilda site ran a working quiz, GetCourse-based payments, and rankings they couldn’t afford to lose. The brief was blunt: move to WordPress, break nothing.

Here’s what I did and what came out of it:

• Kept every URL identical. No slug changes meant almost no redirects and nothing for Google to relearn.
• Preserved the working quiz and rebuilt it on the new stack with the same flow.
• Kept the GetCourse payment integration intact straight through the switch.
• Zero downtime via the parallel-build, single-cutover method above.

The outcome: conversion rose 46% after the move, with no ranking loss and no downtime. The full teardown of what broke and how I fixed it lives in the Club 365 case study. The conversion lift didn’t come from magic. It came from a faster, cleaner site with the same content and a payment and quiz flow that no longer fought the platform.

Tilda/Wix versus WordPress after migration: what actually changes

Factor	Tilda / Wix	WordPress (built right)
Custom logic (quiz, CRM, payments)	Embeds and workarounds	Native, server-side, reliable
Page speed / Core Web Vitals	Heavy output, harder to fix	Tunable, usually faster
Ownership of code	Locked to the platform	You own it, portable
Monthly cost trend	Rises with features and pages	Hosting only, flat
SEO control (schema, redirects, canonicals)	Limited	Full control
Design freedom	Templated within limits	Anything you can build

Migration SEO checklist (copy this)

• Export every indexed URL (GSC plus sitemap plus crawl)
• Build an old-to-new URL mapping table
• Keep URLs identical wherever possible
• 301-redirect every URL that changes, one hop, closest equivalent
• Copy title tags and meta descriptions verbatim
• Preserve H1/H2 hierarchy and body copy
• Carry over image alt text
• Recreate internal links and structured data
• Build on staging, keep the old site live
• Lower DNS TTL a day before cutover
• Single DNS switch, then test forms, payments, analytics
• Resubmit the sitemap, inspect top URLs in GSC
• Keep redirects live 12-plus months, monitor for 30 days

That checklist is the difference between a migration nobody notices and one that costs you three months of traffic. If you’d rather hand the whole thing off, that’s what I do. Browse the case studies or tell me about your site and I’ll map the migration before touching anything.

Frequently asked questions

Will I lose my SEO rankings when migrating from Tilda to WordPress?

No, if you preserve URLs, content, and metadata. Keep every URL identical or 301-redirect it, copy titles and headings over exactly, and rebuild pages with the same body text. Google ranks the URL and its content, not the platform underneath. On Club 365 rankings held with zero loss. Migrations tank only when someone changes URLs and copy at the same time.

How long does a Tilda-to-WordPress migration take?

For a typical 5-to-15 page business site, plan on one to three weeks. Most of the time goes into rebuilding pages, wiring custom logic like quizzes or payments, and QA against the URL map. The actual DNS cutover takes minutes. Larger sites with 40-plus pages or heavy custom logic run longer, because content mapping and testing scale with page count.

Do I need to keep the same URLs, and what if my Tilda slugs are ugly?

Keeping URLs identical is the safest path: no redirects, nothing for Google to relearn. If your slugs are auto-generated garbage, you can improve them, but every changed URL then needs a 301 redirect to its new equivalent, one hop, no chains. Keep those redirects live for at least a year so Google fully transfers the ranking signals.

How much does it cost to migrate off a website builder?

It depends on page count and how much custom logic you need. A simple brochure site is far cheaper than one with a quiz, CRM sync, and payments. Working with me directly, without an agency markup, you pay for the actual build, not account managers. Send me your current site and I’ll scope it before quoting.

Is the improved conversion guaranteed?

No honest developer guarantees a conversion number. The 46% lift on Club 365 came from a faster site with a payment and quiz flow that stopped fighting the platform, plus cleaner UX. Migration removes the technical friction a builder imposes; whether conversion jumps depends on your funnel. What I do guarantee is no ranking loss and no downtime when the method above is followed.