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.

Right now, there is no solution for this problem - though there is a workaround. Blogger Support is aware of the problem - but it's not certain that a solution will be immediate.

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.

>> Top

Recovering A Deleted Page Or Post, Chapter 3

We've been advising anxious blog owners, for some time, how to recover deleted pages and posts.

The easiest solution, in the long run, is to recover the PageID / PostID, and re publish the deleted page / post.

Unfortunately, all deleted pages and posts can't be edited and re published. With new posts, un indexed by the search engines, you won't be able to find the post in cache - and you'll never determine the PostID. This will be a frequent problem with deleted pages - as static pages generally won't get indexed by the search engines - nor will they ever be included in the blog posts feed.

In some cases, even when you know the PageID or PostID, the page editor / post editor may simply reject your attempt to re edit - and give you another bX code.

Even so, all is not lost. You may have to rebuild the page or post - but you can generally keep the URL, of the deleted page or post, operational. Just plan the rebuilding process.

In cases where a deleted page or post can't be simply re published, you can publish a replacement page or post - and redirect both your readers, and the search engines, from the URL of the deleted page / post, to the replacement page or post.

To minimise loss of reader and search engine reputation, you'll want to publish a replacement page / post as soon as possible after the old page / post is mistakenly deleted. With replacement posts published in the same month as the original - and with all pages - this can cause the well known ugly URL suffix, to prevent a duplicate URL.

When you publish a replacement page or post, you have one chance to get the title and URL right - and prevent the ugly URL suffix. The one chance ends, when you hit the "Publish" button.

With a deleted post, you can use the Custom Permalink option ("Permalink", under "Post settings", in the post editor window) to make the published URL slightly different from the default. Alternately, you'll need to deliberately choose a slightly different Title, for the replacement post.

When you publish a replacement page, you won't have a "Custom Permalink" option. Your only option, in this case, is to choose a slightly different Title, for the replacement Page.

Static page URLs do not contain the year and month of publishing, so you'll need to use a different Title for every replacement page - even if you publish the replacement in a later month, or even a later year. Since static pages are generally not as widely publicised as posts, the different title should still be preferable to the alternative - the ugly page URL suffix.

Just choose the title and URL carefully, before you hit "Publish", to prevent long term embarrassment. And having published the replacement, setup a Custom Redirect, to keep the URL of the deleted page or post operational.

>> Top

Recovering A Deleted Page Or Post, Chapter 2

Blog owners have been deleting their pages and posts, then changing their minds later, since Blogger started providing the ability to delete pages and posts.

We've been advising anxious blog owners, for some time, how to recover deleted pages and posts. The easiest solution, in the long run, is to recover the PageID / PostID, and re publish the deleted page / post.

When the deleted page or post cannot be re published, the next option is to re build the page / post, possibly using feed cache.

Using this technique, you'll have to reformat the post content, as feed content is formatted relatively simply. When you publish the post, it will publish as a new post, with a new URL - so any external references to the missing post URL will still be broken.

Thanks to the recently offered Custom Redirects option, though, we can make this latter choice slightly less undesirable.

When a deleted page or post has to be rebuilt from the beginning, the classic prognosis was not good.

1. The content is retrieved or rewritten, then re formatted.
2. The page / post is re published, but under a new URL.
3. The readers, and the search engines, adjust to the new URL being used.

For many blog owners, issue #3 is the cruelest blow - as the blog suffers reputation loss, from readers and search engines seeing

404 Not Found

for the deleted page / post.

Given enough determination and time, the blog owner can get through issues #1 and #2 - but issue #3 is the gift that just keeps on giving. Using Custom Redirects, though, that does not have to be the case.

It's a simple solution - and your readers and the search engines don't have to do anything unusual.

1. Rebuild the page / post, using a carefully chosen Title / URL.
2. Add a Custom Redirect.
   • From: The deleted (previously published) URL.
   • To: The new (re published) URL.
3. The readers, and the search engines can view the re built page / post contents using the old URL - and update their record of the URL, as convenient to them, to point to the new URL. And the page / post never goes offline.

And you, the blog owner, can get back to work on new pages and posts.

>> Top

Custom Redirects, And Old FTP Published Blog URLs

Long ago, Blogger blog owners would publish a blog as part of an existing website. With the website published as "www.mydomain.com", they would create a website subdirectory "www.mydomain.com/myblog", and publish the blog there.

The option to publish a blog as "www.mydomain.com/myblog" required an externally maintained domain / website - and the Blogger feature "FTP Publishing". In 2010, Blogger, with many man hours spent fixing a constant stream of problems, retired "FTP Publishing", in favour of "Custom Domain Publishing".

Custom Domain Publishing, like FTP Publishing, lets us publish our Blogger blogs to non BlogSpot URLs. Unlike an FTP published blog, a custom domain published blog requires a separate subdomain for each different blog. If a non Blogger website is hosted as "www.mydomain.com", a Blogger blog can only be published to "blog.mydomain.com" - and "www.mydomain.com/blog" became an impossibility.

Last year, Blogger introduced Custom Redirects, as part of the "Search Preferences" feature. Now, once again, a Blogger blog can be addressed as "www.mydomain.com/myblog", when hosted as "www.mydomain.com" - though a non Blogger website (if one exists) cannot be directly hosted as "www.mydomain.com", simultaneously.

It may be possible, however, to host an externally published website as "site.mydomain.com", and a Blogger blog as "www.mydomain.com" - and use the Blogger "Missing Files Host" feature to locate website pages, dynamically, in "site.mydomain.com". There may be hope, for people who declined to migrate their FTP Published blogs, in 2009 - and who now have static "blogs" as frozen pages in their external websites.

>> Top

Blogger Magic - Redirecting A URL In Your Blog

In 2012, Blogger gave us a suite of useful utilities to control how the search engines see our blogs. This includes the ability to redirect one URL in our blog to another URL in our blog.

The "Custom Redirects" feature is easy to use - but like many Blogger features, not immediately so. Neither its possibilities, nor its limitations, are obvious to everybody.

Custom Redirects, which is part of the dashboard Search Preferences wizard, is not difficult to use.

1. Go to Settings - Search preferences - Custom Redirects, and click on Edit.
2. If you have existing redirects, click on "New redirect".
3. Enter the correct "From" and "To" values.
4. Select "Permanent".
5. Click on "Save".
6. Click on "Save changes".

The possibilities are almost endless, when you reference any valid URL in a given blog. Thanks to the syntax of the "From" and "To" values in the wizard, Custom Redirects will only redirect within the blog itself, and is thus useless to spammers and others who would like to misuse it.

Just take any two URLs within the blog, strip the base URL from each, and enter the results as the "From" and "To" values. Always start "From" and "To" with a "/" (no leading spaces, or non visible control characters!), signifying the root of the URL, follow the above procedure, and you're done.

Click here, for examples of what you can do. Then, use your imagination. Just remember though - the actual URL - and what your readers see in the address window - will not change.

>> Top

Removing The "/p/" From the URL

Ever since Blogger (finally) gave us the option to add static pages to our blogs, blog owners started asking

How do I make my pages URLs cleaner? The "/p/" in the URL is so messy looking.

Our typical response would be simple.

Sorry, you're stuck with the URL, as is, for a static page.

And, that was that.

Later, Blogger gave us the ability to redirect URLs within the blog - and that changed.

This is the URL of the topics index in this blog ("labels", to use the Blogger native term).

http://blogging.nitecruzr.net/p/topics.html

Here are two alternate URLs, which also reference the topic index.

http://blogging.nitecruzr.net/topicindex

and

http://blogging.nitecruzr.net/topic-index

Click on each link, and note where you go.

To make the alternate URLs work, all that I did was use "Custom Redirects", and add two entries.

From: /topicindex
To: /p/topics.html

and

From: /topic-index
To: /p/topics.html

Of course, the address displayed will be the address published - not the address entered into the browser. You can't change the address displayed - you can only simplify what has to be entered. And, to maintain proper spam mitigation policy, you can only redirect within the base URL of the blog.

Other than that, the possibilities are almost endless.

>> Top

Redirecting Any URL In Your Blog, To Another URL In Your Blog

Several months ago, Blogger Engineering gave us a new Blogger feature - the ability to redirect any URL in a blog, to any other URL in the blog. Like any feature, we found an immediate use for it - something much requested, for a good while.

Other people have found more uses for the redirection feature - and still others have found confusion. The syntax used in the redirection "From" and "To" values is not always obvious - and occasionally there is confusion about what can - and can't - be done with redirection.

This is the URL of this post.

http://blogging.nitecruzr.net/2012/12/redirecting-any-url-in-your-blog-to.html

Using the redirection feature, I can redirect another URL in this blog, to this post - or conversely, I can redirect the URL of this post to another URL, in this blog.

Both the "From" and "To" values in "Custom Redirects" accept any static blog URL, less the base URL of that blog. You cannot specify the base URL - so all redirections will be within the blog itself. You also cannot use a dynamic URL (containing a "?") in a redirect.

The initial use for the redirection feature (at least, for me) was to replace the Home page of the blog, with another page or post - possibly, this post.

From: /
To: /2012/12/redirecting-any-url-in-your-blog-to.html

I could change the Home page of this blog, to start all new readers on the Topics Index page.

From: /
To: /p/topics.html

If I was to change the Title of this post, when re published, the URL would not change. If I wanted to change the URL of this post, I could redirect the desired URL, to the actual URL.

From: /2012/12/redirecting-any-urls-in-your-blog.html
To: /2012/12/redirecting-any-url-in-your-blog-to.html

If I want to allow this post to be accessed from a shorter URL, I can do that. If you click on the shorter URL (below), you will note that you still see the longer URL in the browser address window!

From: /redirecting-any-url-in-your-blog-to.html
To: /2012/12/redirecting-any-url-in-your-blog-to.html

I recently created a shortcut to my Topics index, as "blogging.nitecruzr.net/topics".

From: /topics
To: /p/topics.html

To get the "From" and "To" values for any redirection, I simply take any two URLs in the same blog. Choose any two examples - one for "From", the other for "To".

• The Home page: http://blogging.nitecruzr.net/
• A post: http://blogging.nitecruzr.net/2012/12/redirecting-any-url-in-your-blog-to.html
• A static page: http://blogging.nitecruzr.net/p/topics.html
• A label search: http://blogging.nitecruzr.net/search/label/Redirecting
• A shortcut URL: http://blogging.nitecruzr.net/topics

And drop the base URL: http://blogging.nitecruzr.net

Giving:

• The Home page: /
• A post: /2012/12/redirecting-any-url-in-your-blog-to.html
• A static page: /p/topics.html
• A label search: /search/label/Redirecting
• A shortcut URL: /topics

Having developed the proper "From" and "To" values, adding a "Custom Redirects" entry is simple enough.

Having setup a useful complement of Pages, and redirected the Home page, you may wish to remove the "Home" page tab. Just edit the Pages gadget, using the dashboard Layout wizard, or the on blog quick edit icon - not the dashboard Pages wizard - and de select the "Home" page.

A simple example, showing the result, may be seen in my demonstration blog, Home Page Redirected To Label Search.

From: /
To: /search/label/Home%20Page

You may also wish to remove the "Showing posts with label ..." notice, if you like a cleaner display. In my demonstration blog (mentioned above), I did not do this - to make my examples more obvious.

The possibilities here are endless. Just use common sense - and again, note the limits on redirection.

Click here, for instructions. Note again, that the actual address, displayed in the browser address window, will not change.

>> Top

Redirecting The Traffic From Your Blogger Blog

Some Blogger blog owners are confused about their ability to redirect traffic to, or from, their blogs. Sometimes this leads to problems, as in the need to report a problem with spam classification, in Blogger Help Forum: Something Is Broken

Why was my blog just deleted, for "Malicious JavaScript"?

Other people will want to know why, after renaming their blog, all the search engine references now point to a dead URL. Still others may want to rename specific posts, and yet have the post URLs match the new titles.

Blog URLs, and Post URLs, are complex details, for Blogger blogs. By default, both are managed for you. Not everybody understands how to manage blog and post URLs, when necessary.

Not every blog owner understands that ones readers are not possessions, to be manipulated at will. Many spammers would love to use various Blogger blogs as gateways, redirecting their readers either to other Blogger blogs, or to non Google controlled websites. In order to discourage spamming activity, neither type of redirect is permitted, by the Blogger spam classifier.

Even if automated redirection was permitted, many redirection techniques may not work for everybody. Modern browsers, designed to prevent abusive activity like hacking and spamming, may have filters which explicitly block DNS settings, and scripts, designed to redirect traffic from one website to another. If you design your URL migration strategy to require automated redirection - and even if Blogger / Google does not delete the blog for abusive technique - you may still not see a consistent transfer of existing traffic, to your new URL.

You can redirect a Blogger blog, to a non BlogSpot URL, using properly setup custom domain publishing - "CNAME" referral. That is the only valid way to redirect a BlogSpot URL, to a non BlogSpot URL. Any other method will eventually leave you posting, in Blogger Help Forum: Something Is Broken

Why was my blog just deleted, by Blogger?

If you rename your blog - and publish to a new BlogSpot URL, your only recourse is to publish a "stub" (empty) blog to the old URL, and visually redirect your readers.

This blog is now published as "blogger-status-for-real.blogspot.com". Please update your bookmarks.

You can, if you wish, redirect the blog feed, after renaming the blog - but this should be done only when necessary.

There are several specific cases where the blog feed should not be redirected.

Blogger recently provided us the option to redirect traffic from one blog post to another - but the syntax used by the custom redirects wizard explicitly prevents redirection outside the base blog URL. That said, we have seen some imaginative redirections, between different URLs in the same blog.

Use of the custom redirect feature can generate interesting problems, not all of which can be prevented, easily. You can redirect some URLs - but you need to understand what you can, and cannot do - and why you cannot do everything that you would like.

>> Top

Custom Redirects Let You Modify Pages Or Posts, And Publish Different URLs

We've been asking for the ability to have post URLs that differ from the post titles, for some time. Now, we have the Custom Permalinks feature, available in the New Blogger GUI Posts Editor, for new posts.

Some people would like to use custom permalinks for existing posts - and for pages. We can do that, too - but not by using Custom Permalinks. Custom Permalinks only works for new posts - and not for pages.

To change the permalink for existing pages and posts, we use the Custom Redirects option, in the "Settings" menu under "Search preferences".

This post was published as

blogging.nitecruzr.net/2012/07/custom-redirects-let-you-modify.html

If I had used the "Permalink" option before publishing, I could have entered

new-blogger-gui-gives-us-custom

and published

blogging.nitecruzr.net/2012/07/new-blogger-gui-gives-us-custom.html

If I want to change the URL of an existing page or post, I would use "Custom Redirects".

To address this post as

blogging.nitecruzr.net/2012/07/new-blogger-gui-gives-us-custom.html

instead of

blogging.nitecruzr.net/2012/07/custom-redirects-let-you-modify.html

I would use "Custom Redirects", and

1. Enter "From:" as "/2012/07/custom-redirects-let-you-modify.html".
2. Enter "To:" as "/2012/07/new-blogger-gui-gives-us-custom.html".
3. Select "Permanent".
4. Click the "Save" link.
5. Hit the "Save changes" button.

Note that Custom Redirects, unlike Custom Permalinks, lets you change the published month and year ("/2012/07/"), and the extension (".html"). If you use Custom Redirects, do this carefully.

>> Top

Blogger Magic - A Static Home Page, Improved

For many years, Blogger blog owners have been asking for the ability to have a static Home page, on their blog.

We came up with a basic solution for that, a couple years ago. Last year, I packaged the procedure.

1. Set "Show" to "0 posts".
2. Add a static HTML / Text gadget.
3. Tweak the template for the new gadget, to display only on Home page.

This was an obvious solution (to some of us) - but it's painfully complex, and it involves editing the template HTML. It's an interesting techie solution - and that's about it.

Today, I realised that Blogger recently gave us this option, in a far simpler solution, last month - but not so many people noticed it.

The "Custom Redirects" feature is just what you need, to create a static home page.

1. Setup a Static Page. Use the dashboard Pages wizard, make a "New page", and select "Blank page".
2. Use the "Custom Redirects" dashboard wizard, and redirect from the Home page to the new Static page.
3. Work on the static home page, and make it attractive.

I setup a test blog - Nitecruzr Redirected Home Page Test, and added a Static page - "Static Home Page".

nitecruzr-test-redirected-homepage.blogspot.com/p/static-home-page.html

Having setup the static page, I redirected the Home page to the static page, using the "Search preferences" - "Custom Redirects" feature.

• From: /
• To: /p/static-home-page.html
• Permanent: Yes

Edit "Custom Redirects".

1. Enter "From:" as "/".
2. Enter "To:" as "/p/static-home-page.html".
3. Select "Permanent".
4. Click the "Save" link.
5. Hit the "Save changes" button.

And, that is it. You can see my test blog, as a basic demonstration.

Note that just as easily as redirecting the home page to any static page, you can redirect to any dynamic page (aka a "post"). So, you can pin a post to the main page, using Custom Redirects.

Once the "Home" page / tab is static, you can index the posts using any sidebar gadget - such as an Archive or Label index gadget. Or, you can index posts, as if they were pages.

• Publish your posts to a given label - I used "Posts".
• Add a label search entry, as a "Web address", to Pages.

Thus my Pages entry, "Posts".

Now, anybody can have a blog with a static home page, in 10 minutes (don't overlook steps #3 and #4, above - as I did, the first time). Click here, for more examples.

---

(Update 2012/06/30): See The Video, for a live demonstration.

---

>> Top