How to remove WordPress without losing your Google rankings

For a day, wecreative.site had two websites at once. The one you saw, and another one underneath: a WordPress install that published nothing and still answered anyone who knew where to knock.

We took it out the next day. Here is the whole process, because the part that scares people, losing rankings, is settled by measuring and not by guessing.

An install nobody uses is not switched off

The problem with a CMS you stop using is not the disk space. It is that it keeps working.

Before touching anything we measured what still responded. The login screen served a full page and the admin area answered whoever asked for it. Nobody was going to update that WordPress, nobody was going to read its logs, and nobody would have noticed if someone got in.

Google penalises and can deindex compromised sites. So the forgotten install was not a tidiness matter: it was a serious and avoidable risk.

What we measured before deleting

The scary question is whether removing the CMS drops your rankings. That gets measured, not argued.

We checked three things:

That made the picture clear: the SEO effect, if any, had already happened when the new site went live. Removing the files changed nothing that Google sees.

• Whether any page of the new site depended on files from the old one. None did: zero references, in the files and in the published pages.
• What the WordPress URL patterns returned, the likes of /2025/01/ or /category/something/. They already returned errors before we deleted anything, because the new site had been on top of it for a day.
• Whether the sitemap pointed at any image from the old CMS. None of the 46 URLs did.

The only thing that really changed

Two things, and only one of them mattered.

The login screen stopped existing, which is an improvement: it is a page you do not want in anyone's index.

And the images inside the CMS folder stopped being found. That was the only real risk, because if one were indexed in Google Images or linked from another site, it would be lost. So the deletion went in two phases: the engine first, which carries no risk, and the images afterwards, with the decision made deliberately.

What if this is your case?

If you have a new site and the old CMS still sits underneath, the short answer is yes, take it out. But not bluntly.

Before deleting, check that no new page uses files from the old one, look at what the old URLs return today, and decide separately what to do with the images. And do it from a written list, not by picking files in a browser: the list reorders itself between looking and clicking, and that is where the wrong thing gets deleted.

Do you do this on client sites?

Yes, and that is why we did ours first.

When we migrate a site, the previous CMS is retired with the same procedure: measure what depends on what, check what responds today, separate what carries no risk from what does, and verify from the outside that the site is still standing when it is done. You can see projects we have built this way, and if what you are weighing is the budget, we break it down in what a small business website costs.

If this is your problem

If your new site still has the old CMS underneath and you are not sure what can be deleted without breaking anything, write to us and we will review it: we will tell you what is there, what can be retired and what is worth keeping.