WPDude not only impressed me with his considerable technical prowess, but also with his integrity and commitment. He really is a pleasure to work with.
Continue Reading »WPDude not only impressed me with his considerable technical prowess, but also with his integrity and commitment. He really is a pleasure to work with.
Continue Reading »Thank you for making this such an easy experience to move to WordPress from TypePad. I found it much easier for you to get me going for a small fee than spend hours trying to go through the WordPress codex.
Continue Reading »A couple of weeks ago, I was at my wits end. My blog posts were not showing up in Firefox and I needed help, more than you can imagine. None of the tech people that I know good provide me real assistance so, I used my good friend Google. I found WordPress Dude, Neil Matthews. [...]
Continue Reading »Neil, I just wanted to say thanks for going above and beyond my expectations with our wordpress consultation the other day. You not only fixed my screw ups, but you also showed me where I was going wrong and how to properly operate the new blog template on a day-to day basis, as well as [...]
Continue Reading »I must say that Neil AKA WP Dude is customer service oriented and commited to building a strong and honorable relationship with his clients. I’m far from tech savy and was in need of assistance with updating my version of word press. WP Dude went above and beyond the necessary, by updating all of my [...]
Continue Reading »After spending 3 months setting up my new site I was stuck on the last details to get the site up and running. I was thrilled to find Neil Matthews who took care of the technical stuff to make my site work better so I did not have to spend another 3 months learning things [...]
Continue Reading »
In my post yesterday I wrote about taking 404 errors and using them to your advantage, in this post I want to build on that and talk about tracking down 404 problems and fixing them.
404 is the error returned by web servers to browsers if a file cannot be found. This is a standard error and is usually a dead-end on a website.
We need to fix certain 404 errors because people are coming to your site expecting to find content but are getting errors instead, this does not look good to fickle blog readers, the slightest thing can make people unsubscribe or not come back to your site.
How do you find what URLS are causing 404 errors on your site? You look in your logs. You should have a log file of all the accesses of your site, these will show what page, the referer, what user agent (browser) and many more things. The thing we are interested in is the http return code, searching for 404 will show your problem URLS.
Each hosting provider will have a different config for their logs, please refer to their documentation on how to review your access logs.
Here is a sample from my log file, I have highlighted the 404 error message and the page/post name.
“150.70.xxx.xxx – - [19/Nov/2009:10:28:25 -0700] “GET /hire-me HTTP/1.0″ 404 17600 “-” “Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)”
Here I can see that there was a file not found error trying to retrieve the page hire-me. This is not good, a potential client is getting a 404 because I have renamed that particular page.
Once I find a 404 error I want to fix it by redirecting to a live page. I know what you are thinking, he is about to tell us about a plugin after he had us ferreting about in our log files, you are quite correct, and it’s only because I care and want to give you a holistic view of your 404 problems that I asked you to look in your logs
I use a plugin called redirection which (as the name suggests) redirects URLs to other URLS. Check it out at http://urbangiraffe.com/plugins/redirection/
The beauty of this plugin is that it has a 404 detection function. Using that I can very quickly find out which URLs are causing me problems and then fix them. Below is a screenshot of my 404 for today.
Both of these URLs are ones I have renamed, I want to fix the 404 errors by redirecting them to the new page.
Using the redirection plugin I can set up a URL interceptor which will capture all visits to the 404 URL and do a 301 redirect to a new page or post. 301 redirects are cool if the visitor came from a search engine, because next time you site is indexed, the incorrect URL will be updated to the new one.
http://wpdude.com/hire-me (hint check the browsser bar for the new URL)
If people are getting 404s because of typos or things like that I do not recommend creating redirects, only redirect things which are real issues like renamed pages
Get your 404 errors fixed, it makes you look more click and professional with an increased chance of subscription or other action.
Would this be good to use when converting a traditional website to WordPress, e.g., “services.html” is now just “services”?
[Reply]
Neil Matthews Reply:
November 20th, 2009 at 2:20 pm
It would indeed. I have setup a test redirection, if you go to wpdude.com/janet.html it will redirect to my about page
[Reply]