Blogs Publishing Large NewsFeeds Can Cause Problems

We're seeing a few reports, which involve blogs with published newsfeeds with large volume, producing intriguing varieties of symptoms, in Blogger Help Forum: Something Is Broken.

My Followers are not getting email updates!

and

My blog does not update, on my Followers blogs!

and

My blog can't be viewed! All that I see is the gears turning!!!

All of these blog owners are publishing blogs which produce feeds, which are too large.

In general, a newsfeed can be any size necessary. There are two secondary details, however, which can make a Blogger blog, publishing a large newsfeed, problematic.

There is nothing basically wrong with large newsfeeds - but blogs which use dynamic templates, and blogs which produce feeds redirected through FeedBurner, can have problems when publishing large feeds.

We're currently seeing blogs with large feeds causing problems with dynamic templates. This produces one more case where we end up prescribing a non zero Timeout setting, for dynamic views.

Besides dynamic template display problems, blogs with large newsfeeds can produce problems, when redirected through FeedBurner. There are two approaches to making a feed smaller - use less posts - and alternately (when possible) format posts using Blogger post editor, instead of using Microsoft Office.

To diagnose a large feed problem, one can use any text browser, such as Rex Swain's HTTP Viewer, or maybe Web-Sniffer View HTTP Request and Response Header. Either product will provide a size display.

Feeds over 512K in size will be problematic, with either dynamic view, or FeedBurner redirection.

>> Top

Search Engines, And Private Blogs

Not every blog owner realises the relationships between private blogs, and search engine indexing.

Some blog owners think that private blogs can't be indexed, by the search engine robots. Given the way private blogs work, search engine access is not directly restricted - even though indexing activity is impeded.

People are prevented from viewing a private blog, only because Blogger displays the private blog interstitial in front of the blog display.

This blog is open to invited readers only

It doesn't look like you have been invited to read this blog. If you think this is a mistake, you might want to contact the blog author and request an invitation.

Other than the presence of that display, access to the blog is not affected. This detail becomes important, for some potential readers who are accessing the Internet through some Local Area Networks.

Search engines are not directly affected by the private blog status - though there are interesting details.

• The blog description, when indexed, will contain the text of the interstitial notice.
• Private blogs do not publish newsfeeds - and with newsfeeds used to facilitate indexing, the indexing process is not as consistent as with public blogs.
• The dashboard Privacy setting, which generates an entry in the "robots.txt" file, is advisory only, to search engine robots.

The interstitial notice is authoritative to people, when viewing the blog.

The notice does not block robots. Robots are stopped only when they voluntarily accept the relevant settings in "robots.txt".


The text content of the interstitial advice will replace the blog description, in SERP displays.

This blog is open to invited readers only

Without an actual blog description, potential blog readers won't feel very encouraged to view the blog. Even when clicking on the SERP entry, the would be blog reader is still taken to the interstitial, and goes no farther.

This blog is open to invited readers only

Private blogs do not publish newsfeeds. Since the newsfeed provides the Blogger equivalent of the sitemap, a typical private Blogger blog has no sitemap - and search engine indexing activity is not as regular.

The settings in the "robots.txt" file, which specifies bots and access, is not authoritative. Acceptance of the "robots.txt" settings is left to the discretion of each different robot - and a robot which does not observe the settings can access any website.

A private blog can be indexed - though without free access by readers to a private blog, there will be less links referencing the blog - and less indirect search engine activity.

Less links referencing the blog leads to less indexing, by the search engines. Less indexing leads to less entries in SERPs, poorer SERP positioning - and relative lack of success when using search engine cache, to search the blog.

With a private blog, you'll be much more successful using a direct blog search.

>> Top

BlogLovin, And Blogs Publishing Feeds Through FeedBurner

We're seeing a few reports, in Blogger Help Forum: Something Is Broken, about BlogLovin, and their inability to accept feeds from Blogger blogs.

My feed on Bloglovin is not updating correctly, so I emailed BlogLovin Support. They responded, and said it was because my RSS feed isn't working correctly.

When diagnosed, we frequently see a working posts feed, redirected through FeedBurner.

It appears that BlogLovin is not able to properly accept some (or all) FeedBurner redirected feeds. The most obvious solution here would be to setup BlogLovin properly, to use a non redirected feed, so they get the native Blogger posts feed.

Upon trying to test my diagnosis, using my test blog, it appears that adding a blog to BlogLovin requires publishing a new post, with their Follow button conspicuously located.

Paste this text into a new blog post:

<a href="http://www.bloglovin.com/blog/10757427/?claim=ge8y4cfhqfx">Follow my blog with Bloglovin</a>

In some blogs it's necessary to put the code in the top of the blog post

It does not appear to be easily possible to specify the blog feed, in this case. It appears that BlogLovin extracts the blog feed, using the feed autodiscovery meta code, in the blog template.

It appears that any solution to the problem with BlogLovin vs FeedBurner redirected feeds will require involvement with BlogLovin Engineering.

1. Convince BlogLovin Support to make their service accept FeedBurner feeds.
2. Convince BlogLovin Support to make their service filter feed redirects.
3. Discontinue FeedBurner from your feed redirect.
4. Figure out how to specify a non redirected feed to BlogLovin.

I'm not hopeful that #4 has any future.

>> Top

Preventing FeedBurner Email Distribution Delay

One very useful FeedBurner service is the Email Distribution feature.

Email Distribution is virtually a turnkey subscription management. Email Distribution has one limitation, which not everybody understands, however.

FeedBurner sends out any new posts daily, based on a chosen distribution time. Depending upon what distribution time you choose, for any FeedBurner Feed, you can have anywhere from (up to) 2 hours, to 26 hours - of delay, between publishing a post, and having that post distributed by email.

To minimise email distribution delay, you choose the daily distribution time carefully - then publish immediately before the daily scheduled distribution.

1. Choose a convenient distribution time window.
2. Using the FeedBurner menu, Publicize - Email Distribution - Delivery Time, choose the corresponding daily 2 hour window, for email distribution.
3. Publish posts immediately before the start of the chosen time window.

You will still have a single daily distribution time - but you can choose an appropriate distribution window. And, you can publish just before the chosen distribution window.

>> Top

Dynamic Templates, And Jump Break

We see occasional evidence of confusion, in Blogger Help Forum: Something Is Broken, from blog owners who are using a dynamic template.

Why does the Jump Break not show up, in the blog display?

or

Why can't I see the entire post?

Not all blog owners understand the limited options, in the dynamic templates.

Compare the main page of this blog, to a formatted feed page of this blog.

Do you see the differences? I use Jump Break consistently, on my main page posts. Unfortunately, newsfeeds do not include the Jump Break, because the newsfeed standard was developed before Blogger developed their post summarisation feature, Jump Break.

Since dynamic views format the display using the blog posts feed, they have no way to include the Jump Break. The posts feed contains each post, in its entirety. The "Jump Break" snippet code is part of the main page display, not the posts.

This is just one more reason why dynamic templates won't be chosen, on all blogs.

If you want to display your main page as I do, you can't use a dynamic template. Dynamic templates format their posts without using jump break. Some dynamic template "main page" views include text, broken; others include text, unbroken; and still others include only photos. None of the dynamic views include the Jump Break.

Remember that to use dynamic views, you have to set the blog feed to "Full". If you set the feed to "Until Jump Break", dynamic views won't work. The dynamic views format the post displays to the requirements of each different view (selected by the reader), and require the complete post content in the feed. Here's an example of what happens, using "Until Jump Break" - and with a Jump Break included.

>> Top

What Are The Mysterious Turning Gears?

This is a question, occasionally seen in Blogger Help Forum: Something Is Broken.

I cannot view some blogs - all that I see are gears, turning endlessly. What is going on, here?

The gears are animation, displayed by Blogger, while a dynamic template and blog content loads on the computer being used. Generally, the gears will play for a few seconds, then the blog will be seen. For an example, check out my Musings blog.

Sometimes, all that you will see are the gears, endlessly turning - waiting for the templates and blog content to download.

The dynamic templates, used by some Blogger blogs, represent an innovative approach to providing web content.

Normal web content, provided in Blogger blogs which use Classic, Designer, and Layout class templates, consists of comments, gadgets, posts, and templates, arranged together in pages (dynamic and static).

Blogs which use Classic (HTML only) templates arranges everything when the blog is maintained. Blogs which use Designer / Layout templates (HTML / XML) arrange the content when the blog is maintained - then build the individual pages when the blog is read by each viewer, dynamically. For all 3 classes of templates, the content is served from Blogger / Google servers, in individual display pages.

The Dynamic class of Blogger templates take the concept of dynamic publishing to another level. Dynamic class templates load a significant amount of script code (the template) directly to each client computer. Instead of reading the pages of blog content from a Blogger / Google blog server, a dynamic template script, running on the client computer, reads the published blog feeds from a newsfeed server - then turns the feed content into a display.

A Dynamic template is a specialised Newsfeed Reader, similar to the dashboard Reading List, or to Google Reader.

By offloading a large amount of the publishing process to the client computer, and by using the blog comments and posts feeds, Blogger provides blogs which can be viewed in a number of different ways - selectable by each individual viewer, and at the convenience of the viewer. This selectability is not without cost, unfortunately.

• The templates require a significant amount of script code.
• The templates require the blog comments and posts newsfeeds.

For most blogs using a dynamic template, and being viewed on most computers, the "turning gears" icon plays briefly, while the template code, and the blog comments and posts newsfeeds, are downloaded. As soon as downloaded, the content is assembled into a display, and the viewer can view the blog. This does not happen, in all cases.

• Some client computers may filter the template code.
• Some client computers may not have a fast Internet connection.
• Some blogs may not publish a full newsfeed.

If the client computer has a slow Internet connection, the viewer may watch the turning gears for more than a few seconds. If the computer filters scripts aggressively, or if the blog does not publish a full newsfeed, the gears play, endlessly, while the computer waits for the scripts and newsfeeds to finish downloading. In the latter case, the viewer can only find another blog to view.

If you encounter one or two Blogger blogs playing the turning gears, endlessly, then you are experiencing the reality of dynamic templates - some blog owners do not realise that they have broken their blogs. If you encounter a large number of Blogger blogs doing this, then you might want to check the filters, on your computer - including, but not only, the browser cookie and script filters.

>> Top

Blogger Magic - Activating The Blog Feed

One of the neatest - and easiest - ways to make your blog available to a larger audience uses a replica of the blog posts - the blog newsfeed. Most blogs, when new, have the feed activated by default.

Oddly enough, some blogs do not publish a newsfeed. Some blog owners, wondering why their blogs are not being indexed by the search engines, are perplexed.

Why isn't my blog publishing a feed?

You activate the various newsfeeds from the dashboard Settings - Other - Site Feed wizard. Routinely, you'll have one setting - "Allow Blog Feeds" - and this setting will affect all feed options equally. If you select "Custom", you can enable or disable any of the 3 feed options, separately.

• Blog Posts Feed
• Blog Comments Feed
• Per-Post Comment Feeds

Each setting will have 3 possible selections - Full, Until Jump Break, Short, None.

(Note): If you enable a feed, it is available to anybody with a feed reader, either a feed reader that they personally use, or one built in to a blog. There is no option to limit feed access - feeds are available, equally, to all interested parties. This is why feeds are not published by limited access (private) blogs.

If you fear that unknown parties might steal content from your blog by using your feed, don't publish a Full feed, publish a Short feed. This will require anybody wishing to read a complete post to access your blog, rather than reading it in their newsreader.

>> Top

Add A Simple "Recent Comments" / "Recent Posts" Gadget To Your Blog

The recently observed problems with some third party gadgets, previously added by many blog owners to their blogs, leaves these (and other) owners lacking a useful feature in their blogs. For many blog owners, fortunately, this is not an impossible problem to resolve.

Blogger provides us with a native accessory, called a "Blog Feed" gadget, which will provide acceptable "Recent Comments" and "Recent Posts" functionality, for many blog owners.

Look at the sidebar of this blog, for "The Real Blogger Status - Comments", and "The Real Blogger Status - Posts". Those are "Recent Comments" and "Recent Posts" gadgets, based on the Blogger supplied "Feed" gadget - which is not a third party accessory, and is not subject to future third party peccadilloes.

To make your new gadget, start with the URL of the blog feed desired. Then, add a Blogger supplied Feed gadget, using the "Add a gadget" wizard, in the dashboard Layout display.

This is the URL of this blog.

http://blogging.nitecruzr.net

This is the URL of the blog comments feed.

http://blogging.nitecruzr.net/feeds/comments/default

This is the URL of the blog posts feed.

http://blogging.nitecruzr.net/feeds/posts/default

Setting up a "Blog Feed" gadget is simple enough.

1. Add a "Feed" gadget (Only select the "Feed" gadget, "By Blogger"!!!), using the "Add a gadget" wizard. Avoid any similarly named gadget not "By Blogger".
2. Plug in the Feed URL (see my examples above), and Continue.
3. Review / change the options offered, and Save.
4. Test your new blog accessory - provided by Blogger - with no future hacking activity anticipated.

And, you're done. Wasn't that simple?

>> Top