Moving off WordPress without losing your rankings

1. Decide whether moving is worth it

Owners usually leave WordPress for four reasons:

• Speed. Heavy themes and page builders load a lot of code. Simpler sites often load much faster on phones.
• Plugin upkeep. Every plugin needs updates, and one plugin's update can break another.
• Security updates. WordPress, themes and plugins all need patching. A site no one updates becomes an easy target.
• Cost. Paid themes, premium plugins, managed hosting and security add-ons add up every year.

Moving is not always the right call. Stay on WordPress, or get help first, if:

• Your site runs an online store, memberships, courses or a booking system built into WordPress. Those take real rebuilding.
• Several people publish to it every week and like the editor.
• Your site is fast, updated and ranking well. "It's WordPress" is not a reason by itself.
• You can't commit a weekend now and a few check-ins over the next month.

2. Crawl and export every URL and all your content

You can't protect pages you don't know exist. Build a full list from three places:

1. Your sitemap. Visit yoursite.com/sitemap.xml or yoursite.com/sitemap_index.xml. SEO plugins split it into posts, pages, categories and more. Open each one.
2. A crawler. The free version of the Screaming Frog SEO Spider crawls up to 500 URLs, which covers most small business sites. It finds pages your sitemap missed, plus every image, title and meta description.
3. Search Console. In Performance, open the Pages tab and export it. This shows pages that get searches, including old ones you forgot about.

Put every URL in one spreadsheet column. Remove duplicates. This list is the backbone of the whole move.

Then export your content. In WordPress, go to Tools → Export and choose All content. You get an XML file with your posts, pages, categories, tags and more. That file points to your images but may not contain them, so download your media folder separately. Your host's file manager or a backup plugin can do it.

3. Save your Search Console baseline

After launch you'll want to know whether anything dropped. You can only tell if you saved a "before" picture.

• In Performance, set the date range as wide as it goes. Export the Queries and Pages tabs.
• Write down total clicks and impressions for the last three months.
• In Indexing → Pages, note how many pages are indexed.
• Mark your top 20 pages by clicks. These get extra care in every step below.

If you're new to Search Console, start with the Search Console checkup guide.

4. Keep the same URLs wherever you can

Google ranks addresses. If /back-pain-oakland/ ranks today, the safest plan is for that exact address to still work tomorrow, with the same content on it.

Watch the small details. They count as different addresses:

• Trailing slashes. WordPress URLs usually end in a slash, like /about/. Many new platforms use /about or /about.html. Match the old pattern, or redirect.
• Blog paths. If posts lived at /2019/04/post-name/, keep that path. Don't tidy it to /blog/post-name/ unless you redirect every one.
• Category and tag pages. Check your crawl. If any get traffic, keep or redirect them.

5. Map and set up 301 redirects for every URL that changes

Some addresses will change. You might merge thin pages or drop an old service. For each one, send visitors and Google to the closest new page with a permanent redirect.

1. In your spreadsheet, add a second column: new URL. Fill it in for every row. If the address stays the same, copy it across.
2. For removed pages, point to the closest related page, not the homepage.
3. Add the redirects on your new host. Most hosts use a redirect file or a redirects screen in settings.
4. Use a 301 or 308. Google recommends server-side permanent redirects for moves. Avoid meta refresh or JavaScript redirects when a server redirect is possible.
5. Avoid chains. Old URL should go straight to the final URL in one hop. Google advises keeping chains short.

Keep redirects as long as you can. Google says at least one year, and suggests keeping them indefinitely for visitors. For a small business, just never remove them.

6. Carry over titles, descriptions, headings and internal links

The words on the page are only part of what ranks. Copy these over exactly, page by page:

• Title tag. Your SEO plugin may have set a custom title that differs from the page heading. Use the crawl export, not what you see on screen.
• Meta description. Same rule. Copy it from the crawl.
• Headings. Keep the main heading and subheadings. New templates often turn headings into styled text by accident.
• Internal links. Update links in your content to the final addresses, so they don't pass through redirects.
• Canonical tags. Each page should point to its own new address.

Want to improve pages while you're in there? Fine, but do it after launch. Change one thing at a time so you can tell what helped. The service pages guide covers what to improve.

7. Carry over schema, images and alt text

Schema

Schema is hidden code that tells search engines and AI tools what a page is about. Plugins like Yoast or Rank Math add it for you. When the plugin goes, the schema goes too.

• Rebuild your LocalBusiness schema with your exact name, address, phone and hours.
• Add Article schema with an author on blog posts, and FAQ markup where you have real FAQs.
• Run a few pages through a structured data testing tool before and after launch, and compare.

Images and alt text

• Upload every image you still use. Compress large ones; this is where much of the speed gain comes from.
• Copy alt text from the crawl export. Write it for images that never had any.
• If image addresses change and images got search traffic, redirect them too.

8. Reconnect forms, analytics and Search Console verification

These break quietly. Nobody notices until leads stop.

• Forms. Rebuild every contact and booking form. Send a test from each one and confirm it arrives.
• Google Analytics 4. Add your GA4 tag to every page of the new site. Check the Realtime report while you click around.
• Search Console verification. If you verified with an HTML file or a meta tag, the new site needs it too. Google rechecks, and removing the token can cost you verification. A Domain property verified through DNS doesn't depend on the site.
• Other tags. Ad pixels, call tracking and chat widgets all need adding back.

9. Set up robots.txt and your new sitemap

• robots.txt. Make sure it doesn't block everything. While building, many platforms hide the new site from search. Turn that off at launch.
• noindex tags. View the source of a few pages. Look for noindex. It should not be there on live pages.
• Sitemap. Your new sitemap should list only the final URLs, not the old ones that now redirect.

10. Watch the first 30 days

Google warns that rankings can wobble during a move. For small and medium sites, it can take a few weeks for most pages to switch over. Don't panic at a dip in week one.

• Indexing → Pages. Look for "Not found (404)." Each one is an old URL you missed. Add a redirect, then click Validate fix. "Page with redirect" is normal for old addresses.
• Performance. Compare clicks and impressions to your baseline. Look at your top 20 pages one by one.
• Sitemaps. Resubmit after any fixes. The discovered page count should match your new site.
• Bing. Submit the new sitemap in Bing Webmaster Tools too. See getting indexed for setup.

If a top page drops and stays down past a few weeks, compare old and new side by side. The cause is usually a missing title, a lost section of text or a broken internal link.

11. Use Change of Address only when the domain changes

Search Console has a Change of Address tool. It is only for moving from one domain or subdomain to another, like oldname.com to newname.com.

• Don't use it if you keep the same domain and only change platforms.
• Don't use it for a move from http to https, or between www and non-www.
• If you do change domains, set up redirects first. You must own both properties in Search Console with the same Google account.

Changing platform and domain at the same time doubles the risk. If you can, do one, let it settle, then do the other.