How to migrate from Tilda to WordPress without losing pages

How to migrate from Tilda to WordPress without losing pages

Migrating from Tilda to WordPress is not a design exercise first. It is a page-by-page transfer, and that means the address of each page matters as much as the text on it. If one URL disappears, the page can disappear with it, at least for search engines and old bookmarks.

The safest way to approach how to migrate from Tilda to WordPress without losing pages is to treat the move like a ledger, not a redesign. You need names, URLs, types, and a yes-or-no answer for each page. That sounds slow. It is slower than guessing.

1. Check which Tilda URLs must survive exactly as they are

Start with the pages that already have a track record: indexed pages, pages shared in social posts, and pages linked from partner sites. Those are the ones that deserve one-to-one continuity. A page with 20 external links is not the same as a page nobody has ever seen.

One useful trick is to separate “must keep” from “can change.” A product page, a service page, and a long-read article usually belong in the first group. A temporary promo page may not. If you are unsure, mark it for review instead of assuming it can be replaced.

Search Console, analytics, and backlink reports give you the first 3 lists to compare. If the same page appears in all 3, treat it carefully. That page is carrying weight, even if it looks plain in the editor.

Some site owners try to rebuild everything from memory. That breaks fast. A page that seems minor can be the one that receives traffic from a forum, a PDF, or an older newsletter. Old links keep working only if you respect them.

2. Build a page inventory for the migration handoff

Create a simple inventory before any WordPress work begins. Each row should include the current Tilda URL, the target WordPress URL, the page type, and any special content blocks that must be recreated. A spreadsheet is enough. A messy chat thread is not.

Keep the inventory practical. If a page has a form, write down the form fields. If it has a gallery, note the number of images. If it has a map, video, or accordion block, name it. Rebuilding from “there was a form here somewhere” invites mistakes.

This inventory also helps with ownership. One person can check URLs, another can check content, and a third can confirm media files. Three people, one sheet. That is usually cleaner than a dozen screenshots.

If the site has 40 pages, the inventory saves arguments later. If it has 400 pages, it becomes the only way to stay sane. The number matters because every missing row becomes a missing page.

For reference checking, you can also compare how the site handles other structured pages, such as the dream dictionary starting with k. The page itself is not about migration, but its clean page structure is a reminder that a page list should stay orderly.

3. Decide the URL strategy before building anything in WordPress

Before you open the WordPress editor, decide what happens to each slug. Some pages should keep the same slug. Some should move into a new structure. Some may be merged into one better page. That decision needs to happen before the build, or you will create accidental page loss during setup.

Three choices are enough for most sites: keep, move, merge. Keep means the old address stays. Move means the page gets a new path. Merge means two or more old pages become one new page. Each choice has consequences for redirects and internal links.

Do not rename a slug simply because it looks cleaner. Clean does not matter if the old URL is already indexed. A tidy structure is helpful, but a dead page is not tidy at all.

One practical rule works well: if a page already ranks or attracts links, keep the slug unless there is a clear reason not to. If you must change it, record the exact old and new paths in the inventory. That record becomes the basis for the redirect map later.

4. Recreate the existing page structure in WordPress first

Set up WordPress pages, menus, and hierarchy before redesigning anything. The goal is simple: the old pages need visible destinations in the new system. If the hierarchy is missing, content editors start guessing, and guessing causes misplaced pages.

This step is about structure, not visual polish. Create parent pages, child pages, and the main menu items first. Then match the current site map as closely as possible. The design can change later. The destinations should already exist.

That order matters because a missing page is easier to fix when it has already been created in WordPress. A page with no parent, no menu item, and no target URL is just a problem waiting for launch day. Nobody wants to discover it after traffic has moved.

If you need a parallel example of how pages are organized by topic, look at the dream dictionary starting with p. Different content, same lesson: page order should make sense before the content lands inside it.

5. Preserve page-by-page content during the move

Move the content page by page, not in one broad sweep. Text, images, videos, downloadable files, forms, and embedded widgets all need a check. A migration can look finished while quietly dropping one form field or one embedded map.

Use the inventory as a checklist for each page. Confirm the headline, body text, CTA buttons, media captions, and any hidden elements that affect behavior. One page may have a simple layout; another may depend on 6 blocks arranged in a specific order. That order matters.

Be careful with forms, because they often fail quietly. A contact form that looks fine in WordPress may send submissions to the wrong inbox or no inbox at all. That is a small technical error with a large business cost.

Media files deserve the same attention. An image can display correctly but lose its alt text or filename. A video can load on desktop and fail on mobile. A PDF can remain linked in the old system and vanish from the new one if nobody copies it across.

Sometimes the page content itself tells you what needs to survive. For example, a site section like the dream dictionary starting with c shows how repeated structure can support many entries without confusion. Your migration should preserve that kind of repeatable page logic, not flatten it.

6. Set up redirects for every replaced or renamed page

Any old Tilda URL that does not remain unchanged needs a redirect plan. In most cases, that means a 301 redirect from the old address to the new WordPress page. Without it, visitors hit dead ends and search engines waste time on broken paths.

Map the redirects one by one. Old URL on the left, new URL on the right. No bundles, no “close enough,” no shortcuts based on page title alone. If 2 pages merge into 1, both old URLs should point to the new combined page.

This is where a lot of migrations fail. A developer may build the new page correctly, yet forget the old path. The content exists, but the address does not lead anywhere useful. That is how pages get “lost” without ever being deleted.

Keep the redirect map with the inventory. It will matter again after launch, because some links will still point to Tilda long after the switch. Old newsletters do not update themselves. Neither do backlinks from other sites.

If you need to check whether a page contains the right legal or support details before you redirect it, use tools like how to check if a website и how to check if a website. Those pages are about verification, and verification is exactly what redirect mapping needs.

7. Test the migrated pages before going live

Test every migrated page in a staging environment before launch. Open the page, click internal links, submit forms, and check media on desktop and mobile. Then test the old URL and confirm that it lands on the intended WordPress page without an error.

A good test list has at least 4 checks: page loads, link paths, form behavior, and media display. If one of those fails, fix it before going live. A half-working page is still broken.

Do not stop at the homepage. Deep pages are where migration mistakes hide. A page three levels down in the site hierarchy can fail while the front page looks perfect. That mismatch is common, and it fools teams that only inspect the top layer.

Test internal links from the content itself. If a paragraph links to another page, that link should point to the WordPress destination, not the old Tilda path. A site can have perfect pages and still feel broken because the links were forgotten.

If a page depends on external references, such as an FAQ or policy page, verify those too. A useful check is how to find a website's FAQ, because missing support pages can create the same confusion as missing content pages.

8. Do a post-launch page audit and fix missed URLs

After launch, crawl the site and look for 404s, broken links, and pages that were skipped in the move. This is not a ceremonial step. It is where you catch the pages that nobody noticed during staging.

Scan the crawl report for old Tilda URLs that still appear in browser logs, search results, or internal links. If a URL is missed, patch the redirect or add the missing WordPress page immediately. Waiting even 1 week can send mixed signals to search engines and visitors.

Check the site in two directions. First, from the new WordPress pages outward, to see whether the internal links point to the right targets. Second, from the old Tilda URLs inward, to confirm every old page resolves correctly. Both directions matter.

A quick audit can reveal patterns. If 5 old URLs all point to the wrong new page, the mapping rule was probably too broad. If only one page is missing, the inventory may have skipped a block or a child page. Either way, the fix is specific, not abstract.

There is one last habit worth keeping: treat the migration as a live list, not a one-time task. Pages get added, renamed, and merged later. The inventory, redirect map, and URL strategy should stay updated so the next change does not break the last one.

For readers who like to compare page structure with another content system, the dream dictionary starting with k и dream dictionary starting with p both show how stable page paths make a site easier to maintain, even when the content inside them changes.