Sunday, October 12th, 2008
This is a follow up post to my previous posts about my friend’s Google ranking drop. As you may remember, his Google ranking was restored a few weeks after he blocked the proxy website from copying his entire website and submitted a Google reinclusion request. As you may have guessed, he was quite thrilled to see his SERP ranking shoot up again.
Well, as luck would have it, I received a phone call last night from my friend telling me that his website was bombing again. I Googled his favorite keywords and they seemed to rank fine over at my end, but he explained that he traffic stats from Google was flat. They nosedived a day or two ago. I chalked up the results I was getting to Google adjusting the results.
This new twist got me thinking. What in the world could be making this website’s ranking bounce around like this? Looking back, the proxy website may not have been 100% at fault. There has to be something else.
I began doing a little research and learned about few things about duplicate content. The reason I looked at that particular area is because there is absolutely nothing else I can find wrong with this website. Duplicate content seems to be a rather popular culprit.
I came across a pretty well laid out website called “Google Rankings Diagnostics” that describes a whole heck of a lot of issues you might be having with your website. This website validated what I pretty much already knew…that if you have multiple URLs (on a domain) with the same exact content, Google has trouble figuring out which page is the original and may throw all of them out.
I took a very close look at my friend’s website. Again, I took a unique line of text from his homepage and searched for it in Google (inside quotes). A funny thing happened. I saw the homepage result, but there were a few extra results as well, all on his domain. There were about 5 extra pages in total.
Now, some of these extra results have been there for years, so I don’t attribute the issue to those pages being duplicate content. What struck me was one of the extra pages.
A few months ago, my friend moved one of his pages. He put a 301 redirect in his .htaccess file, which was the correct thing to do. So now, the old directory where the page was held forwarded to a new page. It looked something like this:
Redirect 301 /olddirectory/ http://www.hiswebsite.com/newpage.php
The redirect worked fine, but here is what that extra page in the search results looked like:
http://www.hiswebsite.com/newpage.phpoldpage.php
Guess what page was showing at that URL…yup, the homepage. The dynamic nature of his website sends unknown page results like this to the homepage. This was a fluke. My friend forgot that there were pages inside the old directory he redirected to the new page. Every old page in that old directory was tacked on to the new page, like you see above. To make matters worse, there were a bunch of links from other websites pointing to the old pages in the old directory.
I am not sure if this would cause the ranking drops that he is experiencing, but the timing certainly lines up with when the issue began. It is also certainly considered duplicate content.
So, here is what I did to deal with the issue this time. I deleted the redirects in the .htaccess file and blocked the URLs of all those extra results in the robots.txt file. Hopefully, this will tell Google to not spider or index those pages and it will also tell Google that those links into the site are dead.
Now, we have to wait. I am not going to submit another reinclusion request to Google because I want to see if the ranking returns naturally. If it does, this was the problem for sure.
Related posts
Wednesday, September 17th, 2008
Ok, this is a pretty simple thing to do and it has some important benefits.
Have you ever visited a website or a web page only to find that annoying “Not Found” error message? If so, what did you do? You probably got ticked off, hit the back button and visited another website. Can you imagine someone coming across a “Not Found” error page on your website? Well, if you don’t have a custom 404 “File Not Found” page set up on your website, that might just be happening.
Here is what you need to do to fix this problem and keep your visitors on your website.
The first thing is to create a web page with some sort of message on it. Something like, “Whoops, looks like the page you are looking for isn’t here. Please click this link to visit our home page or our search page…” You get the idea. You can save the page as “404.php” or something similar and upload it to the root of your web server.
Oh, I forgot to mention this. In order to do what I am suggesting here, you need to be running an Apache web server and your web host has to allow changes to your .htaccess file. I am sure there are other ways to create a custom 404 File Not Found error page and get it up and running, but I am only talking about one way here.
Now, open up your .htaccess file and place this code into it somewhere. I like to place it right on top:
ErrorDocument 404 /404.php
I am using .php extensions for this stuff just because of habit and preference. You can use .html or whatever you wish.
Well, that’s basically it. You can now save your .htaccess file and upload it to the server and go see if it worked. Try typing in some page that you know isn’t there. If it works, please read my previous post about “How To Check Your Web Page HTTP Headers & Response Codes” for some important information.
Good luck.
Related posts
Tuesday, September 16th, 2008
There may be cases when you would like to see what your webpage HTTP headers look like. Why? Well, because they are kind of important. As Wikipedia states, the HTTP headers define what the returned data looks like.
Still you ask, “Why in the world do I care about that?” Ok, I’ll keep going. The main reason I look at the HTTP headers is to find out what the HTTP status code is. The reason the status code is important to me is because this is the code the search engines use for a multitude of things.
Let me give you a little example, and this related to my previous post regarding the sudden drop in Google rankings. As I was doing research into what the problem may be for this particular website, I came across an issue where someone had recently put custom “404 Not Found” error pages up on some of their websites. Everyone knows that custom “404 Not Found” error pages are cool, but what some people don’t know is that if those 404 error pages show a “200 OK” (successful HTTP requests) code, the site may be in big trouble, SEO-wise. The reason for this is because there are going to be many “404 Not Found” error pages on a dynamic website. If you have your custom “404 Not Found” error page showing a “200 OK” response code, the search engines will think that all the instances of this page are duplicate. You know as well as I do, that spells trouble.
What’s worse is if you set your homepage as your “404 Not Found” page. Your homepage is going to return a response code of “200 OK.” That’s not good, because now you have multiple instances of your homepage…all duplicate content.
It’s my opinion that the search engines are smart enough to figure this out. The page (such as your homepage) with the highest Pagerank will prevail. Still, I have some websites that I am working on that have multiple instances of the homepage and they all have Pagerank, which isn’t good, because the duplicates are taking the Pagerank from the real page. Now, again, that’s my opinion.
Here are two tips:
- How to check your HTTP headers – visit this website or just Google “Website header check”
- How to set a particular page as your “404 Not Found” error page in your .htaccess file – Just place this code in the file: “ErrorDocument 404 /404.php” without the quotes. The 404.php file is the actual error page in this case.
Related posts
Friday, July 18th, 2008
Ok, so on to the installation of Joomla 1.5.
Before I did anything, I bought a domain name and pointed it to my server. That is basic stuff. I set the domain up on my server and created a mysql database for this application. That’s more basic stuff.
After that was all good to go and the domain resolved to the server, I went over to Joomla for the latest download, which happens to be version 1.5.4. I clicked the link in the left navigation column and downloaded the “Joomla_1.5.4-Stable-Full_Package.zip” file and saved it to my desktop. I unpacked the zip file and placed the contents of it in my website folder. Since I already had the FTP account set up on my server, I uploaded to contents of my website folder to my server. Here is a word of warning…there are almost 4,000 files. If your host has file limitations, you should find out what they are. Since I have a dedicated server, I am not worried about that. Also, remember that your database is still empty. That will be populated during the install.
After all the files were uploaded, I headed back over to Joomla and clicked on the “New Installation” link about half way down their homepage. Since I am familiar with these types of installations, I skipped past all the upper links and clicked right on “Installation.”
Apparently, there are two different types of installs…one being the web browser method and the other being the manual install. In this case, I did the web browser installation.
In my case, I am did a remote installation to the domain root directory. I did not use a sub-domain, a local install or install the package in a sub-directory. If you would like to, there are instructions on how to go about this on the Joomla website (the same instructions I am using). Basically, you have to visit your domain and, if you have done everything correctly so far, you should see the first Joomla installation screen.
The first screen asks you to choose your language. Simple enough. Since I speak English, I kept the default “English” setting and hit the “Next” button.

The next screen checks the server to see if everything is set correctly and if Joomla is able to utilize it’s resources. In my case, everything checked out fine, but I was told that the “configuration.php” was not writable. After reading the instructions, I found out that this is a regular occurance. I actually didn’t see a “configuration.php” file. I clicked to the “Common Issues & Error Handling” page and read about it. The page gave a few options:
* Do a manual installation
* Create a completely empty file, name it as configuration.php and upload it to your joomla_root/ directory before commencing the installation. Joomla! will then enter the details as the installation proceeds as normal.
* Wait until the end of the installation when at Step 7 the Finished Screen is displayed a list of the variables and settings for the configuration.php file will be displayed. These should then be copied and pasted into a new text document and saved as configuration.php
* As with the last suggestion wait until the end and using the information provided in Step7 manually alter the content of the configuration.php-dist file (this is simply an example file and not a part of the functioning installation) included with all Joomla! installations. There is clearly a greater chance with this method of making mistakes so greater care should be taken. Once the variables have been correctly edited, change the name of this file and save it as configuration.php
I decided to go with creating an empty file named, “configuration.php” and upload it to the root directory. I also chmod the file to 777.

This time, everything checked out, so I clicked the “Next” button.
The next screen is nothing but the license agreement. I read the entire thing and understood it. Then, I clicked the “Next” button.

The next screen is the database configuration. Remember that empty database you have sitting there? Well, you have to fill in the required information.

I entered the information and clicked the “Next” button.
The next screen is the FTP configuration. This is the first time I have come across something like this, but I filled in the FTP information. They suggest to create a local FTP account and not use one that can control the entire server.

Since I am getting slow in my old age, I placed in the FTP username and password and then clicked the autofind path button. That worked and filled in the path automatically.
The next screen is the main configuration. I placed in the main (Super Administrator) email address and password. Then, I clicked the “Install Sample Data” button. I was told that the sample data imported properly.

A word of warning: My first attempt at installing this application gave me an error message that read, “Error: the XML response that was returned from the server is invalid.” on the FTP page and when I tried to install the sample data on the main configuration page. The reason for this had to do with the “configuration.php” file. I needed to upload one and set the permissions correctly. After I did that, I was able to pass those pages. You can read more about the issue here.
The last page looked like this…

Basically, the page gives you the option to view your site or log in to the admin section. I always like to log in to the admin section so I can get the URL. Also, the system says to delete the entire “installation” directory. Lastly, I like to download the now populated config file for backup.
To log in to the admin area, the username is “admin.” Obviously, you should change this.
You can take a look at the site I just set up at http://www.fiixer.com. Next up, configuring and customizing Joomla. Ye haw.
Related posts
Thursday, July 17th, 2008
For some time, I have been looking for a versatile CMS (content management system) that would allow my mind to wander. So far, I have set up some pretty nice systems. They are meeting my goals, but I wanted to see how things would be outside the realm of business. I mean, a new website would certainly be set up under the business name, but it would be sort of a hobby site in the beginning and we would see what it looks like after a year or two.
There is a blurry line between CMS applications and blog applications now. I understand blogs are becoming actual CMS applications, so who knows what will happen with that. I can see WordPress staying my favorite for a while, but I feel like learning something new.
Here are some of the top open source CMS applications I looked at:
- Joomla
- e107
- Drupal
- Plone
- Mambo
- PHP-Fusion
- PHP-Nuke
- XOOPS
After going over a bunch of these, I decided upon Joomla (along with about a million other people). Just to let you know, there is a really great website that lists many top content management systems, along with blogs, wikis, etc… All listed systems are open source and the website has a link to their homepage as well as a demo of the front page and the admin. This helped tremendously during my research.
I really don’t know what I am going to do with this website yet, but I am sure that once I go through all the plug-ins, I will start forming a plan. For now, I am just going to do the install and document the process here. After that, I will document all the exciting things I come across.
Related posts
Saturday, January 12th, 2008
Again, I read the writing on the wall.
One of the companies that created some of my website applications recently put a web poll in their forum. They asked how we users feel about having the next upgrade (and every one thereafter) only work with PHP5 and up on our web servers. I didn’t know what to think. I believe I was running PHP 4.3.8 on a few of the servers and some other version of 4 on the other servers. I didn’t know how all of my 30+ websites would respond to a PHP upgrade.
To find out, I did a little configuring in the .htaccess files on two of my websites. By doing this, I automatically brought the version up to PHP 5.2.4. If things blew up, I could easily bring the version back down to PHP4 by taking that line of code out of the .htaccess file.
Well, I tried it out and everything worked fine, except for two little files that an outsourced developer created for me. I contacted him and he fixed the issue rather quickly. Since I knew things would be ok, I went ahead and had one of my other servers upgraded to PHP 5.2.5.1. After the upgrade, everything worked fine on all my websites.
So, what is the difference between PHP4 and PHP5? You can click here to find out.
Related posts