Blogger to WordPress Migration: Fixing Mobile Redirects

If you migrated from Blogger to WordPress and set up redirects from your old Blogger URLs to their new WordPress equivalents, you may find the redirects work fine on desktop but fail specifically on mobile browsers like Safari on iPhone.

Cause

Blogger serves a separate mobile template independently of your main template, and that mobile template can keep loading the old Blogger site directly instead of respecting your redirect, even after your main (desktop) template has been switched over correctly.

The Fix

1. Log back into Blogger and open your old blog.
2. Go to Theme (or Template, depending on your Blogger version).
3. Find the mobile template settings — there’s a small cog/gear icon specifically for the mobile template.
4. Click it and select the option to disable the separate mobile template.
5. Save your changes.

Once the mobile-specific template is disabled, mobile visitors fall through to the same template (and therefore the same redirect) as desktop visitors. Test by visiting your old Blogger URL directly on an iPhone or Android browser and confirming it now redirects to your new WordPress site correctly.

Does This Still Apply in 2026?

It depends entirely on which Blogger theme family the old blog is running. If it’s still on one of Blogger’s older “Designer” era themes (the classic Simple/Awesome Inc./Watermark/Ethereal-style templates), the separate mobile template toggle described above still exists and still needs disabling exactly as outlined. If the blog was ever switched to one of Blogger’s newer responsive themes — Contempo, Soho, Emporio, Notable, and the other single-column responsive designs rolled out from March 2017 onward — there’s no separate mobile template at all; those themes render the same responsive markup for every device, so this specific redirect failure shouldn’t occur in the first place. Before troubleshooting further on a modern-themed blog, it’s worth confirming the actual cause is something else (a caching layer, a CDN in front of the old domain, or an app-specific in-app browser behaving differently to Safari/Chrome proper) rather than assuming this fix still applies.

Resources

• Blogger
• WordPress
• rdp
• Browse our General Tech Accessories picks on Amazon