Skip to main content

Following / Friend Connect, Stats, And "opensocial.googleusercontent.com"

Some blog owners spend hours pouring over the activity records, Blogger Stats display, and / or visitor logs for their blogs. Sometimes, they see unexplained details which cause needless worry.
I clicked on a link in Stats, that referenced activity from "opensocial.googleusercontent.com", and got "Page not found". Is somebody hacking my blog?
and
What is "opensocial.googleusercontent.com"? I see that URL a lot, in my visitor logs!
Fortunately, this is a slightly less mysterious and sinister story.

Take a look at the Following community on your blog, or any other blog that interests you. See the icons, of the Followers? Click on one, and watch the contents of the browser status display (generally, the lower left border of the browser window), closely. As the large white popup window opens up, in the middle of your browser, you'll see "opensocial.googleusercontent.com" mentioned in the status display, briefly.

The popup window, with the Followers profile - including a list of blogs owned and / or Followed - is hosted from "opensocial.googleusercontent.com". That's the purpose of Following - giving people a chance to surf from blog to blog, using personal recommendations (lists of Followed and owned blogs) from the Followers and blog owners.

When you surf blogs using Following, you're opening these temporary popup windows, and you're generating temporary pages displaying the profiles of the Followers. When you click on a URL that looks interesting, to check out somebody's blog, you're generating an inclick ("referer entry"), from "opensocial.googleusercontent.com", in the Stats / visitor log for that blog.

When you close the popup window, that temporary URL goes away. Separately, and later, when you examine your visitor log, you see these "opensocial.googleusercontent.com" referer URLs, you click on one, and you get "Page not found", it's because that was a temporary page, hosting the popup window. That page existed in cache, on the computer owned by someone who just visited your blog - and it's long gone by the time you view your Stats display.

The bottom line is that these mysterious log entries mentioning "opensocial.googleusercontent.com" are the result of activity from Followers, visiting your blog. It's good to worry about hacking - just don't worry needlessly, from seeing "opensocial.googleusercontent.com" in your visitor logs. Get back to work, on your blog.

>> Top

Comments

Tito said…
Nice post.
Thaanks!
CraftyMummy said…
Thanks for the explanation.
I'm curious though: could the same thing occur when a reader clicks through from a comment I've left on a blog post with my blogger profile?
Jessi said…
Thanks so much for the explanation! I had no idea and it was driving me nuts!
Thanks for this useful post. In fact, I am not the only one got this.
Billy Kravitz said…
but is that URL in any way a form of referral spam, or could referral spammers 'ride in' on it?
Boy Bastos said…
doeas it mean that if you have a lot of these like a few thousand... most of your followers are actually reading your blog everyday?

Popular posts from this blog

Adding A Link To Your Blog Post

Occasionally, you see a very odd, cryptic complaint I just added a link in my blog, but the link vanished! No, it wasn't your imagination.

What's The URL Of My Blog?

We see the plea for help, periodically I need the URL of my blog, so I can give it to my friends. Help! Who's buried in Grant's Tomb, after all? No Chuck, be polite. OK, OK. The title of this blog is "The Real Blogger Status", and the title of this post is "What's The URL Of My Blog?".

Add A Custom Redirect, If You Change A Post URL

When you rename a blog, the most that you can do, to keep the old URL useful, is to setup a stub post , with a clickable link to the new URL. Yo! The blog is now at xxxxxxx.blogspot.com!! Blogger forbids gateway blogs, and similar blog to blog redirections . When you rename a post, you can setup a custom redirect - and automatically redirect your readers to the post, under its new URL. You should take advantage of this option, if you change a post URL.