This is a hugh problem since Google crawls Domino hosted web domains and pairs them with them “wrong” directories (wrong data) since it does not know better.
This is not possible today with web site rules or any other way.
Also it is not possible to force subdomains x.webdomain.com to webdomain.com, where x could be anything. I will instead get redirected to the default website. That is NOT a good solution
Please fix this sooner than later!
These are MAJOR problems if you have more than 1 webdomain on you Domino server.
1.) Use Apache or some other reverseproxy solution in front, and use Apache config to block access to other folders outside each hosted domain. Our admin made a notesagent that reads from the sitedocuments in the names.nsf and writes the config.
2.) Use sitedocuments to set your root path. For example, if your db is /www/test/test.nsf, create a substitution rule pointing /* to /www/test/test.nsf/*. This will lock down and point everything to the root of test.nsf. You will then have to “unlock” access to every other db in the same folder. This also have the benefit that you can access the site with www.test.com/ and not www.test.com/www/test/test.nsf. You can find good examples on this on the net.
We do so by making a page (but you can use any design element, and probably even a document), and then we use substitution rules to point /robots.txt to /www/test/test.nsf/robotsPage