WordPress Plugin Security Concerns

The true definition of a WordPress Plugin is code that goes into the core of your site and allows you to change appearance, security, or other settings.  With the access and amount of plugins that are out there, is there any way to be sure they are secure?  I have posted several times about plugins that have security vulnerabilities that allows hackers/script kiddies to download your wp-config.php file, gain access to your root, or make themselves an admin.  Is there truly a way to protect yourself from probing attacks?

As I write this post, I am reviewing probing links into my site:


Full Post Here

Keywords: Just what is the right amount?

I hear this so often that I felt the need to create a post about it.

“So I have this topic I want on the first page of Google results.  How many times should I use the keyword on my page?”

There are opposing views on this topic, depending on who you talk to, past experiences, the keyword, Google total results… the list goes on.  Is there truly a correct answer?

I take the view of this:  If I am holding a conversation with another person about a specific topic, how often should I use the same keyword?  I know.. this is an open-ended way to bring the topic about.. you just want results.  Maybe there is just a magic formula that someone who is a search engine optimization specialist should be able to quote.  In reality, if there was a formula, it would work for one search engine, not all of the major ones.

Take the previous paragraph.  I used the necessary verbiage to get the point across.  I did not fluff, stuff keywords, use black hat tricks in the paragraph...

Full Post Here

Some of the latest issues effecting WordPress Security

So I have been preparing for some major things with my full time job.  I left the site up and have not refreshed things in a while.  Not to say that I did not update the plugins, themes, and core WordPress; that is a requirement of any site.  However content and posts were idle for a few months.  This post shares some insight from my backend, where probes went, and now the IPs that are at fault.  I share this information in the hopes fellow site builders can be proactive, possibly by banning the IP address prior to defacing attempts, or possibly just raising the red flag just a little bit more as you watch hits coming in to your site.  Whatever the case, here is the long list:

Report for

Records in database: 25
Latest hit: July 15, 2015 14:18:02
First hit: July 15, 2015 14:17:45
User agent(s): Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_6) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.12 Safari/534.24
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.66 Safari/535.11
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_0) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.0 Safari/534...
Full Post Here