Powered by Blogger.
Menu :
Showing posts with label Dynamic Views. Show all posts
Showing posts with label Dynamic Views. Show all posts

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

Is A Sitemap Useful, For A Blogger Blog?

Occasionally in Blogger Help Forum: How Do I?, we see evidence of confusion and doubt.
Do I really need a sitemap, for my blog?
This question, when asked, may help us to design our blogs better.

WikiPedia defines a sitemap as
a list of pages of a web site accessible to crawlers or users
Classically, a sitemap is a visual index, to help the people viewing a static website, to easily identify and access a specific article in the website.

A sitemap provides an alternate index, to a non Blogger website. Most websites are static, with a hierarchically accessed, single structure. A well designed sitemap allows people and crawlers to more efficiently locate specific articles (pages or posts), in a static website.

Most Blogger blogs provide much more than a hierarchical, single, static structure. By default, a Blogger blog links its pages and posts dynamically, using several alternate indexes.
  • Archives (posts listed hierarchically, by date).
  • Labels (posts listed hierarchically, by topic).
  • Extended main page (posts listed sequentially, by "Newer Posts" / "Older Posts").
Any blog, which provides one or more of these features, is effectively its own sitemap - for viewer access.

For crawler access, the options are simpler.
  • Archives (posts listed hierarchically, by date).
  • Extended main page (posts listed sequentially, by "Newer Posts" / "Older Posts").
Label searches, which use a different URL structure from the base blog design, are not used for indexing a Blogger blog.

If you look at the main page of a typical blog, you can follow the "Newer Posts" / "Older Posts" links from page to page, repeatedly - and eventually, see every post in the blog. With a new blog, with few posts, and predominantly "first visit" viewer traffic, the main page makes a passible sitemap. For an older blog, with many posts, and more "repeat" viewer traffic, the main page makes a less efficient sitemap.

For crawlers, which will generally follow a limited number of links within any single blog or website, the main page makes a still less efficient sitemap. Most blogs with any appreciable search engine reputation, however, only need new posts indexed by the crawlers - as older posts are already indexed, and remain in search engine cache.

Blogger provides a good, default gadget which serves as a sitemap, on most blogs - the Archives index. Look in the sidebar of this blog, about halfway down, for the "Contents" gadget. This is an HTML based gadget, which produces a set of hierarchical, date structured links, exhaustively enumerating each post in the blog. It's an ideal structure, for search engine bots (crawlers) to follow. If your blog includes this accessory, that's probably sufficient for indexing.

Blogs which contain one or more features can provide search engine access, organically.
  • Well written, regularly published posts.
  • The standard Archives gadget.
  • The standard "Newer Posts" / "Older Posts" links.
Such blogs may not need a sitemap, to provide good access to both people and crawlers.

Both the Archives, Labels, and "Newer Posts" / "Older Posts" links are subject, on some blogs, to customisation. A blog with Javascript driven Archives, Labels, and / or custom pagination ("Newer Posts" / "Older Posts") gadgets may not provide easy crawler access. This also affects blogs which use dynamic templates. If you tweak your blog extensively, you may want to consider these issues.

There is one special case where a sitemap is always needed. Any time the URL of your blog is changed - whether to a new BlogSpot URL, or to a non BlogSpot custom domain - prompt re indexing, under the new URL, is a necessity to regain search engine reputation. A robust sitemap set, which directly references all posts in the blog, helps the crawlers to re index each post, under the new URL, much faster.

Other than that special case, a blog with standard, well designed, features may not actually need a sitemap.

A sitemap, setup through Google Webmaster Tools - and using the blog posts newsfeed, defined through "robots.txt" - is a simple accessory to add, and requires no ongoing maintenance. Given this reasoning, most blog owners simply setup a sitemap, and don't worry about the above issues and questions.

>> Top

One Spurious Technique For Publishing Your Blog Anonymously

Some blog owners wish to publish their blog anonymously.

One of the most obvious ways to achieve anonymity - and one of the least useful - is to not publish your name, in your blog posts.
Edit the "Blog Posts" gadget, in the dashboard Layout wizard, and de select "Posted By".
This solution will immediately remove your name from any posts published by you - as long as a dynamic template is not involved.

The dynamic templates do not reference the "Blog Posts" selections. This will be a problem, for achieving anonymity.

Any blog, at the option of the reader, may be viewed, in dynamic mode. No blog, even with the "Posted By" option un checked, will be anonymous.

This is the URL of this blog.
http://blogging.nitecruzr.net/
This is the URL of this blog, using a dynamic template.
http://blogging.nitecruzr.net/view
You - or any reader - can do the same with your blog. This will be a problem, if you use the "Posted By" selection in "Blog Posts", to make your posts anonymous.

Now, checkout my anonymity test blog - in non dynamic view.
http://nitecruzr-test-anonymity.blogspot.com/
And checkout the first post, in dynamic view.
http://nitecruzr-test-anonymity.blogspot.com/view
D'Ohh!

If you truly want to publish your blog anonymously, there are several issues which you need to consider - all of them necessary. The "Posted By" option is not part of these issues - since it has no effect on anonymity.

Having considered all of the issues required to achieve anonymity, consider the issues where true anonymity can be a problem. Blogger supports our right to publish our blogs, anonymously - and will not break our right to anonymity.

>> Top