The Real Blogger Status

Ever since 2009, when Blogger introduced the Stats visitor activity counter , blog owners have been reporting inconsistencies between Stats and other visitor activity counters . Recently, Google+ changed their +1 counter. Now, we wait for Blogger Engineering to update their +1 per post display counters, which use the +1 counts from Google+. Blog owners continue to report various Stats inaccuracies - such as discrepancies between Stats pageview counts, and the various social sharing counters. They fail to observe the functional differences between the various activity counters - and similarly, between Stats counts and social sharing metrics, such as Google+ +1 counts.

With the pre 2016 Followers gadget, the Followers population for a blog was managed through an Options link on the Followers gadget . This required the blog owner to sign into the Followers gadget, to access the Options link. Authentication - and an owner specific Options menu - is no longer a pert of the Followers gadget. It is possible to Block Followers, from a blog - the option is just not part of the Followers gadget, any more.

We're seeing a problem with Blogger Hosted Comments - and "Bad Request Error 400", following the use of the comment "Preview" feature. When a blog owner or reader composes a long or important comment, use of the Preview feature is normal. Right now, after hitting "Publish", following a successful Preview, one frequently sees the bad news. Bad Request Error 400 There is a workaround for this annoyance - and it's not difficult to use.

One of the most obscure Blogger error messages - next to "Another blog ..." - is the monolithic advice seen on main page display of some blogs. No posts. or maybe There's nothing here! What can you say, to a blog owner who has started a new blog, and spent days publishing blog content - only to view the blog, and see "No posts." - or "There's nothing here!"?

Many blog owners want the legendary wealth, from publishing a Blogger blog, and adding AdSense ads. Not everybody understands the AdSense review process - and the fact that "Congratulations!" is only the beginning .

The Internet is diverse and large - and the Internet directory system, aka the DNS Infrastructure, supports the diversity and size. When we setup a new domain, the registrar frequently advises us to wait patiently, before continuing. Congrats on your new domain! Now, we suggest that you wait 24 - 48 hours for the new domain to propagate, before trying to publish to the domain. When we update a domain - and add or delete a single DNS address - we won't always get advice about waiting, from the registrar.

As most of us know, Blogger HTTPS support does not include custom domain publishing . The advantages offered by HTTPS access are widely advertised - and have led to envy between blog owners who publish to custom domains, and native BlogSpot blog owners proudly advertising their new HTTPS connectivity. Long ago, we saw possibly malicious code which helps our readers avoid using country code aliases , to read our blogs from an aliased country. Recently, there was dodgy code which blocked HTTPS mode , to read a customised blog. Now, we have custom code to force HTTPS access, for BlogSpot published blogs.