WordPress hosting for blogs moving off Blogger.
A long-running Blogger site has years of ranking URLs ending in .html, a duplicate mobile address for every one of them, and an export format WordPress does not read natively.
What a decade on Blogger leaves you holding.
The posts import without much drama. The addresses they live at are the part worth being careful with.
Addresses that end in .html
Blogger uses /YYYY/MM/post-title.html. WordPress can reproduce that exactly, which for a site with long-standing rankings is usually better than redirecting every post.
A mobile copy of every page
Blogger serves a separate ?m=1 address for mobile visitors, and those get indexed. They need resolving to the canonical page rather than being left to compete with it.
An Atom export, not WXR
Blogger produces an Atom XML file. The WordPress importer expects its own format, so the export is translated rather than uploaded straight into the importer.
Labels that become categories
Blogger has one flat labelling system doing the job of both categories and tags, so how it splits across the two is a decision made before the import rather than tidied up afterwards.
Comments worth keeping
Comments live in Blogger's own system, and where a third-party commenting service was added on top, the two sets have to be reconciled rather than one silently winning.
Keep the addresses that earned the traffic.
For most Blogger sites the archive is the asset. A move that changes every URL trades years of accumulated ranking for a tidier permalink structure, which is rarely the trade anyone wanted.
- Permalink structure matched to the existing .html addresses
- ?m=1 mobile URLs canonicalised
- Labels split into categories and tags with you
- Blogger site left published until you confirm
An archive that stays fast as it grows.
Blogger never slowed down because Google ran it. The risk in moving is inheriting a thousand-post archive on hosting that was sized for a brochure.
What this move needs that a host migration does not
Blogger is a hosted product with its own URL conventions, and those conventions are the substance of the migration.
| Setting | What we do | Why |
|---|---|---|
| Permalink structure | WordPress configured to reproduce /YYYY/MM/post.html exactly | Blogger addresses end in .html, and a site with a long ranking history usually loses more from redirecting every post than it gains from a cleaner permalink format. |
| Mobile URLs | ?m=1 addresses canonicalised to the main page | Blogger serves a separate mobile address for every post and search engines index both, so after a move the duplicate keeps appearing unless it is pointed at the canonical page. |
| Export translation | Atom XML converted into a format the importer accepts | Blogger exports Atom rather than WordPress WXR, so the file will not go into the standard importer without being translated first. |
| Labels | Split into categories and tags as a deliberate choice | Blogger has a single flat labelling system covering both roles, so an unguided import puts everything in one taxonomy and loses whatever structure the labels implied. |
| Comment history | Blogger comments imported and reconciled with any third-party system | Older blogs frequently added an external commenting service on top of Blogger's own, leaving two separate sets that will otherwise not both survive. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Can I keep my .html URLs after moving to WordPress?
What are the ?m=1 URLs in my search results?
Will the WordPress importer take my Blogger export?
How do Blogger labels map to WordPress?
Do my Blogger comments come across?
Own the blog without losing the archive.
Free migration, .html addresses preserved, and the mobile duplicates cleaned up.