Welcome to WebmasterWorld Guest from 18.104.22.168
I have a client with a domain name of Widget1.com. This is only 1 of 20 sites the client has, each site being 1 page. Widget.com (not widget1.com) is hosted with Company ABC and the other 19 widget sites are parked at the same nameserver as Widget.com. We are running a content manager which identifies the URL desired and renders the appropriate page.
So when you type Widget18.com, you are truly landing at Widget.com and being served the page Widget18.php and the address bar shows Widget18.com.
With me so far? *grin*
Yahoo! has gone psycho on one of our domains. If you enter the command site:Widget1.com at Yahoo! there are 111 pages returned yet it is a 1 page site.
Examples of pages showing up for site:widget1.com are:
- www.widget1.com/?M=A - this is meaningless to me...we don't have variables with m's and a's in them *grin*
- www.widget1.com/live21 - Live21.com is indeed a domain name which is parked at the same location as widget21.com.
What is freaky is that widget1.com does not have subfolders. Yahoo! has arbitrarily (sp?) made widget1.com the parent (instead of widget.com) and made it look like there are subfolders (such as /widget2/ under the parent. widget1.com/widget2 gives a 404 page.
I am not so sure that I can create a custom 404 page for widget1.com because it is actually widget.com/widget1.php.
Is this making any sense at all? If not, let me know and I will present the actual file structure :-)
I am wondering about making custom error pages for freaky events like Yahoo is showing so that people don't get 404s but get redirected to the proper domain - like if you land on widget1.com/widget2 go to widget2.com
Thanks for those who can process this riddle like info :-)
By following each redirect response you see, you may be able to track down where the "internal" URLs are being revealed.
The CMS system may have created a subfolder for each of the other domains, and then accidentally "published" that internal URL-path by doing an external redirect to it. Anyway, checking the server headers will be more useful than my guesses.
I'd also recommend pointing the DNS for those alternate domains straight to the IP address of your server, and dumping the "forwarding" or "domain redirection." I don't use those services, and I suspect they're only useful for 'cheap' hosting. However, when you factor in the cost of the recovery exercise you are about to go through, the true cost of cheap hosting will become clear (sorry).
Those "?M=A" - type URLs are some dumb exploit that's been running around. You can detect them and reject them, but the domain-related problem is the one to worry about first.
I think you said "for domain=any domain# you have: domain1 URL=domain# + multiple pages of domain listings: while domian1=any domain# create multiple pages of domain listings and add pages that do not exist to SERPs."
Anyway, sorry for the math... My first question is what is the exact format of the current redirects? Are they [P] proxy served, are they [R] with no code which creates an implied 302 temporary move, or are they something else entirely?
Where do the links that Y has listed take you when they are clicked? Are you redirected, or do you get content on the pages they think exist?
I think you will find a better, more complete solution after you find out exactly what is happening now... at the source.
Then after you know why we can probably help you devise a solution that will help solve your problem, not possibly compound it.
Anyway, not much of an 'answer' but may help you narrow down to find the best solution.
Added: What Jim said too, must have been typing at the same time.
The parent site, which is the one used to set up hosting: Gambbal.com. There are 20 other domains whose nameservers were pointed to exactly the same nameservers as Gambbal.
The odd duck site is Betws.com, which is also hosted at the same place. The way the content manager works, Betws goes to Gambbal.com and the page betws.php is shown, although the address bar shows Betws.com. A server header check on Betws.com shows code 200(OK):
HTTP/1.1 200 OK
Date: Tue, 26 Apr 2005 13:15:52 GMT
Server: Apache/1.3.33 (Unix) mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/22.214.171.12435 mod_ssl/2.8.22 OpenSSL/0.9.6b PHP-CGI/0.1b
Now, if you go to Yahoo! and enter site:betws.com you get 111 pages showing up! Yikes! These pages don't exist :-) An example would be: www.betws.com/btnfl. Btnfl.com is indeed a domain which has the same nameservers as Gambbal.com and Betws.com. but there is no subfolder under Betws.com because that is actually Betws.php being served up!
So perhaps this gives more information to work with ;-) And if I make things more clear maybe I will be able to understand the responses more clearly *grin*
[edited by: jdMorgan at 2:38 pm (utc) on April 26, 2005]
[edit reason] Obscured specifics. [/edit]