Migrate from WordPress Without Losing Google Rankings

You can migrate from WordPress without losing rankings if you keep what Google already knows about your site: the URLs, the content that ranks and the technical signals. Anything that changes address gets a 301 redirect, one by one, and everything is measured before and after. The platform does not sink your traffic. Improvising the move does.

This is the guide we follow at Walaá, a software studio in Bogotá. If you have already decided to rebuild your site, this is how we approach web design from scratch, with technical SEO built into the code.

Quick facts about the web design service (taken from the service page, as of October 29, 2026):

Item	Detail
Timeline	Around eight weeks
Performance	95 or higher on mobile Lighthouse, measured before launch
Accessibility	WCAG AA level verified
SEO	Technical SEO included from the code
Design	From scratch, no templates
Support	Monthly support with reports

If your WordPress site already brings in visits and you want to move it with a written plan, tell us about your case on WhatsApp. The first conversation is free.

Will I lose rankings if I leave WordPress?

No, leaving WordPress does not cost you rankings by itself. Google ranks URLs and content, not the system the site was built with. Traffic is lost when addresses change without redirects, when pages that ranked disappear, or when the site launches with technical errors. If you avoid those three mistakes, the platform does not matter.

That does not mean the move is painless. It is normal for Search Console to show movement in the first few weeks, while Google crawls your pages again. No serious provider can promise zero variation. We prefer to measure before we claim anything.

Where traffic is lost when you redesign a website

It is almost always the same causes:

• URLs that change without a redirect, so visits and external links end up on a 404.
• Trimmed content because the redesign wanted to look clean, often the very texts that ranked.
• Titles, descriptions and headings that never get carried over. In WordPress they usually lived in an SEO plugin and stay there.
• The noindex from the staging environment that reaches production, or a robots.txt that blocks everything.
• A new site that is slower or less accessible than the old one.
• Sitemap and internal links that still point to the old addresses.

What is a URL map and what is it for in a migration?

A URL map is a table that lists every address on your current site and says which new address it corresponds to. It makes sure no page with traffic or links is left without a destination: the 301 redirects, the content review and the launch-day checklist all come from it.

You build it in a spreadsheet. You crawl the current site with a crawler, cross that list with the pages that get clicks in Search Console, and add the ones other sites link to. Each row ends with a decision.

Here is a sample map (illustrative addresses):

Current URL	What it is	New URL	Action
/servicios/diseno-web/	Page with traffic	/servicios/diseno-web	301
/2022/05/guia-seo/	Article with external links	/blog/guia-seo	301
/?p=123	WordPress short address	Final article URL	301
/categoria/sin-categoria/	Archive with no value	No equivalent	404 or 410

Pay attention to what WordPress generates on its own: date archives, tags, pagination, ?p= addresses and image attachment pages. Many do not deserve to survive, but it is better to decide that in writing than to discover it in an error report.

301 redirects in a migration: the rules that are not negotiable

A 301 redirect tells browsers and Google that a page has moved permanently. The Google Search Central documentation explains how the search engine treats them. In practice, these are the rules we apply:

• One to one. Each old URL goes to its closest equivalent. Sending everything to the home page is the fastest way to lose what you earned.
• No chains. The old URL points straight to the new one, not to an intermediate address that redirects again.
• Tested before launch. You run the full list from the map against the staging environment and check that each one returns a 301 and lands on a page with a 200 status code.
• No false promises. If a page has no equivalent, an honest 404 or 410 is better than a redirect to something unrelated.
• Internal links updated. The new site should link to itself using the final addresses, without relying on the redirect.

At Walaá, the URL map and the 301 redirects are part of the WordPress migration plan, not an extra for the last day. If you want to understand what else gets solved from the code, read our guide to technical SEO.

Moving from WordPress to another platform: what it must allow

It doesn’t matter which one you move to, but before choosing, check that the new platform lets you:

• Define the structure of every URL yourself, including the trailing slash.
• Set up 301 redirects in bulk.
• Edit title, description, headings and canonical tag per page.
• Generate a sitemap and structured data.
• Deliver the full content in the HTML, without depending on the browser running JavaScript to show the text.

If any of those points is not possible, the problem will show up late and cost more to fix.

Step by step to migrate without losing traffic

1. Inventory. Crawl the entire current site and export URLs, titles, descriptions, headings, canonicals and response codes.
2. Baseline. Export the performance data from Search Console (it keeps 16 months) and note the pages with the most clicks. Also measure the current site with Lighthouse, Google’s tool that scores speed, accessibility and best practices on a scale of 0 to 100.
3. URL map. One row per page, with its destination and its action.
4. Build in a staging environment, protected and set to noindex while the work is in progress.
5. Carry over the signals. Text, titles, descriptions, headings, structured data, image alt text and internal links.
6. Measure before launch. Mobile Lighthouse, Core Web Vitals and accessibility. Our standard is 95 or higher on mobile Lighthouse, measured before publishing.
7. Launch. Remove the noindex and any block in robots.txt, turn on the 301 redirects, publish the new sitemap and submit it to Search Console.
8. Monitoring. Check Search Console daily during the first week and fix whatever shows up.

Step 7 is where most people trip. A forgotten noindex is silent: the site looks perfect and Google receives the order to ignore it.

What do I check in Search Console after migrating?

Check four things: the page indexing report to see that the new URLs get in and the old ones drop out, the submitted sitemap with no errors, performance compared against your baseline, and the crawl stats to look for spikes in 404 or 5xx errors. Do it daily during the first week and then weekly.

How to read each report

• Page indexing. Old URLs showing up as pages with a redirect is expected. A URL from your map showing up as not found (404) is not.
• Sitemaps. It should appear as processed and include the new URLs. If the WordPress sitemap is still there, replace it.
• Performance. Compare periods of equal length and look page by page, not just at the total. That way you see which URL dropped and why.
• URL inspection. On your key pages, confirm that Google picks the new address as the canonical.
• Crawl stats. Look for server errors or sharp drops in requests.

All of this is done in Google Search Console, which is free and which you need to have verified before launch.

Who this plan is for and who it is not for

It is for you if you have a WordPress site that already brings in visits, inquiries or sales, and you want to rebuild it for speed, maintenance or control of the code without losing what you have already built.

It is not for you if your site barely gets any traffic: in that case it makes more sense to start fresh with a good structure than to invest in preserving what does not exist. Nor is it for you if your WordPress is only slow because of a couple of plugins or heavy images, because sometimes optimizing it is enough. If you are still comparing budgets, see how much a website costs in Colombia.

How we do it at Walaá

Our delivery process has six stages and a website takes around eight weeks. It starts with a written proposal covering scope, timeline and investment, and the URL map is built from the beginning. We measure before launch: on our own site we have mobile Lighthouse of 95 or higher and 0 violations in axe, the accessibility checker, at WCAG AA level. It is the same standard we apply to client sites. To understand what those metrics measure, the web.dev guide is the best reference.

After launch, monthly support with reports follows. If you also want someone to watch the results and publish content, there is monthly SEO positioning with a Search Console report.

If you want us to review your current site and tell you what to keep, what to redirect and what to leave behind, write to us on WhatsApp. We speak Spanish, English or German.

Written by Eduardo Obdulio, software engineer at Walaá. Updated October 29, 2026.