Tag Archives: Wordpress Error

Organic SEO Lesson

Search engines want true organic listings, and for some reason a lot of people struggle with this concept. If you write an original article you are creating an organic (natural) post. And the results you achieve might just surprise you. And yes, this is probably harder for me as a programmer than you can imagine. I tend to want to program my results, but, over the last year I have learned the value of just letting the blogging flow.

I have 2 clear examples of writing a post that was influenced by my own circumstances and imagination that were rewarded in the SERPS.

  • The first was written 2 months ago and included a video. I was just trying to relay my thought on how we each respond to making mistakes and that we need to be open minded while taking responsibility for our own actions. This post is ranked # 2 on Google for open minded vlogging and # 14 for the term open minded blogging. The title was “Making mistakes and being open minded“. And yes I gave some thought to the SEO in the post, but, I was still surprised to see people coming to my site for the above mentioned terms.
  • Organic SEO

  • The second post was ” WordPress XML Parsing Error” and landed pretty good for several terms including, WordPress error, WordPress XML Error, and WordPress Parsing error. The post was basically a log of troubleshooting an error I was having with WordPress. Yes I did a little SEO on the post, but the results once again were above my expectations.

As a side note, the only reason I knew of these results is because I evaluate my analytics to get a better understanding of how people find and use my sites. This work is probably one of the keys to my success, as I know it is not my pure writing skills.

The moral of the story…..

Be natural, be organic.

It is good to do the SEO work, but do not JUST let the SEO drive the Content.

WordPress XML Parsing Error

No sooner did I write the post about troubleshooting I came across a WordPress error that took way more time to solve than I expected.

One thing I know as a programmer is that every single character in a file is critical. I can not even guess how many times a simple question mark or apostrophe has caused me to lose hours of time trying to find. And here is a perfect case of troubleshooting a WordPress error that was so simple, yet so hard. The error was an XML Parsing Error.
I have a new site (NonPartyPolitics.com) that I have been working on and I realized the RSS Feed was not displaying, the following error was popping up.

XML Parsing Error

Looks pretty obvious, there was an error at line 2, column 1. Step one was to see what was happening, so the first thing I did was look at the source of this page. Nothing jumped out at me, so I loaded a working WordPress site, pulled up the RSS feed and looked at the source, I placed the 2 files side by side and there it was. On the feed with the error there were 2 blank lines before the code. Interesting. I then pulled up the home page for both sites and the same thing, there were 2 extra blank lines on the home page source. This told me that the problem was probably not in the RSS code, but it could still be in the code somewhere.

The next logical step was thinking of what I changed last. I really had not done much outside the template except installing a couple plugins. So, I turned off all plugins. Now the hard part was having a little patience. I could see that on the home page the 2 blank lines were now gone, but I had to edit a post and wait for the feed to catch up.

Sure enough that was it, 2 blank lines were gone in the feed. Now, which plugin?

Here is a little logic for you, if I have 2 blank lines, and I know a plugin is causing it, all I need to know is which plugin is issuing 2 extra carriage returns. The key to this is to know that I was not looking for the plugin actually writing the blank lines, I was looking for a plugin with 2 extra carriage returns. And I found the culprit.

I am not going to call it by name because the plugin worked fined on other sites and it did not download from the original like this. Either I did something to cause this problem, or it was just a fluke.

Here is the plugin before I fixed it…..

Plugin1

and here is the plugin after the fix…

Plugin 2

So there we go, a real WordPress troubleshooting case solved. All of that because of 2 extra carriage returns.

Make sure when you are working with code you are aware of every character and every space!

Import Blogger to WordPress error

If you have tried to import a blog from Blogger to WordPress 2.2 you may have been frustrated by an error. The system just returns a message that it can not login to your Blogger account. There is a very simple fix for this error that requires a one character change in the wp-admin/import/blogger.php file.

On or around line 84 there is a reference to www2.blogger.com, change this to www.blogger.com and the import should work.

I have done several imports from Blogger to WordPress and the system has been working great.