Choose the source path for each record
The public Blogger API can support discovery of published posts and related public records from an accessible blog. It does not prove access to drafts, private or deleted content, standalone pages, or every media file.
A Blogger backup provides an XML control artifact and can support WordPress importer workflows. The WordPress importer can create supported destination records, but a successful import message is not proof of complete migration. Compare the public site, backup, importer result, and agreed scope before accepting the result.
Blogger to WordPress transferability matrix
| Source item | Typical WordPress result | Required control |
|---|---|---|
| Published posts | Posts or an approved custom post type | Preserve source identity, HTML, dates, status, and source URL |
| Authors | WordPress users or approved bylines | Map visible identity; Google credentials and permissions do not transfer |
| Labels | Categories, tags, or another taxonomy | Approve one taxonomy strategy before loading |
| Comments | WordPress comments | Load after posts and resolve destination parent IDs |
| Inline images | Media Library files and rewritten body references | Discover, download, validate, upload, and verify rendering |
| Embeds | Supported embeds or destination-native blocks | Test provider support, privacy, and rendered behavior |
| Standalone pages | WordPress pages | Separate access and mapping review; not covered by the current public API path |
| Draft or private content | Approved editorial states | Requires an authorized non-public source path |
| Themes and widgets | Theme, blocks, plugins, or custom implementation | Rebuild separately from content import |
| Feeds and subscribers | WordPress feeds or an external email platform | Plan feed destinations; subscribers require separate consent and data scope |
1. Create a backup and crawl the live blog
Create a Blogger backup before making changes and retain it as a dated source artifact. Record the blog URL, custom domain, account owner, export time, approximate counts, and any warnings.
Crawl the accessible live blog as a separate baseline. Capture published posts, pages, labels, authors, comments, images, embeds, status codes, titles, descriptions, canonicals, headings, internal links, and feeds. The crawl can reveal public dependencies that the XML or API path does not represent cleanly.
2. Build the complete URL inventory
Collect canonical post URLs, the original Blogspot hostname, connected custom-domain routes, year/month paths, standalone pages, archives, label pages, mobile variants, feeds, pagination, campaign URLs, and priority inbound links.
Give every valuable source URL an intended outcome: retain, redirect, consolidate, or intentionally remove. Use the redirect mapping worksheet and preserve this inventory through launch validation.
3. Prepare WordPress before importing
Prepare staging WordPress with the approved post types, authors, roles, categories, tags, comment rules, media settings, permalink structure, SEO fields, templates, upload limits, and authenticated write access.
Choose the destination model before the full load. Changing permalinks, taxonomy, author ownership, or SEO storage after import creates another mapping and validation cycle. Keep staging blocked from public indexing while authorized testing continues.
4. Define repeatable mapping rules
Preserve Blogger source IDs and URLs so reruns resolve the same destination records. Map title, body HTML, publication and update dates, status, visible authors, labels, comment parentage, image URLs, and original paths deliberately.
Record normalizations, defaults, exclusions, and exceptions in the content mapping worksheet. Mapping rules should produce the same result in a dry run and final run instead of relying on manual corrections.
5. Import representative posts and comments first
Test old and recent posts, multiple authors, several labels, long discussions, nested replies where present, complex HTML, inline images, embeds, missing assets, custom-domain URLs, and unusual characters before full volume.
Load posts before dependent comments, resolve every parent to its destination ID, and keep failed or skipped records visible. A small dry run should expose systematic mapping problems while they are still inexpensive to correct.
6. Move inline files and rewrite references
Blogger content can reference images and files hosted on Google or another external service without exposing a complete attachment catalog. Parse post bodies to discover inline files and embeds.
For each in-scope asset, download it, validate its response and file type, upload it to the approved WordPress media location, and rewrite the content reference. Record inaccessible, duplicate, malformed, unsupported, or intentionally external items as exceptions.
7. Reconcile, validate, and cut over
Compare source, loaded, skipped, failed, and unresolved totals for posts, authors, labels, comments, and media. Inspect dates, chronology, authorship, taxonomy, comment parentage, HTML, images, embeds, mobile rendering, metadata, canonicals, internal links, redirects, feeds, and analytics.
Use the migration validation guide for reconciliation and representative checks. Resolve systematic failures, repeat the dry run where necessary, then run an approved final or delta transfer with documented acceptance and rollback conditions.
8. Keep the source available through acceptance
Do not delete the Blogger publication, release the custom domain, or remove source access immediately after import. Keep the source and backup available until destination reconciliation, URL checks, rendering, feeds, analytics, and rollback conditions pass.
Google Account credentials and Blogger permissions do not transfer to WordPress. Revoke temporary migration access only after the final run, evidence review, exception decisions, and agreed retention steps are complete.
Turn the inventory into a migration scope
Review the balanced Blogger vs WordPress comparison, current Blogger migration compatibility, Blogger redirect and SEO controls, broader SEO migration guidance, and Blogger migration cost factors.
Create an account and select Blogger and WordPress to analyze supported public content, destination readiness, mappings, exceptions, validation, and cutover requirements without sending credentials through a public form.