Skip to main content

FeedBurner Feed Redirection, And "BrowserFriendly"

Some blog owners and readers ask about blog feed displays, in Blogger Help Forum: Get Help with an Issue.
I clicked on this text at the bottom of the blog page:
Subscribe to: Posts (Atom)
and I got a screen full of gibberish.
This is a known oddity, in Chrome.

The Chrome browser, unlike Firefox or Internet Explorer, lacks a built in newsfeed reader.

If you, the blog owner, want to see a useful display of blog content, when you click on "Subscribe to: Posts (Atom)", you can do that. Just add a Chrome extension, such as "RSS Subscription Extension (by Google)".

With the right extension added to Chrome, you will see blog content - instead of a screen full of gibberish. But what about your readers?

Give your readers a consistent and useful newsfeed display page.

If you want your readers to see useful content - plus a toolbar that helps them subscribe, using email or a feed reader, you can setup a FeedBurner feed, and add the BrowserFriendly service.

Just activate BrowserFriendly, from the FeedBurner Optimize page. Then, select the BrowserFriendly options that interest you.

You can choose from a number of popular feed readers to support, or add your own.

If you have Email Subscriptions added, your readers will have a selection for that, in the BrowserFriendly display.
NOTE: Because you use FeedBurner Email Subscriptions, a link to subscribe via email will automatically appear with your subscription selections.

You can add the original blog feed, to BrowserFriendly.

For more consistent reader statistics and subscriptions, you can make sure that the BrowserFriendly display uses the original posts newsfeed.

If you have configured your web server to redirect from your old feed to your new one, you should tell subscribers to use your old, redirected address so that the redirect can work its magic and subscribers always use that address, but FeedBurner tracks 100% of your traffic. FeedBurner will always show that address to potential subscribers instead of the FeedBurner feed address in BrowserFriendly.

Click on "Use your redirected feed URL on your BrowserFriendly landing page", to open the "BrowserFriendly" Redirected Feed URL setting wizard.

Copy the "Original Feed" URL from "Edit Feed Details" into the "Redirected Feed URL".

BrowserFriendly gives all readers, ignoring the browser, a good subscription page.

Whether your readers use Chrome, Firefox, or Edge / Internet Explorer, you can have them using the FeedBurner BrowserFriendly newsfeed display, and subscription wizard. All of your readers will have a more consistent access to your blog feeds and subscription options - and you'll have a happier reader community.

Complementing BrowserFriendly, you may wish to look at SmartFeed and Format Burner, to provide the right feed format. And if any of these ideas create conflicting needs, you can use multiple FeedBurner feeds.

With a #Blogger blog that uses email / newsfeed subscriptions to attract and encourage readers, you can provide a more consistent subscription display for your reader community, by using #FeedBurner and the BrowserFriendly service.


Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: