views:

421

answers:

2

Hi Folks,

I was wondering if would it be possible to protect the "https://www.DOMAIN.com:8443" URL from search engines listing perhaps using the htaccess to redirect the 8443 port from "DOMAIN" to elsewhere?

This is the VZPP Plesk - Login Login to Plesk. Please enter your login information. Username. Password. Interface Language. User Default, ENGLISH (United States), GERMAN (Germany) ... https://www.DOMAIN.com:8443/ -

Many Thanks.

A: 

Try to use (if I've understood your question right)

<meta name="robots" content="noindex,nofollow,noarchive"/>

And google about robots.txt... don't remember the syntax...

Jet
Won't work as Plesk header is not accessible by users!
Iman Samizadeh
Didn't know. Never used Plesk. Well... Actually this is not a header itself - its only instruction for browser to do the same as if he got this header.If this won't work - then only .htaccess, httpd.conf or something like ipfw.conf left, beacause there's no more layers to filter requests, only OS-firewall(s)-apache-php.
Jet
A: 

You can read about using User-Agent detection with mod_rewrite here, how to setup your robots.txt for Google, Yahoo!, and MSN/Live Search - however, this all assumes sane and cooperative bots. There's little that can be done to protect against agressive, 'black-hat' bots.

TML
Not working :( still google shows the login page :(
Iman Samizadeh
Well, if they've cached it, they've cached it. You can use the Google trick below to find out when they grabbed the page.http://lifehacker.com/5239562/display-the-date-a-web-page-was-published-in-search-resultsYour best bet is probably to rename/move the 'control panel'. Also, make sure there are no 'inbound links' pointing there that bots might follow, or make sure you use the 'nofollow' pseudo-attribute value.
TML