Welcome to WebmasterWorld Guest from 184.108.40.206
My concern is that since my dedicated IP Address will change if I move to a new hosting company, will this effect my Google Rankings, PR, or anything thing else?
I have heard that Google does effect weight and significance to IP Address.
Help! What can I do? Should I just remain with my old hosting company who is doing a decent job, but does not have the tech support that I expect (which I can get from my new hosting company)?
A drop in our rankings could mean $$10,000+ losses per month.
You are saying this is not correct, right?
A brief interval could mean a lot of money to us ... $10,000+ for a few weeks potentially, so we don't want to move even if there is a brief outage.
When you say if the old or new host are incompetent, in what way do you mean it?
The new host seems very competent, to me anyway, which is why we want to move. But our old host ... I'm just not sure about -- although without moving, we have excellent ranking and are afraid of jeopordizing it.
When I say brief, I'm talking about the 'new' site propogating across the web.
I'm talking minimal disruption for a maximum of about 48 hours - only increased if your site falls down a hole between two hosts. If the 'new' host is OK, I can see zero reason for more than a hiccup - or no problems at all.
Talk to your new host about 'worst case scenarios' - I'd be surprised if there is one! ;)
I thought google attributed more weight to IP addresses. But perhaps not.
I think that started when Google got registrar rights; some thought this meant Google looking through their bedroom windows. That appears not to have happened ;)
The one time that IP addresses do matter is when moving from a host in one country to another country. Google's country-specific searches do seem to take account of site origin, as well as domain.suffix
But host-to-host within a country does not seem to matter at all.
Do report back on your experience, please :)
You really need to ask yourself if it is worth a gamble. If it's just tech support, keep in mind, that changes.
I have a site that is hosted by a service that was great. But it changed hands and now tech support is the worst. But I have resisted, til now, changing hosts because their uptime has always been near-perfect.
But in the last month it has gone down twice. And according to google sitemaps it happened when google was trying to spider the site. Twice. In a row. So I am looking around for a new host now.
In some cases my site has moved from one country to another without being affected.
As long as you keep the old site online while you set up and test the new site, and wait for the DNS entries to propagate, you should'nt have any problems.
Make sure all you 301 redirects (From the past) are in place on the new server before doing the DNS change, thats VERY Important!
If that's not possible then at least put a redirect on the old machine.
The reason: the DNS changes will take time to propagate across the net. There will be a period of time where some users/spiders have the old IP address, and some have the new one. So you need to provide some meaningful content (even if it's just a redirect) on both.
So for example:
If your domain name is widgets.com and you're currently on 220.127.116.11, and you're moving to 18.104.22.168, then you could set up 22.214.171.124/index so as a redirect to 126.96.36.199/index, and set up *both* web servers to serve requests for widgets.com.
Then make the DNS change, so that widgets.com moves stops resolving to 188.8.131.52 and changes to 184.108.40.206. This change will take some time to propagate, so for a while (how long depends on your DNS settings), you might have users visiting *either* 220.127.116.11 *or* 18.104.22.168 when they type in widgets.com.
Something else you can do that'll help: some time *before* you make the move, change your DNS settings (TTL and so on) so that your domain name will be only cached by DNS servers for a shorter period of time than usual. That way, when you do make the move, your DNS change should take effect more quickly. Then after you've made the move successfully, change your DNS settings back to normal, to ease the load on your nameserver.
I don't know if this is a result of the june 27th update or the move, either way we will find out soon i guess. I'm hoping it's just a bad data push/glitch, it just really hurts looking at the Google analytic traffic curve's nose dive, scared my heart will follow soon .lol.