IPs and Domains

[tylerfraser]

If a domain loads on the domain and the IP is that a problem?

So it loads on domain.com and 69.16.....com

Thanks!

[matbennett]

Oh - the IP is the old server, not the IP of the current one?  All of the above still applies, except it just got a lot easier!

Redirect all traffic on the old server to the new one (301 redirect). Failing that just turn off the old one.

[tylerfraser]

Thanks Mat! Do you think I should disallow the IP address from the old server. The one that this site was switched from?

Thanks again.

[matbennett]

Sitemap.xml is useful, but it won't help with this issue I am afraid.  To solve the problem of the wrong version of the site being indexed you need to instruct search engines that they are looking at the wrong version. It might sound logical to give them a list of the right URLs, but that is not enough. They don't follow the logic of "... and ignore the rest".

There are 2 main ways to go about this. I personally prefer the first, but either is a win. Unfortunately both method will probably require the help of your developer.

Option 1 - 301 Redirects

A rule is added to the server that says "if a user requests a url of http://69.16.xx.xx/pagename.html send them instead to http://www.example.com/pagename.html . Also send a 301 code - and instruction that the old address has been moved permenantly.

Depending on your server set-up this is most likely done by adding some redirect rules to the .htaccess file on the server. Quick easy job for someone who knows that they are doing - literally a few minutes.

Option 2 - rel Canonical

Depending on what powers you site this might be simpler. A conditional statement is added to the code that checks that pages are being served from correct sub/domain. If they are not then a simple tag is added to the HTML output that points the search engines towards the correct address.

If you are using a CMS to power the site this might be a simple change. A few lines added to a common template. Again, quite a fast job.  If you are using static pages you won't have the option to use this method.

If all of the above sounds like gibberish then you need to talk to the developer.  If not,. then great!

I hope that is some help.  I wouldn't panic about this. Even if the IP address versions do all get indexed it is probably not going to cause a big problem to be honest.  However if you can you should get it fixed.

[tylerfraser]

Thank you Mat. I am seeing the IP address being cache and am considering adding a sitemap to the IP address in my sitemap index xml file. Does this sound like a good idea?

[matbennett]

Do you mean if the site loads by visiting domain.com and 69.16.xx.xx ?

If so it is only a problem if it starts getting indexed, which usually doesn't happen unless someone links to it.  You could have a redirect in place just in case (via .htaccess or similar).  Many designed to catch the www and non-www versions would catch this as well anyway.

However, unless you start seeing the ip version appearing in the results I wouldn't overly worry about this.