Your WordPress site has been running for years, but it is getting slower, updates keep piling up and every change feels like a risk. Moving to a custom website is the obvious next step. The biggest fear is usually: will I lose my place in Google? It does not have to happen. In this plan you will read how to handle content, URLs, redirects and SEO, so your visitors and rankings move with you.

When switching makes sense

Not every WordPress site needs replacing. If your site works well, is fast and takes little effort to maintain, there is little reason to move. Switching does pay off in these situations:

  • The site is slow and optimising yields little more, often because of a heavy theme or a page builder.
  • Updates have become a risk. Something breaks after every update, or you no longer dare to update.
  • You rely on many plugins, some of which are no longer maintained or cost licence fees every year.
  • You need features WordPress struggles with, such as your own quote flow, a customer portal or a link with your accounting.
  • A redesign is planned anyway. Then it is a logical moment to rethink the technology as well.

Still unsure whether custom is the right direction? First read WordPress or a custom website: an honest comparison. Sometimes a custom WordPress theme is enough as an intermediate step. The differences are in custom WordPress website: what does it really mean?

Inventory: content, URLs, forms, plugins

A good migration starts with knowing what you have. Do not skip this step. Whatever you forget in the inventory will be missing after launch.

Content

List all pages, blog posts, categories and landing pages. For each page, note whether it moves over, gets merged with another page or disappears. Thin or outdated content does not have to come along. A migration is a good moment to tidy up.

URLs

Make a complete list of all URLs. Good sources are your current site’s XML sitemap, a crawl with a tool such as Screaming Frog and the Performance report in Google Search Console. The last one matters most: it shows which pages get impressions and clicks. Those pages deserve the most care.

Do not forget images and PDFs if they bring in visitors through Google. Also note which pages receive links from other websites.

Forms and features

Which forms are on the site? Where do submissions end up: in a mailbox, a CRM, a newsletter system? Are there bookings, payments or a search function? Each of these features has to be rebuilt or connected in the new site.

Plugins

Go through every active plugin and note what it does. Some will drop away, because the feature is built into the new site. Others do things you only miss once they are gone: a redirect plugin holding old redirects, an SEO plugin with its own titles and meta descriptions, a cookie banner, analytics tracking. Extract that data before you shut down the old site.

URL structure and 301 redirects

This is the step where most migrations lose their SEO. Google knows your pages by their current address. If that address changes without a redirect, the old URL returns a 404 error and Google sees the new page as a page without history.

Keep URLs where you can

The safest redirect is no redirect at all. If the new site can use the same URLs, do so. With custom development you have full control over the URL structure, so this is usually feasible. Typical WordPress patterns such as /2023/05/article-title/ or /category/news/ can be kept or deliberately simplified.

What is a 301 redirect?

A 301 redirect tells browsers and search engines that a page has moved permanently to a new address. Visitors land on the right page automatically, and Google transfers the signals of the old URL to the new one. A temporary redirect (302) sends that signal less clearly and does not belong in a migration.

Build a redirect map

In a spreadsheet, put every old URL next to its new destination. These rules keep it clean:

  • Every old URL points to the most relevant new page, not en masse to the homepage.
  • No chains: old points directly to new, without an intermediate step.
  • A page that genuinely disappears without a replacement may return a 404 or 410. That is better than an irrelevant redirect.
  • Watch details such as a trailing slash, capital letters and the version with or without www.

Include the existing redirects from your WordPress plugin in the same list. That way old links from earlier moves keep working.

Migrating content and media

WordPress can export all your content, through the built-in XML export or through the REST API. In a migration to a custom site we import that export and convert the content into the structure of the new content management system. A few points of attention:

  • Clean up the markup. Content from a page builder is often full of shortcodes and extra HTML. That has to go, or you drag the clutter along.
  • Images. Bring the original files, not just the resized versions. Convert them to a modern format such as WebP or AVIF and keep the alt texts.
  • Metadata. Carry over the SEO titles and meta descriptions from your SEO plugin, together with publication dates, authors and categories.
  • Internal links. Links in your text point to old URLs. Update them to the new addresses so they do not have to pass through a redirect.

We often move a small site with a handful of pages by hand. That is also a chance to improve the copy. For a site with many articles we write an import script, so nothing gets lost.

SEO checklist before launch

Build and test the new site on a separate staging environment that is shielded from Google. Before launch, go through this list:

  1. All redirects in the redirect map have been tested: every old URL returns a 301 to the right page.
  2. Every page has a unique title and meta description.
  3. Every page has one H1 and a logical structure with H2 and H3.
  4. Canonical tags point to the correct, final URL.
  5. The XML sitemap contains only the new, indexable URLs.
  6. Robots.txt blocks nothing that should be indexed, and the staging noindex has been removed.
  7. Structured data, for example for your business, articles or FAQ, is present and validates.
  8. Images have alt texts and are optimised.
  9. Forms work and submissions arrive where they should.
  10. Analytics is installed, with cookie consent where required.
  11. The site is fast on mobile. Speed is one of the benefits of switching, so measure it. Why it matters is explained in why fast websites win more customers.
  12. HTTPS works everywhere, without mixed content.

Plan the launch for a quiet moment, not just before a busy period. Hosting and DNS must be ready. If you are also changing hosts, lower the TTL of your DNS records in advance so the switch takes effect quickly. Check that your email (the MX records) stays unchanged. More on hosting is in website hosting: what you pay and why.

After launch: monitoring Search Console

The first weeks after launch matter. Google has to recrawl your new site and process the redirects. Some ranking fluctuation during that period is normal.

  • Submit the new sitemap in Google Search Console.
  • Monitor the indexing report (Pages). Watch for unexpected increases in “Not found (404)” and “Page with redirect”.
  • Compare performance with the period before the migration: impressions, clicks and positions for your most important pages and queries.
  • Check your key URLs with the URL Inspection tool.
  • Keep the redirects in place for a long time. Google recommends at least a year. Ideally you keep them permanently, because old links on other sites do not disappear.

If an important page drops, first look at the redirect, the canonical and the content. Was text lost along the way? Is the page still linked internally? The cause is usually one of those points.

Cost and timeline

In practice, a migration to a custom site is a new website plus the move. The cost depends mainly on:

  • the number of pages and posts that come along;
  • how much content needs cleaning up or rewriting;
  • the features that need rebuilding, such as forms, bookings or a webshop;
  • integrations with other systems.

At WKD Solutions a custom website starts from €650. Hosting and maintenance start from €150 per year. What is realistic for your site is explained in what does it cost to have a website built? After a first conversation you receive a clear quote, with the migration included.

The timeline also depends on the size. A business site with around ten pages moves faster than a site with hundreds of articles and a webshop. Either way, set aside time for the inventory and the redirect map. That is a step you should not rush.

Conclusion

Moving from WordPress to a custom site does not have to cost you visitors or rankings. The difference lies in the preparation: a complete inventory, a well-considered redirect map, carefully migrated content and strict checks before and after launch. Follow those steps and you often start with a faster site and a cleaner foundation than before.

Want to know what a switch would mean for your site? See how we approach having a custom website built, or book a free 30-minute call. You talk directly to the developer who carries out the migration.