Are you a Google Analytics enthusiast?
More SEO Content
Google Picked The Wrong Url
Posted 21 February 2005 - 05:40 PM
Last week - hurry - we got a nice boost in PR (for Domain A - I never check any of the others) and a nice boost in Google rankings. I happen to check it out today to show the boss and now Site A isn't listed and Site B is in it's place.
I ran it through an online service that checks what is returned to the search engine for domain B and it says:
HTTP/1.1 200 OK
Date: Mon, 21 Feb 2005 22:35:56 GMT
Server: Apache/1.3.29 (Unix) JRun/4.0 ApacheJServ/1.1.2 PHP/4.3.4 mod_throttle/2.11 FrontPage/188.8.131.5234 Rewrit/1.1a
Last-Modified: Fri, 21 Jan 2005 15:40:00 GMT
Which is what it also says for Domain A.
Domains B, C and D are all "forwarded" through our registrar to domain A.
Is it set up wrong? Shouldn't it say 301 instead of 200?
Posted 21 February 2005 - 05:49 PM
No and No, It's a DNS forward not a redirect.
Posted 22 February 2005 - 10:22 AM
Posted 22 February 2005 - 10:34 AM
See the pinned thread at the top of the forum
Posted 23 February 2005 - 11:14 AM
Posted 23 February 2005 - 02:39 PM
You just never know how much, or many times if, something like that is affecting your site's ranking until well after the fact. So I just eliminate the possibility right up front.
Posted 23 February 2005 - 03:25 PM
Unfortunately we are currently using a 302 redirect for our forwarding and masking services. At the current time there are no plans to change this. I apologize for any inconvenience this causes.
Is the 302 going to continue to cause intermittant problems or was this just a glitch?
Posted 23 February 2005 - 03:42 PM
Posted 23 February 2005 - 05:22 PM
It looks like both! When I view domain B's DNS info, it's pointing to the DNS server that domain A sits on. When I view the forwarding information for domain B, it say's it forwarding to domain A.
Should it be one or the other but not both? If so, which is better?
Posted 23 February 2005 - 06:16 PM
Unless the host has set up parked domains I doubt that the DNS pointing to the host will do anything.
A 302 can cause problems with Google. You need to do a header check with one of the forwarded domains that has the DNS records also pointing to the site and see if the HTTP header returned is 200 or 302. Either one is not good. If you get a 200 response then they have parking set up with the host and the DNS records are taking being used at Godaddy. If a 302 Is returned, then the forward is what is being used.
Hope that make sense.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users