Moving blog posts from one WordPress site to another is easy. Moving them without losing the rankings, traffic, and links those posts have already earned requires a little more planning.
The biggest risk is not the WordPress import itself. It is changing URLs, losing SEO metadata, breaking internal links, or accidentally preventing Google from indexing the new version.
If your posts already receive organic traffic, treat the migration as an SEO move first and a WordPress task second.
Quick Answer
To move WordPress blog posts without losing rankings, map your existing URLs before the migration, keep the same slugs wherever possible, export and import the posts, preserve their SEO metadata and content, and use permanent 301 redirects for every URL that changes. After launch, update internal links, check canonicals and indexing settings, submit the new sitemap in Google Search Console, and monitor the migrated URLs.
Google recommends creating a URL map before a site move and using permanent redirects when URLs change. It also warns against changing several major things at the same time because that makes migration problems harder to diagnose.
First, Are Your Blog URLs Actually Changing?
This determines how complicated the migration needs to be.
| What is changing? | SEO risk |
|---|---|
| New WordPress install, same domain and URLs | Lower |
| New design, same posts and URLs | Lower |
| Blog folder or permalink structure changes | Higher |
| Posts move to a different domain | Higher |
| Posts are merged, renamed, or removed | Higher |
For example, suppose your current post is:
example.com/blog/wordpress-speed-guide/ and it remains exactly the same after the move. There is no new URL for Google to learn, so you normally do not need a redirect for that page.
But if the destination becomes:
newsite.com/wordpress-speed-guide/ the page has permanently moved. The old URL should redirect directly to the new one.
Google says permanent redirects such as 301s are an appropriate signal when a page has permanently moved, and permanent redirects do not cause a loss of PageRank by themselves.
If you can keep a ranking URL unchanged, keep it unchanged.
A migration is not the best time to rename every old slug simply because the new URLs look cleaner.
Make a URL Map Before You Move Anything
Before opening the WordPress exporter, make a simple spreadsheet.
You only need a few columns:
| Old URL | New URL | Redirect Needed? | Checked |
|---|---|---|---|
| Old Post A | New Post A | No | ☐ |
| Old Post B | New Post B | Yes | ☐ |
| Old Post C | New Post C | Yes | ☐ |
Export or crawl all of your existing blog URLs and decide where each one will live on the new site.
Pay extra attention to posts that:
- already receive organic traffic
- rank for valuable keywords
- have external backlinks
- generate leads or sales
- receive a lot of internal links
Those are the URLs you have the most to lose by breaking.
This URL mapping step is also part of Google’s recommended site-migration process.
Export Your Existing WordPress Posts
For a standard WordPress-to-WordPress move, WordPress already includes an export tool.
On the old website, go to:
Tools → Export → Posts
You can export all posts or filter them by:
- category
- author
- date
- post status
WordPress creates a WXR/XML export file containing the selected content. The native export can include posts and associated data such as categories, tags, comments, custom fields, and authors.
However, do not treat that XML file as a complete website backup. WordPress specifically notes that an export is for transferring content; it is not the same as backing up your entire website.
Import the Posts Into the New WordPress Site
On your new WordPress installation, go to:
Tools → Import → WordPress
Install the WordPress Importer if prompted, upload your export file, and map the authors to the appropriate users.
WordPress supports importing content from another WordPress installation through this process.
After the import finishes, do not assume the migration is complete.
Open a sample of posts and check them manually.
Make sure:
- headings are correct
- images appear
- featured images are assigned
- categories are correct
- author information transferred
- links still work
- formatting did not break
If you use custom fields, an SEO plugin, a page builder, or custom post functionality, check those separately. A normal WordPress export does not necessarily recreate every plugin or theme configuration on the destination site.
Preserve What Is Already Helping the Posts Rank
This is where many otherwise successful WordPress migrations go wrong.
The article moves, but important SEO elements do not.
For every valuable migrated post, compare the old version with the new one.
Check:
- URL slug
- SEO title
- meta description
- H1
- heading structure
- main content
- canonical URL
- image alt text
- internal links
- structured data
- author information
- featured image
If a post currently ranks well, avoid rewriting half of it during the migration unless there is a strong reason.
You already have enough variables changing.
Google itself recommends changing major site elements one at a time where possible. For example, if you are changing a domain, CMS, and layout, separating those changes makes problems easier to identify.
The same principle applies here:
Move first. Confirm stability. Improve the content afterward.
If you are also redesigning the site, Survyc guide on redesigning a website without losing SEO rankings covers the wider process of protecting ranking pages during a rebuild.
Add 301 Redirects for Every URL That Changed
If an old post URL no longer exists at the same address, redirect it.
For example:
Old:oldsite.com/wordpress-security/
New:newsite.com/wordpress-security-guide/
The old URL should permanently redirect to that specific replacement.
Do not redirect every old blog post to your homepage.
Google specifically advises against sending many old URLs to one irrelevant destination because it can confuse users and may be treated like a soft 404.
A good migration follows this rule:
Every valuable old URL should either continue to exist or redirect directly to its closest relevant replacement.
Also avoid unnecessary redirect chains.
Bad:
Old URL → Temporary URL → New URL
Better:
Old URL → New URL
For a true domain migration, Google recommends keeping redirects in place for at least one year, and from a user perspective it can make sense to retain them even longer.
Update Your Internal Links
Redirects protect old URLs, but they should not become your permanent internal linking system.
Suppose an old post contains a link to:
oldsite.com/wordpress-speed/
That URL now redirects to:
newsite.com/wordpress-speed/
The redirect works, but the migrated article should link directly to the new URL instead.
Check links:
- between blog posts
- from posts to service pages
- from pages back to blogs
- inside buttons
- inside navigation
- inside images where applicable
Google recommends updating internal links to point directly to the new URLs after a site move.
Doing this also reduces unnecessary redirect hops.
Check Your Images Too
A post can look successfully migrated while its images are still loading from the old domain.
Check several articles and inspect:
- inline images
- featured images
- image URLs
- alt text
- captions
- downloadable files
If the old site is eventually removed and your images were never actually copied, previously working posts can suddenly become full of broken images.
WordPress’s export format can contain attachment information, but WordPress also notes that the WXR export itself does not contain the actual attachment files.
This is why media deserves a separate check.
Run This Checklist Before Launch
Before making the migration final, confirm:
☐ Every old blog URL has been mapped
☐ Ranking URLs have been preserved wherever possible
☐ Required 301 redirects are working
☐ Posts imported correctly
☐ SEO titles and descriptions remain intact
☐ Canonicals point to the correct live URLs
☐ Internal links use the new URLs
☐ Images and featured images load correctly
☐ No important pages contain noindex
☐ robots.txt does not block the blog
☐ XML sitemap contains the correct URLs
☐ HTTPS works properly
☐ Google Search Console is configured
☐ Analytics and conversion tracking are working
☐ Old URLs have been tested for redirects and 404s
The noindex check deserves special attention.
Staging WordPress websites are often deliberately hidden from search engines. If that setting makes it to production, the migration can appear technically perfect while Google is being told not to index the new posts.
If that happens, use Survyc guide to fix WordPress page indexing issues to check WordPress visibility settings, SEO plugins, robots.txt, canonicals, and Search Console statuses.
What to Do Immediately After the Migration
The job is not finished when the new site goes live.
1. Crawl the New Site
Run a crawl and look for:
- 404 errors
- broken internal links
- redirect chains
- incorrect canonicals
- missing title tags
- accidentally blocked pages
If the migration itself produces WordPress errors, Survyc also has a guide covering common WordPress errors and how to fix them.
2. Submit the New Sitemap
Submit the current XML sitemap through Google Search Console so Google can discover the destination URLs.
Google specifically recommends submitting the new sitemap as part of a site move.
3. Use Change of Address if the Domain Changed
If you moved from one domain or subdomain to another, use Google’s Change of Address process in Search Console after the redirects are working.
You do not need Change of Address merely because individual paths changed on the same domain.
4. Monitor the Important Posts
Watch:
- Google Search Console clicks
- impressions
- indexed pages
- 404 errors
- redirect problems
- organic landing-page traffic
Some ranking fluctuation can happen while Google recrawls and processes changed URLs. Google notes that a small or medium-sized site move can take several weeks for most URLs to settle.
That is different from an immediate collapse caused by a technical mistake.
The Most Common WordPress Blog Migration Mistakes
| Mistake | Better approach |
|---|---|
| Changing every slug | Preserve existing URLs where possible |
| Importing posts and forgetting SEO | Compare metadata and canonicals |
| No redirects | 301 every permanently changed URL |
| Redirecting everything to the homepage | Redirect one-to-one to relevant pages |
| Rewriting every post during migration | Move first, optimize later |
| Forgetting images | Verify media on the destination site |
Leaving staging noindex active | Check indexability before launch |
| Keeping old URLs in internal links | Update links to final destinations |
| Deleting the old domain immediately | Keep it available to serve redirects |
Frequently Asked Questions
Will moving WordPress posts hurt my Google rankings?
Not necessarily. The risk is much lower when URLs, content, metadata, internal links, and other important signals remain consistent. Risk increases when you change the domain, URL structure, design, and content at the same time.
Google also warns that temporary ranking fluctuations can occur while migrated URLs are recrawled and reindexed.
Should I keep the same URLs when moving WordPress blog posts?
Yes, when practical.
If an existing URL already ranks or has backlinks, preserving it eliminates the need for Google and users to learn a different address.
When a URL genuinely needs to change, use a permanent redirect to its new equivalent.
How long should I keep 301 redirects after a migration?
Google recommends keeping site-move redirects for at least one year so its systems have enough time to transfer signals from old URLs to new ones. Keeping important redirects longer is often useful for visitors and old backlinks too.
Should I delete the old WordPress site immediately?
Not until you have confirmed that the content, images, redirects, indexing, analytics, and important URLs are working correctly.
If you moved to a different domain, the old domain must also remain available for its redirects to continue working.
The Bottom Line
Moving WordPress posts is not difficult.
Protecting what those posts have already earned is the part that deserves attention.
The safest process is:
Map the URLs → preserve what already works → move the posts → redirect changed URLs → update internal links → test everything → launch → monitor Search Console.
If the same URLs and content can remain intact, do not create unnecessary changes.
And if URLs must change, make the relationship between every old page and its new destination completely clear to both visitors and Google. That is how you move your WordPress blog without turning a straightforward migration into an SEO recovery project.
