Quote:
Originally Posted by kgun
A follow up on that idea. Assume that, - The webmaster's ISP IP is on the white list and
- his site is hosted by a hoster on the white list
then (s)he will not see the link as broken. The not white listed SE will see the anchor text but are unable to crawl and index / archive the page(s in the protected area).
I thnk that is not problematic for Google as reported in Matt Cutt's video or am I wrong? |
I think I must have been tired.
It is of course the IP of the webmaster's ISP that is relevant. The link to the page in the protected region can be on a server outside the white listed region. (S)he will still see the page if (s)he clicks the link from a computer with Internet access in the white listed region.
But there may be bots in the white listed Ip region and then,
by replication, the content
is potentially open to the whole world as far as I can see.
Quote:
Originally Posted by crankydave
Just briefly... no pages are unimportant IMO. Some are more important than others. Rather than try and granularly funnel bots, why not use the pages you consider less important to your advantage?
|
There may be (educational or other) content that you don't want to be publicly available.
Conclusion:
If you white list Ip's (Ip regions), you must be careful that there is no bot on that list (in the Ip region). As long as we are not talking about a secure server (https), the best way is perhaps as Matt Cutts says in the video, to use .htaccess to password protect, that is authenticate the protected area for human beings. But if your content is open to one other person, it is potentially open to the world
