Forum Moderators: Robert Charlton & goodroi
I am on a shared host with windows server and an h-sphere panel.
Any recommendations?
It sounds like your content is accessible using your ip addresss directly. This is not the right thing to do. If a visitor enters
http:// 0.1.2.3/foo
then you should redirect them (preferably with a '301 Moved Permanently' header) to your correct address at
http://www.example.com/foo
rather than just serving the content. Talk to your server administrator to get this set up right.
You need to do a couple of things immediately.
1. Make sure the shared account has been completely removed and verify it by following the IP domain name URLs in the index.
2. Submit a URL removal request using the IP as the domain name [128.1.1.1...] & [128.1.1.1...] to:
Good luck!
I am on a shared host with windows server
Well, I don't know that I would go willy-nilly issuing redirects if I was sharing an IP address with other domains -- how do you know which domain the request was for. OTOH, I guess it won't hurt for you to redirect. If the server is configured correctly, you'll probably never actually get any such requests; if it's not, then there's already a mess and you're not making it that much worse.
It occurs to me that I don't know why Google is willing to list bogus domain names such as this.
What about your directories within?
That's what counts. Google will analize your page, if ok then another page.
Just cause you have a dedicated IP will not help if you are looking for your site to show up high.
What is the connection of your page b..or c or d?
Then what's your homepage about? Virtual server or dedicated is not part of the math problem.
Search engines are smarter than that. (well not MSN right now).
Original Content = #*$!? nOPE!
Be original oR prove it.\
If you don't have a cancer cure then do not even talk to me about your bull#*$! biz.