jdMorgan
msg:3858731 | 11:03 pm on Feb 26, 2009 (gmt 0) |
> does robots.txt ignore any domain information and just look at what comes after the /. Yes, only the server-local URL-paths can be specified. If you have the technology to "change the prices" between domains, you likely also have the technology to serve a different robots.txt per domain... I suspect the right questions are not being asked. Jim
|
deadsetchamp
msg:3858735 | 11:06 pm on Feb 26, 2009 (gmt 0) |
Thanks Jim, They said that they can't do individual files but might be able to do the meta spider restriction method. Cheers for the quick reply.
|
jdMorgan
msg:3858749 | 11:23 pm on Feb 26, 2009 (gmt 0) |
> they can't do individual files I'll bet you can easily find someone who *can* do individual files -- Good help is cheap in an economic downturn, something that "no-can-do" people should bear in mind... ;) Use mod_rewrite or ISAPI Rewrite to internally rewrite robots.txt URL requests to different files based on the Host header sent with the client HTTP request. Or again, use a rewrite engine to pass all robots.txt requests to a PERL or PHP script which can generate different robots.txt content, again based on the Host header sent with the HTTP request. Or build this function into the script you use to generate your custom 404 error page contents, and let the robots.txt requests activate that script as well, with that script producing the robots.txt content (and a proper 200-OK server status response)... There are many ways to do it. Jim
|
deadsetchamp
msg:3858800 | 1:15 am on Feb 27, 2009 (gmt 0) |
Thanks for this! I know what you mean about getting 'can-do' people. I will pass this on to them and it might kick start their imagination.
|
g1smd
msg:3871251 | 9:29 am on Mar 16, 2009 (gmt 0) |
What you need can be done in just a couple of lines of code, as jd has outlined above. WebmasterWorld uses a similar system to serve a different robots.txt file to different bots.
|
|
