Moving a blog to a new publishing platform is more than exporting posts and importing them elsewhere. This blog platform migration checklist helps you protect search visibility, preserve reader pathways, and verify the details that are easy to miss, from URL redirects and images to metadata, analytics, feeds, authorship, comments, and backups.
Overview
A platform migration changes the system that stores and delivers your content. Depending on the project, it may also change your domain, URL structure, templates, image locations, navigation, structured data, RSS feed, or tracking setup. Each change can create a broken link, missing asset, duplicate page, or search signal that needs attention.
The safest approach is to treat the move as a documented comparison between the old site and the new one. Before making changes, capture what exists. During the migration, map each important old URL to its intended new destination. After launch, test the new site and monitor whether visitors and search engines can still reach the content.
This process applies whether you are moving a WordPress blog, changing from one hosted platform to another, or rebuilding a publication on a different content management system. The exact export and redirect screens will vary, so confirm the current instructions for both platforms before starting. The underlying checks remain broadly the same.
Migration goals to agree on first
- Keep the same domain, change only the platform, or move both domain and platform.
- Preserve existing post URLs where practical, rather than changing every address at once.
- Retain useful content, media, authorship, categories, tags, and publishing dates.
- Maintain measurement, subscriptions, feeds, and links from other websites.
- Record decisions so the team can distinguish intentional changes from migration errors.
What to track
Create a migration workbook before exporting anything. A spreadsheet is sufficient. Use one row per important page and add columns for the old URL, new URL, page type, redirect status, title, canonical URL, image status, owner, test result, and notes.
1. Content and export completeness
Record the number of published posts, pages, media files, authors, categories, tags, comments, and other content types on the old platform. The count is not a quality judgment; it is a reconciliation tool. After importing, compare the old and new totals and investigate unexpected differences.
Open a sample of content rather than relying only on totals. Include a recent post, an older post, a post with images, a post with embeds, a category or tag archive, and any high-value evergreen page. Check headings, paragraphs, lists, links, formatting, captions, downloads, and embedded media.
2. URL mapping and redirects
URL mapping is the central document in a blog migration SEO checklist. For every valuable old address, specify the exact new address it should serve. If a post has no direct replacement, decide whether it should remain available, point to a closely related page, or return an appropriate not-found response.
A simple mapping template looks like this:
| Old URL | New URL | Page type | Redirect tested | Notes |
|---|---|---|---|---|
| /old-post/ | /new-post/ | Blog post | Pending | Preserve title and images |
| /category/interviews/ | /topics/interviews/ | Archive | Pending | Confirm archive is indexable |
Use a permanent redirect for a permanent URL change, and test the complete path from the old address to the final page. Avoid redirect chains, loops, and sending many unrelated pages to the home page. A redirect should lead visitors to the most relevant equivalent destination.
3. Metadata and on-page SEO
Compare page titles, meta descriptions, canonical URLs, heading structure, indexation settings, open graph fields, and structured data where relevant. Confirm that imported posts have not inherited a temporary noindex setting from a staging site. Check that the new platform does not automatically append unnecessary text to titles or generate duplicate archive pages.
Use the on-page SEO checklist for blog posts to review priority pages before launch. For posts being rewritten during the move, a blog post outline template can help separate migration corrections from editorial changes.
4. Images, files, and embeds
Check that images load at their intended sizes, retain useful alternative text, and use stable new file paths. Test featured images, inline images, galleries, downloadable files, video embeds, audio players, and social embeds. Look for references to the old domain in image URLs, CSS, JavaScript, canonical tags, and downloadable assets.
Do not assume that an image import preserves every field. Compare a representative sample manually, especially for posts where the image carries context or accessibility information.
5. People, comments, feeds, and analytics
Confirm that author names, author pages, publication dates, bylines, and contributor links migrated correctly. Decide how comments will be transferred, displayed, closed, or archived. If comments are important to the publication, test both existing threads and new submissions.
Check the RSS or Atom feed, email subscription connection, sitemap location, analytics property, consent settings where applicable, and search verification. Open the site in a private browser session and confirm that a page view, outbound click, and subscription action are recorded as intended. Keep a copy of the old analytics configuration before replacing it.
6. Internal links and navigation
Scan for links that still point to the old domain, staging host, HTTP version, or outdated URL pattern. Review menus, footer links, related-post modules, breadcrumbs, author pages, category pages, and calls to action. Pay particular attention to older posts that may not be included in a modern navigation system.
If the move exposes outdated or overlapping articles, document them rather than deleting them impulsively. A content audit template for bloggers can help classify pages as keep, update, merge, redirect, or remove.
7. Backups and rollback
Keep an export of the original content, a database or platform backup when available, the media library, the URL map, theme or template files, and key configuration details. Store copies separately from the live platform. Define who can pause the launch or restore the previous version if a serious issue appears.
Cadence and checkpoints
Use three checkpoints instead of treating migration as one launch-day task.
Before the move
- Freeze the inventory date and export current URLs, metadata, media, and analytics settings.
- Identify priority pages using visits, links, subscriptions, conversions, or editorial importance.
- Build and review the old-to-new URL map.
- Test the new platform on a private or staging address.
- Record the old sitemap, feed URL, robots settings, navigation, and tracking configuration.
At launch
- Confirm the intended domain and preferred protocol are live.
- Apply redirects before announcing the move.
- Check representative posts, pages, archives, images, files, forms, and feeds.
- Verify titles, canonicals, indexation controls, analytics, and search verification.
- Submit or otherwise expose the current sitemap using the platform's supported workflow.
After launch
Run a focused check on the first day, then repeat it after several days and again during the first few weeks. Track redirect errors, not-found responses, crawl or indexing warnings, analytics continuity, feed delivery, top landing pages, and important conversion paths. A quarterly review is useful after the migration settles, especially if the new platform changes templates or URL rules.
How to interpret changes
Not every change in traffic means the migration failed. Compare like with like: the same pages, dates, channels, and tracking definitions. Separate technical signals from editorial changes, seasonality, promotion, algorithmic shifts, and normal audience variation.
| Signal | Likely area to inspect | First response |
|---|---|---|
| Many old URLs return not found responses | Redirect rules or URL map | Test priority URLs and add precise redirects |
| Pages load but images are missing | Media paths, permissions, or import | Check file URLs and restore missing assets |
| Titles or descriptions changed unexpectedly | Template defaults or metadata import | Compare priority pages with the pre-migration export |
| Traffic appears to stop recording | Analytics configuration | Test tracking on several page types and devices |
| Readers cannot find older content | Navigation, search, or archive settings | Review menus, internal links, and archive visibility |
| Search visibility changes on selected pages | Canonical, indexation, content, or redirects | Inspect affected URLs individually before making broad changes |
Look for patterns. A problem affecting one post may be an import error; the same problem affecting every post type is more likely to come from a template, setting, or redirect rule. Keep a dated change log so you can connect a symptom to a specific release or configuration change.
When to revisit
Revisit this checklist whenever the domain, URL structure, publishing platform, theme, analytics setup, or media storage changes. It is also worth reviewing on a monthly basis during the first few months after launch, then quarterly as part of routine site maintenance.
Refresh the platform-specific portions when either system changes its export tools, redirect controls, sitemap behavior, editor, or analytics integrations. The strategic checklist can remain stable, but the button names, settings, and technical terminology may not. Mark those details with the date they were last verified.
For a practical closeout, schedule these actions:
- Export the current URL list and compare it with the migration workbook.
- Test a rotating sample of old URLs, priority posts, archives, images, feeds, and forms.
- Review new errors and classify each as a redirect, content, metadata, media, tracking, or navigation issue.
- Update the workbook with the fix, date, owner, and retest result.
- Save a fresh backup and record any platform-specific instructions that changed.
A successful move is not defined only by a new design or a completed import. It is a controlled handoff in which readers can still reach useful content, search engines can understand the new addresses, and your team can prove what changed. Keep the URL map and verification log after launch; they will make the next platform comparison, domain change, or redesign far easier to manage.