Skip to main content

Dynamic View Blogs Have Limited Recovery Potential

We deal with a lot of "lost blog control" complaints, in Blogger Help Forum: Get Help with an Issue.

Lost blog control complaints, that involve blogs published using a dynamic template, are not easily resolved.

There are several types of control / ownership problems, that are not easily resolved, for blogs that use dynamic templates.
  • Blogs deleted by Blogger, as malware or spam.
  • Blogs with ownership lost, by the owner.
  • Blogs locked by Blogger, for suspicious / unusual account activity.

We see this a lot - and this is a real problem, with a blog that used a dynamic template.

Blogs deleted for abusive content can't be triaged as easily.

Triage of blogs deleted by Blogger, whether deletion was righteous or spurious, is most successful with blog content examined.

With a deleted blog, content can be examined only using cached copies. Content, in blogs published to a dynamic view, is not always cached - because it's based on the blog newsfeeds, retrieved as the blog is being viewed.

This is a dynamic template blog, displayed from cache.

If cached feed content can't be found, triage is useless. Abuse review must be submitted blindly, with no examination possible. Successful review depends completely upon observation by Blogger Policy Review, and no suggestions by forum members are possible.

Blogs with ownership lost cannot be researched.

The first step in recovering ownership, for many blogs, requires a look at the owner profile information, in the blog source code - and one or more possibly overlooked Blogger / Google+ profiles. The owner profile ID is not frequently seen in dynamic view source listings, however.

Without any ability to identify the owner profile, ownership recovery is left solely to monolithic options provided by "Forgot?" and "Having trouble?".

Blogs locked for suspicious / unusual activity are more complicated.

If a blog, locked by Blogger under suspicious / unusual account activity lock, cannot have the owner identified, the owning account will remain locked. If the owner cannot identify the account, account review can't be requested.

Without the ability to research ownership, using profile information in the source code, the owning account, and blog(s), will remain locked. The owner must log in, in a blind login attempt - frequently requiring brute force technique. Incautious brute force can lead to more locked accounts.

Suspicious / unusual activity lock may be more likely, with dynamic template use.

The original market for dynamic templates was casual / new blog owners. Casual / new blog owners are more likely to attract brute force hacking attacks, by casually revealing account details.

With brute force hacking more possible, account / blog lock becomes more likely also.

The bottom line.

As with any blog in general - but even more so for blogs using dynamic templates - blog ownership details must be retained by the owner. When ownership information is lost, control of the blog will be lost also - and dynamic templates have less chance of successful recovery.

Owners of blogs using dynamic templates should be more strongly urged to use Google 2-Step Verification.


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: