Skip to main content

Custom Redirects, And The Mobile Template Redirect, Are Not Compatible

We've recently seen a few reports about problems with custom redirects, in Blogger Help Forum: Something Is Broken.
I want to redirect my blog URL to a static home page. With a redirect in place, mobile computer users can't access my blog. Mobile browsers display an error, mentioning too many redirects.

This problem is being reported by owners of blogs both published to BlogSpot, and to non BlogSpot domains.

When published to a non BlogSpot domain, the problem is present even for domains properly setup.

Some advice, given in the forum, suggests use of forwarding, instead of referral, as a solution. This advice is a problem, for 2 reasons.
  • Forwarding cannot be used with blogs published to BlogSpot.
  • Forwarding is not a good solution for custom domain publishing.

(Update 2014/11/01): By adding one additional custom redirect, you can have a redirected mobile home page. Even a different mobile home page, if you like.

For blogs published to BlogSpot, there are just two choices.
  1. Disable the redirected home page, and do without the custom home page.
  2. Enable the custom redirected main page, and do without mobile access to the blog.

For blogs published to a custom domain, there are, supposedly, three choices.
  1. Disable the redirected home page, and do without the custom home page.
  2. Enable the custom redirected main page, and do without mobile access to the blog.
  3. Use forwarding, instead of referral, to redirect the domain to the blog.

Forwarding comes in two versions, with differing effects from the two versions. Neither version of forwarding is beneficial, to Blogger blogs.
  • DNS forwarding results in the blog being indexed under the BlogSpot URL, by the search engines. The blog's readers will be able to use the (forwarded) domain URL, to access the blog - but all search engine references will mention the BlogSpot URL.

    With some access to the blog through the BlogSpot URL, and other access through the domain URL, blog reputation will drop, similar to blogs newly published to a new URL. Both reputation and traffic will do the same.
  • Frame forwarding results in the blog being visible within an IFrame. No indexing of the blog, by the search engines, will take place, with blog contents visible inside an iframe. Search engine reputation will drop even worse with DNS forwarding.
Not all registrars offer both versions of forwarding, so you may have to take what they offer - and accept the resulting loss to the blog.

As a workaround, until the problem is fixed, you can return to the previous technique for making a static home page.

Basically, blog owners may have to choose between having a custom home page (for desktop access), and having the blog accessible through mobile browsers (for mobile access) - or using the workaround. And everybody has to wait, patiently, until Blogger Engineering can come up with a better solution - to make custom redirects, and the mobile browser redirect, work together.


Ryan Stefiuk said…
I have been search in all over for a fix. Haven't found one yet. I'm glad to see it's not me who's going crazy thinking there's something wrong. When did the changes occur that cause the redirect loop? They must be pretty recent. Great site by the way!
alene said…
Thank you so much for your site! Thank you for putting these issues in simple english and in a comprehensive manner!
I'm just encountering this problem with a new site - has there been a fix to this issue since 2013 or will i run into the same problem if I create a static home page?
Nitecruzr said…
Hi St Luke's,

Thanks for the question.

It's not a fix - but they enhanced the custom redirect feature to support "?" based URL suffixes.

You simply add a second redirect, to support the mobile URL - if you want.
From: /?m=1
To: /p/static-home-page.html?m=1

You could even redirect the mobile URL to a different static page. This seems like a better solution, it gives you more choice.
From: /?m=1
To: /p/static-home-page-2.html?m=1
Thank you! I very much appreciate the update and help!

Popular posts from this blog

Embedded Comments And Main Page View

The option to display comments, embedded below the post, was made a blog option relatively recently. This was a long requested feature - and many bloggers added it to their blogs, as soon as the option was presented to us. Some blog owners like this feature so much, that they request it to be visible when the blog is opened, in main page view. I would like all comments, and the comment form, to be shown underneath the relevant post, automatically, for everyone to read without clicking on the number of comments link. And this is not how embedded comments work.

What's The URL Of My Blog?

We see the plea for help, periodically I need the URL of my blog, so I can give it to my friends. Help! Who's buried in Grant's Tomb, after all? No Chuck, be polite. OK, OK. The title of this blog is "The Real Blogger Status", and the title of this post is "What's The URL Of My Blog?".

With Following, Anonymous Followers Can't Be Blocked

As people become used to Blogger Following as just another tool to connect people, they start to think about the implications . And we see questions like How do I block someone who's been following my blog secretly? I couldn't see her in my Followers list (hence I couldn't use the "Block this user" link), but I have looked at her profile and could see that she's Following my blog. Following, when you look at the bottom line, is no more than a feed subscription and an icon (possibly) displayed on your blog, and linking back to the profile of the Follower in question. If someone Follows your blog anonymously, all that they get is a subscription to the blog feed. If you publish a feed from your blog, and if the feed is open to anybody (which, right now, is the case ), then it's open to everybody. If someone wants to use Following to subscribe to the feed, you can't stop this. You can't block it before, or after, the fact. You can't Block w