Moving off WordPress without losing your search rankings

WordPress runs a large share of the business websites in Bangladesh, and for a site that is purely pages of text it is a perfectly reasonable place to be. The trouble starts when the site has to do something — take a booking, take a payment, hold inventory, give staff a place to work. At that point the site becomes a stack of plugins from a dozen different authors, and the reliability of your bookings is the reliability of the least-maintained one.

Updated 19 September 2026

The short version

The usual reason to move is not fashion, it is that something important now depends on a plugin nobody maintains.
The risk in moving is not the build. It is losing the search rankings you already have, and that risk is entirely avoidable.
Map every existing URL to its new address and redirect it. This one step is the difference between a clean move and a disaster.
Keep the old site running until the new one is proven, and watch Search Console for a fortnight afterwards.

Why businesses actually move

In our experience it is rarely a single dramatic failure. It is the accumulation:

The booking plugin only sends a request

The guest fills a form, you get an email, and somebody has to reply before anything is booked. Every hour of that delay is a guest who booked elsewhere. Most affordable WordPress booking plugins work this way, and no amount of configuration changes it.

Updates are a gamble

WordPress, the theme and twenty plugins each update on their own schedule. Applying them can break the site; not applying them leaves known security holes open. Neither option is comfortable, so most sites drift into the second one.

The PHP underneath has stopped getting security fixes

This is the one owners almost never know about, because nothing visibly changes. The site keeps working on a version of PHP that no longer receives security patches, and stays there for years. Our free website check reports the version your site is on.

Plugin licences that renew forever

The booking plugin, the form plugin, the speed plugin, the multilingual plugin. Individually small, annually permanent, and the site breaks when one lapses.

It is slow and nobody can say why

Thirty plugins loading their own scripts on every page. The usual fix is another plugin, which is another thing to load.

What breaks in a badly run migration

The build is the easy part. These are what cost businesses money:

URLs change and rankings vanish

Your old page was at one address and ranked there for years. The new site puts it somewhere else, the old address returns a 404, and Google drops it. Traffic falls within weeks and takes months to recover. This is the big one, and it is completely preventable.

Images are left behind

Years of uploads live in the WordPress media library. If they are not moved, half your pages come up blank and you will not notice until a customer mentions it.

Forms silently stop sending

The contact form posts successfully, shows a thank-you message and delivers to nobody. Nothing looks wrong from the outside. Enquiries simply stop, and you assume business is quiet.

Email breaks with the hosting

If your email was on the same host as the site, moving the site can take the email with it. Move them as separate decisions and check the mail records before you switch anything.

The migration checklist

This is the order we work in. Nothing here is optional on a site that already has traffic.

Inventory every URL first

Pull the full list of live addresses from the existing sitemap, from Search Console and from a crawl. You cannot redirect what you did not know existed.

Write the redirect map before the build

Every old address gets a permanent redirect to its new equivalent. Where there is no equivalent, decide deliberately where it should go — not to the homepage by default, which search engines treat as a soft 404.

Keep the titles and the headings

The pages that rank, rank for the words already on them. Redesign the page; do not rewrite the words that earned the position, at least not in the same month.

Move the images and keep the file names

Image search traffic is real, and file names carry it.

Test on a staging address first

Every form, every payment path, on a phone as well as a desktop. Then have somebody who does not work for you try to complete a booking.

Switch, then submit the new sitemap

Submit it in Search Console the same day and request indexing on the pages that matter most.

Watch for a fortnight

Search Console's coverage report will show you every URL that started returning a 404. A few always slip through; caught in week one they cost nothing, caught in month three they cost rankings.

Keep the old site until you are sure

Do not cancel the old hosting on switch day. Keep it, dormant, until the new site has been live and correct for a month.

What we do differently

We do not build on WordPress. The systems we build are written for the job they do, so there is no plugin between your guest and their booking, no yearly licence that can lapse, and no update that can take the site down on a Friday. You own the source code.

That is also why we can be specific during a migration: the redirect map, the forms and the payment path are our code rather than somebody else's, so when something is wrong we fix it rather than file an issue and wait.

If you want to know what your current site is running on before you decide anything, our free website check reports the platform, the PHP version and whether it is still supported.

Check what your site is running on

Questions we get asked

Will I lose my Google rankings if I move?+

Not if the URLs are mapped and redirected properly. Expect a small wobble for a week or two as search engines re-crawl, then a return to where you were. Sites that lose rankings permanently lost them to unredirected URLs, not to the move itself.

Can I keep my blog on WordPress and move the rest?+

Yes, and occasionally that is the right answer if you genuinely publish and your editors know the tool. It does mean maintaining two systems, so it is worth being honest about how often the blog is actually updated.

How long does a migration take?+

The redirect work and the content move are usually measured in days. The new site itself is the real timeline, and that depends on what it has to do. The migration is the last week of the project, not the project.

What happens to my email?+

Nothing, if it is handled as a separate decision. We check your existing mail records before any DNS change and leave them pointing where they already point unless you have asked us to move email too.

Want this looked at for your own business?

A short call, no charge, and a straight answer about what it would take.

Book a scoping call