Google Buzz Teleseminar with Chris Lang

Posted on by

Tonight we hosted a one hour Teleseminar with Chris Lang, the “Nostradamus” of Google.

Over the past several weeks Chris has had several of his WordPress Blogs that are (were) hosted on GoDaddy hacked into with the Base64 virus not once, but three times.

The most recent attack was just hours before his Teleseminar, so I really appreciate his commitment and being able to be our guest.
During Chris’s one hour presentation, Chris discussed:

  1. If you’re hosting WordPress sites on GoDaddy, Blue Host, Network Solutions what you need to know about the recent attacks and how to fix your blog/site if it becomes infected.
  2. Chris also discussed the migration of Facebook users to Google Buzz because of privacy concerns and how Google Buzz is shaping up as a social media platform.
  3. Why it is important to become familiar with Google Buzz if you own a local business and how tips using Google Buzz and Google Maps to increase business.
  4. Chris also revealed for the very first time some new tricks and tips on how to use Google Buzz and YouTube in your Internet Marketing.

Then at the end of Chris’s presentation he answered a number of questions our members had regarding the recent WordPress security issues and other questions about Google’s social media network.

You can listen in on this Chris and his teleseminar by using the player below:

Certified Master SEO Instructor by the Search Engine Academy and CEO and founder of SEO Training SW.
Roy Reyer
Roy Reyer
View all posts by Roy Reyer
Roy's website
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

13th May 2010 8 Comments

8 Responses to Google Buzz Teleseminar with Chris Lang

Leave a Reply

Your email address will not be published. Required fields are marked *






Webinar Replay How to Increase Conversions and Traffic to Your Website

October 16th, 2014


Warning: Use of undefined constant php - assumed 'php' (this will throw an Error in a future version of PHP) in /home/customer/www/ on line 55