Market Your Blog, To Those Who Are Interested

We see many questions in Blogger Help Forum: Something Is Broken, about blog content, and (lack of) appreciation by the readers.

Occasionally, people become concerned about activity of the people reading their blogs - why they get so many new visitors (but nobody returns later, to read more), or why the main page is so well read (but nobody reads the archived posts).

In other cases, they wonder why the blog was deleted - even though it had the required warning protecting it. And sometimes, they may wonder why so many people read the blog, but nobody comments on the posts.

If your blog just uses Stats, to provide you reader activity statistics, you'll probably be only concerned with visitor activity, and pageview count.

If you use an actual visitor activity log, like SiteMeter or StatCounter, you may also look at new / return visitor ratio, or pages read / visitor count. In both cases, you're examining visitor interest.

Visitor interest starts with how you advertise the blog. You get good visitor interest when you advertise the blog where it will be welcomed, and in a style where your advertisements will be welcomed.

People who don't like your blog may read the first page, then go elsewhere. If they read more than the first page, they will probably be doing that so they can report the blog, for TOS Violation or similar. This is why some blogs are unrighteously clasified as abusive.

No matter how objectively you may write a blog discussing alternative lifestyles, if you advertise your blog where Bible Belt USA Conservatives may gather, the best result that you may see is "single pageview" visitors.

Occasionally, we'll see a problem report that starts out with a common complaint.

Why was my blog deleted? I don't spam.

When we're able to retrieve a cached copy of the blog, we'll agree with the owner.

Some blogs, deleted as abusive, will have a little known problem.

Commercially funded adult content.

Other times, the problem will be more subtle.

I set the "Adult Content?" flag to "Yes"! Why am I getting complaints? (Why was the blog deleted?).

The problem here starts with the nature of the "Adult Content" warning.

Not every blog owner realises that the warning is only advisory. Anybody, no matter their age or religious preference, may (by accident, or intentionally) click on "Agree". Having clicked, they may be subject to a faceful of content which is not in their best interest, or which they do not appreciate.

If a link to your blog appears in the wrong forum discussion, or on the wrong website - either a Bible Belt forum or School Children's website - don't be surprised if your blog continues to get content complaints. And in some cases, we'll see you in the forums.

Why was my blog deleted? I don't spam.

Be sensitive to both the stated, and unstated, policies where you post. If your blog contains controversial material, be very conservative about how and where you advertise. Publish properly targeted posts, with unique content, for the best future of your blog.

>> Top

Dynamic Template Instabilities Have Multiple Causes

For some time, we've been seeing reports, in Blogger Help Forum: Something Is Broken, about blogs using blogs using dynamic views, which display incompletely, and lack specific features.

Various blog owners have developed, and reported, a workaround to the problem, which involves using an unpublicised Blogger setting found in the template HTML code. This workaround sets a loading delay, known as Timeout.

There are several different causes of the dynamic view problem - some varying by the different blogs, others varying by the blog viewers - and some, varying by the Blogger / Google infrastructure. None of the causes will be universal in effect. This will result in varying success, when using a static Timeout setting as a workaround for the problems.

The current workaround for the problem - changing the Timeout setting - will have immediate success with some blog owners, partial or temporary solution with many, and no solution with others.

The inconsistency will come from the various causes of the latency - and from the variety of symptoms being reported. The latency is the cause for development of the Timeout tweak.


There are three details which cause latency, and which result in missing dynamic view content, of varying effect.

• Complexity of blog content - unique to each blog.
• Computer and network issues - unique to each different client computer.
• Server and network issues - unique to the Blogger / Google networks and servers which support dynamic templates.

Complexity of blog content is the only detail which can be consistently resolved, by a change in the Timeout. As any dynamic template blog becomes more complex, increasing Timeout improves the chance that all blog content - including gadgets and template customisations - will be packaged before the blog is viewed. Each blog owner will be responsible for evaluating the need for this workaround, on an ongoing basis - based on current blog complexity.

Computer and network issues causes problems, that may be partially resolved, by the blog owners. Each blog owner can make the Timeout relevant to the known audience. Any blog, with an audience known to have problems, can be tuned by the blog owner, as necessary. Each blog owner will be responsible for evaluating the need for this workaround, on an ongoing basis - based on the needs of the majority of the known blog viewer audience.

Overall load on the Blogger / Google networks and servers causes problems that cannot be consistently resolved, by the blog owners. It's possible that some portion of the latency problem is regional in nature - in that Blogger / Google resources may not be evenly allocated, world wide, to support dynamic template use. Blogger / Google will be responsible for evaluating the need for this solution - based on current complaint level and load on network resources.

Any action taken by Blogger / Google will present a challenge, for several reasons. Note the problems discussed here are unique to dynamic views - because of the unique design of the dynamic templates.

• The Timeout setting will have a global effect, for each blog with a problem - even though the problem may not be global.
• As more blog owners resolve their immediate problems, by increasing the Timeout, this will put more load on Blogger / Google resources.
• As more blog owners report their immediate problems solved, this will encourage still more blog owners to use dynamic templates, and to try increasing the Timeout on their blogs.
• More blogs using dynamic templates will put still more load on Blogger / Google resources - and this will necessitate still more Timeout increases.
• Some blog owners, using computers or Internet service particularly susceptible to causing the symptoms, may try the basic workaround ("500"), which may not produce results - and may falsely conclude that their symptoms are not caused by the problem. A few owners may persistently try "1000", or "2000" or higher - and may eventually observe an improvement - while other owners may not.

The only long term solutions to this problem lies with Blogger / Google. Blogger / Google has two options.

• Halt or restrict customisations of dynamic templates.
• Tune their network resources better, to make latency less of an issue.

The latter option will require supporting action, by blog owners and readers.

• People who view blogs using dynamic templates have to tune their own computers and networks, so they do not contribute to the problem.
• Some blog owners may have to accept reality - that their reader audience simply can't be properly served, given the level of customisation required by their blog design.

The bottom line is that some blogs will never be properly served, if the owners insist on using dynamic templates, and customising uncontrollably. Blogger / Google cannot provide the universal solution.

>> Top

Dynamic Template Instabilities Have Multiple Symptoms

Recently, we've been seeing a few reports, in Blogger Help Forum: Something Is Broken, about blogs using dynamic templates, which display incompletely, and lack specific features.

Various blog owners have developed, and reported, a workaround to the problem, which involves using an unpublicised Blogger setting found in the template HTML code. This workaround sets a loading delay, known as Timeout.

The currently recommended Timeout setting will force a fixed delay on blogs using the workaround, which may not be 100% effective in all cases. The effectiveness may vary, according to the specific problems reported by the various blog owners.

Problems reported by blog owners, which involve dynamic templates, center around several distinct areas.

• Absence of comments, displayed after the posts.
• Absence of multiple gadgets, in the popout sidebar.
• Absence of Pages entries in the display header bar.
• Absence of Posts ("No Posts Found"), with blogs heavy on photos.
• Absence of template tweaks, applied using "Add CSS".
• Absence of template tweaks, applied using "Edit HTML".

Each of these different symptoms will be caused by different needs, in publishing a blog - and the different symptoms will be observed by owners with different technical skill level.

Absence of multiple gadgets, in the popout sidebar is probably common to most blogs, as most blogs have more than one accessory gadget. Blog owners reporting this problem may be of very low technical skill level - and will likely have problems applying the workaround.

This problem may be more common than problem reports would imply - as not everybody with a blog, with this problem, will observe the unusually short accessory tab when the accessory bar is docked.

Absence of comments, displayed after the posts will be observed by blog owners who focus on comments, as part of their networking strategy. This will generally involve the more popular blogs (with lots of comments, making their absence more noticeable). Blog owners reporting this problem may be of low technical skill level - and may have problems applying the workaround.

This problem may be more common than problem reports would imply - as not everybody with a blog, with this problem, will observe the absence of comments, displayed after the posts. Some owners, with blogs which receive less comments than others, may not even care.

Absence of Pages entries in the display header bar will be reported by blog owners who have setup a complex structure of dynamic and static pages, and a Pages index to index the pages. The blog owners reporting this will have medium skill level, with the ability to use the Pages wizard. These owners may not necessarily have the ability - or desire - to use the Template Editor effectively. Some of these owners may have problems applying the workaround.

Absence of Posts ("No Posts Found"), with blogs heavy on photos, will be visible in blogs using "Flipcard", "Snapshot", and similar views. Blog owners reporting this problem may be publishing photoblogs. These blog owners will be those who spend a lot of time providing photos - and who may not notice other symptoms, like missing header or sidebar features. These blog owners may be of low technical skill level - and may have problems applying the workaround.

Absence of template tweaks, applied using "Add CSS" will be reported by blog owners who carefully applied appearance and style tweaks, using the Template Designer. The blog owners who apply these tweaks will have medium technical skill level, and the ability to use the "Add CSS" feature in the Template Designer. Some of these owners may have problems applying the workaround.

Absence of template tweaks, applied using "Edit HTML" will be reported by blog owners who customised the blog appearance, using the Template Editor. These blog owners will be of the highest technical skill level. These owners should have no problem applying the workaround.

With the assortment of problems to be fixed by Blogger Engineering, we will likely see each problem worked on, separately. As each problem is solved, we'll likely see new problems become more visible - and existing problems become more urgent, in the eyes of the blog owners.

The number of different possible symptoms, in combination with the number of possible causes of the problems, will create an apparently infinite number of differing complaints - and inconsistent visibility of the problems. Blogger Engineering will be busy, for a while, resolving these problems.

>> Top

Dynamic Templates, And Network Problems - #2

We're been getting problem reports in Blogger Help Forum: Something Is Broken, from various dissatisfied blog owners, who chose a dynamic template for their blog.

The problems reported involve various symptoms.

• Blogs displayed will lack various gadgets, in the slideout gadget bar.
• Some blogs, when customised, will display using default layout and template settings.
• Some customisations, applied recently, just won't show up.

Various blog owners have discovered a solution, based on code present in newer dynamic templates. This solution has been publicised, in forum discussions - and in various blogs and web sites.

<script language='javascript' type='text/javascript'>
      setTimeout(function() {
        blogger.ui().configure().view();
      }, 1000);
</script>

The solution, as proposed, involves a very simple change - but the change won't be immediately, or permanently, 100% effective.

The solution, being publicised by various blog owners and forum helpers, involves a very simple change, using the template editor.

Once you have a secured a back up of your blog template, click on Edit HTML and you will see the html editor come up. Scroll down to the bottom of your template to where you see code that looks like this.

<script language='javascript' type='text/javascript'>
      setTimeout(function() {
        blogger.ui().configure().view();
      }, 0);
</script>

Change the 0 to 1000 so it looks like this.

<script language='javascript' type='text/javascript'>
      setTimeout(function() {
        blogger.ui().configure().view();
      }, 1000);
</script>

Click on Save Template.

Here, as always, I will strongly recommend that you backup the template, twice - before, and after, you make this template change.

This solution - changing the Timeout setting - will have immediate success with some blog owners, partial or temporary solution with many, and no solution with others.

The number of possible causes of the problems, in combination with the variety of possible symptoms, will create a visibly infinite number of differing complaints - and some complaints will continue, even with the workaround applied. Blogger Engineering will be busy, for a while, resolving these problems.

Once again, I'll suggest that you consider the functional and historical reasons for existence of the dynamic templates. Consider exercising some restraint, when customising your blog. Be part of the solution.

>> Top

Dynamic Templates, And Network Problems

We're getting a few problem reports, in Blogger Help Forum: Something Is Broken, from blog owners who chose a dynamic view for their blog.

My layout has one colour - yet when I view my blog, it's another colour. The accessory bar is missing gadgets - and there are various tweaks missing. I tried updating, using the Template designer, unsuccessfully. When I finished updating, the preview looked good - but when I saved and viewed my blog, it was still incomplete.

This blog owner, like many owners, may not understand the unique design of the dynamic templates - nor how the design affects what is seen by the readers.

The complexity of a Blogger blog is not truly appreciated by anybody, until possibly when a blog has to be backed up or re built.

There are many components of a Blogger blog - not just the comments, posts, and template.

• Accessories.
• Comments.
• Decorations.
• Gadgets.
• Posts.
• Layout / Template.
• Third party hosted accessories and tweaks.
• URL.

With a non dynamic ("Designer" or "Layout") template, the blog is packaged for viewing, from the many components, on the Blogger servers. When you get a page of a blog, on your computer, it's already packaged - and what you see is immediately ready for viewing.

With a dynamic template, the comments, the posts, the template, and the various other components all arrive separately from the various Google and non Google servers, which provide the blog content - and the blog page is packaged, for viewing, on your computer.

If any piece of the package does not arrive at your computer as soon as the other content, the blog page is packaged, from what is available - but it's going to be missing pieces.

This is why some folks see the posts without the tweaks applied using Template Designer - or the layout lacks a key improvement made using "Edit HTML" - or maybe the accessory bar is short. A piece of the package did not arrive, before the packaging was complete - and the blog was displayed, incomplete.

The alternative would be to have the packaging process wait longer - but how long do you want to wait? What happens if your computer (or your reader's computer) cannot connect to one key Blogger server, to download that one essential component?

How long should a moron wait, before giving up, and asking for details? Or at least clearing cache, and restarting the browser, before trying again?

Packaging a blog page, on the reader's computers, has benefits - and drawbacks. If you occasionally see an inconsistency in your blog, imagine your various readers, with some seeing your tweaks and others seeing only a basic (Blogger standard) template - and you never knowing what everybody is seeing.

For best results, you need to keep the dynamic views simple.

---

(Update August 2013): We have a workaround to the problem - but the workaround is not going to be 100% consistently effective. The lack of consistency is going to be especially noticeable, because of the several different symptoms being reported.

---

>> Top

Why Does Referer Spam Get Reported, Primarily, By New Blog Owners?

One of the details of referer spam, that intrigued me for a while, involved who was reporting the spam.

Most - but not all - referer spam is reported by newbie owners. People who just setup a blog, and are anxiously waiting for their first readers outside their own country, are suddenly astounded

Wow, thousands of people are reading my blog - from China and Russia! I am an international celebrity, in my first week!!

The euphoria quickly vanishes, when told in the forums

Nobody is actually viewing your blog from these sites - and nobody knows about these links but you, since only you can see your Stats logs.

The general response to the cold water, dashed in their faces, is generally acceptance

Thank you for the prompt and informative reply - I'm very relieved to learn that the site is not actually linking to my blog.

The latter is the general response - but not the only response. Nobody should be surprised at that, as not everybody is the same. What is surprising, though, is who is not so accepting of my advice.

Of the people who do not seem to appreciate my advice - that the owner of the new blog is not an immediate international celebrity - not all of them are actual first time blog owners.

Many blog owners, who scorn my advice, turn out to be long time blog owners.

You are an idiot! I have other blogs, which I've been publishing for years - and none of them get this crap! How dare you tell me that this traffic is not targeting my new blog, intentionally?

Why would people who have published other blogs not see the spam traffic, in their other blogs? Particularly in other blogs that are well known, by the world, in general? And why would experienced blog owners not know of - or even believe - my advice?

The principle of Occam's Razor tells us to look for a simple explanation, to the questions. Instead of concluding that so many experienced blog owners are morons - or do not check their Stats logs like everybody else - or wondering if referer spammers carefully tune their spammy activities to only attack new blogs - the simple explanation is that every blog is subject to referer spam, in the same volumes.

Not every blog owner sees referer spam, in their Stats logs, simply because the volume of referer spam is not so heavy, compared to genuine traffic. If I check the Stats logs for this blog, repeatedly, throughout the day, I can generally find the currently mentioned spam domains, reflected in my pageview counts.

To reliably find the referer spam attacking my blog, I have to check my Stats logs frequently. In my case, when I note the domains in question, they will be listed in the "Now" time range - and occasionally in "Today" - when "Now" reflects early morning UTC (just after the daily counts reset).

If the referer spammers attack this blog during any other time of the day, the volume of legitimate traffic generally exceeds the referer spam traffic, any time outside "Now". Thanks to the limited function of the Stats logs, referer spam is simply not always visible, because legitimate traffic is more visible.

Thanks to regular changes by the spammers, and to ongoing spam blocking by Google, the same domains are not active for more than a week or so. The "Week" and "Month" normal volumes, for this blog, simply exceed the referer spam volumes.

And that's the case for everybody's blog. Check the logs for your blog, if you don't believe me. Just check frequently, and regularly, during a week, for the most accurate conclusion.

And that brings me to my last bit of advice, about the spam.

Concentrate on publishing your blog, and getting legitimate traffic - and the referer spam will not be an important issue.

That's not condescension, or snark - it's simple truth.
>> Top

Stats Displays Pageviews - Not Unique Visitors

Too many blog owners do not understand the unique capability of Stats - nor do they understand its limitations.

We see the periodic question in Blogger Help Forum: How Do I?.

How do I find out how many actual people are viewing my blog?

Stats does not provide unique visitor counts - Stats provides pageview counts.

It's simply not possible to determine, with 100% certainty, how many different people are viewing your blog.

Consider these environments, where multiple locations, or people, are involved.

• A single person can use multiple computers, simultaneously.
• A single person can use a mobile computer, moving from one cellular connection to another.
• Multiple people can view the same computer, simultaneously.
• Multiple people can share the same computer, serially.
• Multiple people can share the same Internet connection, serially.

There are other visitor meters besides Stats - and some other such products will provide "unique" visitor counts. Each product, which claims to provide "unique" visitor counts, will do so based upon specific limitations and techniques.

One of the most obvious ways to determine unique visitors is by comparing IP addresses. Surely, two pageviews from the same IP address will be one person - and two pageviews from two different IP addresses will be two people, right? Wrong.

• One person can use two computers, simultaneously.
• One person can use a mobile computer, moving between two locations (each location will have a different IP address).
• Two people can use the same computer, at a library or Internet cafe.
• Two people can use the same mobile Internet connection.

In each of these cases, one person may look like two people - or two people can look like one person.

Some visitor logs will drop cookies onto a computer. Detecting a cookie already in place, this indicates one person, returning - and successfully dropping a cookie, indicates a different person, right? Wrong, again.

• Again, a shared computer is a possibility.
• Not all computer owners will permit unknown websites to drop cookies, onto their computers.
• And some owners, when they permit cookies on their computers, will periodically clear cookies.

Some very sophisticated visitor logs can compare demographic details, similar to the Stats Audience display. Besides IP address, what can be determined?

• Operating system, brand, model, and version.
• Browser brand, model, and version.
• Maybe, location (possibly determined by IP address, again).

And finally, some visitor logs will compare IP address, over a given time interval. Arbitrarily deciding that all activity from the same IP address, over a period of 30 minutes, represents a statistical "single person", is a known technique. This is not a legally significant technique, however.

The bottom line is, as I state repeatedly, you simply cannot compare numbers from any two visitor logs or meters, with any degree of usefulness. Each product will have its own way of determining unique visitors - when they even suggest a "unique" visitor count. Stats simply avoids the uncertainty, and only provides pageview counts.

>> Top

Fluctuations In Reader Activity Level Are Normal

One sign of panic, seen regularly in Blogger Help Forum: Something Is Broken, comes from people who spend a lot of time viewing their Stats logs.

My pageview counts are always going up and down. Why is Stats so flaky?

It's good to monitor your reader activity - sometimes this will warn you of a major problem in the Internet, or with Blogger. But keep it in perspective.

No matter what time range you view, in Stats - "Now", "Day", "Week", "Month", or "All time" - you can expect to see fluctuations - peaks and valleys - in pageview counts.

• If you spend time working on your blog this week, and your work is successful, your readers may enjoy the blog more next week. Conversely, if your work is unsuccessful, they may enjoy it less.
• As Google deals with the constant waves of referer spam, you'll see a drop in counts across all time ranges. And as new referer spam campaigns come online, you'll see the counts rise.
• Unless your blog is completely homogenous across all world wide cultures, you'll have one or two predominant audiences. Your audiences will eat, sleep, and go to work - and all real life activity will affect their viewing of your blog.

It's good to watch the counts, understand your audience, and be prepared to take action if you see a significant rise or fall - but don't obsess over the details.

Remember that your readers will appreciate content, so keep publishing to the blog. And, learn to understand the trends.

And, to best avoid confusion, use more than one visitor log / meter.

>> Top