Attention: If you are using WordPress, then this will be the most important page that you have ever read. Period.
If you use WordPress for your blogs then you likely fall into one of two camps:
1. The Ideal Blogger:
You keep all of your blogs up to date regularly. You always install the latest security patches, versions of plugins and themes.
2. The Normal Blogger:
You only ever upgrade your blogs when you login to post and sometimes not even then.
If you fall into the first group, then I am surprised and you are amongst the top 2% of bloggers. Or more likely, you already own a copy of WP Pipeline
With WP Pipeline… No longer will you have to worry about:
- upgrading plugins
- upgrading themes
- upgrading WordPress software
- creating backups of blogs
- creating duplicate or clone blogs
- finding themes/plugins that you have purchased
and so much more!
Find out more:
Do you make money from your WordPress blog?
Even if you don’t make anything yet from your blog, you could end up losing more than just a blog if someone hacks your WordPress installation.
WordPress has long had a history of security loopholes, and many of the updates are designed to plug those loopholes.
Many bloggers have built up a blog network of sites that are making them commissions only to have them get hacked and either taken down or turned into a profit center for the hacker. Sometimes, the hacking can cause the blogger’s hosting account to be suspended or shut down, because the hacker can also access the cpanel of the hosting account.
This can mean losing multiple sites, lost commissions and lost money because you were paying for a hosting account that is not even operational.
Luckily, we have people who are always working hard to beat the hackers. The result of this is WordPress Shield! Take a look at it and see how much it can help you with your blog security:
Comment spam is the fastest growing issue for bloggers. It seems like the minute your blog is live, the comments come pouring in, people ranting and raving about how well written your blog post was, even though it is still the Hello World post that comes with WordPress!
Your comments must show that you have read the post you have commented on. If you show up, leave a generic comment and never come back, you are just like the rest of the spammers out there.
- Take the time to read the post. Comment on the content. Be real and use your real name for the comment. If you use your keywords, chances are you will be marked as spam.
- Be controversial! If you disagree with what you have just read, go with it. Tell them why you disagree, bloggers (most of the real ones) want some controversy to get others involved. My friends Ross Goldberg and Rick Butts once had a comment war where each of them held an opposing viewpoint that polarized the readers to choose one side or the other, and comments came from both sides in droves! This ended up helping both Ross and Rick since the commenting continued on each of their blogs long after the original post.
- Help the author. Offer suggested resources for readers to get more information (not your affiliate link or your own blog) that shows your knowledge of the subject. Often, the author may not have known about the resource and will be glad to hear about it.
Obviously, you can find other ways to comment that will be appreciated by the moderator of the blog you are targeting. By all means experiment and let us know your results. The more people comment on my blog, the more I will continue to look for reasons to write.
Facebook And WordPress
Want your Facebook Fan Pages to be an extension of your blog? How about requiring people to be members of your Fan Page before they can read your blog? I am going to be interviewing George Curtis and Evan Mugford on a special edition of “Blogging With Micheal” on Blog Talk Radio. Join us for an hour of high quality content on why and how you should be using Facebook with your blogging. You can listen via the web, or you can dial [(646) 478-0874] in at 1PM Eastern on Wednesday May 18, 2011. You can also listen to the recording from this page as well: