Start before WordPress permalinks are finalized
Record current Blogger behavior before changing DNS, custom-domain settings, themes, feeds, or destination permalinks. Combine a crawl with analytics landing pages, Search Console data where available, backlinks, campaign URLs, and existing redirect behavior.
Exact redirect control depends on the old hostname, custom-domain ownership, Blogger configuration, WordPress hosting, and the routing mechanism available at cutover. Confirm those controls before promising a URL pattern.
Inventory every URL family that can carry value
Include canonical post URLs, the original Blogspot hostname, custom-domain variants, year/month paths, standalone pages, archives, label pages, pagination, mobile ?m=1 variants, RSS and Atom feeds, FeedBurner addresses, media URLs, campaign parameters, priority backlinks, and organic landing pages.
Keep the full hostname, path, query behavior, status, canonical, indexability, traffic evidence, and intended owner. A list of titles cannot expose hostname, mobile, feed, or parameter variants.
Choose preserved paths or tested one-to-one redirects
Blogger commonly uses year/month post paths. WordPress can preserve a compatible structure or use a different permalink model, but make the choice before the final import and test real examples. Do not assume a plugin will infer every historical slug or custom-domain variant.
| Source | Decision | Validation |
|---|---|---|
| Canonical post | Preserve or 301 to its final post | One hop, 200 destination, self-canonical |
Mobile ?m=1 | Normalize without losing the post path | Same final canonical as desktop |
| Valuable label archive | Map to an equivalent taxonomy or approved replacement | Relevant destination, not the homepage |
| Removed page | Approved 404/410 when no replacement exists | No soft-404 or unrelated redirect |
| Feed URL | Separate feed destination rule | Valid feed and subscriber-path check |
Build an auditable redirect map
For every valuable source URL, record the final canonical destination, reason, implementation rule, owner, expected status, observed result, and exception. Use the redirect mapping worksheet.
Avoid homepage fallbacks, chains, loops, broad rules that overmatch, and accidental parameter loss. Update links you control so the new site points directly to final destinations.
Carry the signals redirects cannot replace
Review titles, descriptions, headings, canonicals, robots directives, structured data, social metadata, publication dates, visible authorship, image alt text, and internal links. Transfer or intentionally revise each field.
A redirect does not repair missing content, changed intent, broken images, weak metadata, inaccessible pages, or internal links that still depend on Blogger.
Plan feeds and subscribers separately
Inventory Blogger RSS and Atom endpoints, FeedBurner configuration, email tools, syndication consumers, and custom feed links. Browser redirects do not prove a feed reader accepts the new endpoint.
Subscriber records do not transfer automatically. Audience migration needs an approved destination, lawful data scope, consent handling, export path, and validation.
Validate staging and the production launch
Keep staging blocked from indexing while checking old URLs, destinations, canonicals, metadata, schema, internal links, images, mobile rendering, feeds, sitemap contents, robots rules, and analytics tags. Use the SEO migration checklist and SEO migration guide.
At launch, repeat tests against public DNS and normal HTTPS. Keep the Blogger source and custom-domain control until acceptance and rollback conditions pass.
Monitor after cutover
Monitor errors, redirect hits, chains, sitemap processing, indexation, landing traffic, queries, feeds, conversions, and performance. Compare changes with the baseline and investigate affected URL groups.
No migration can guarantee preserved rankings or traffic. The goal is to control avoidable technical loss, detect exceptions quickly, and retain evidence for correction.
Connect SEO controls to migration scope
Use the Blogger import guide for content and assets, the comparison for ownership decisions, and the cost guide for estimate inputs.
Review current Blogger to WordPress compatibility, then create an account to analyze destination readiness, URL rules, exceptions, validation, and cutover requirements.