Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First of all, there is no way to securely identify that a request is coming from a search engine, so that anything you let a search engine see can be seen by any enterprising web surfer. I would say that the very first thing you must do is make sure that the client understands this. You can make something that works for the "default" user that isn't trying to bypass your system controls, but if you're going to let a search engine in to see content without authentication, then regular users will be able to follow that path too (with a little ingenuity).</p> <p>Second, it is not wise to assume that a search crawler will support cookies at all. If you're only targeting one particular search engine, you could test it and see if it supports cookies, but from what I've read, most do not as it's just a lot more housekeeping on their end of things and they want to index what is freely available anyway. So, you can't use a cookie to keep track of a search engine request.</p> <p>The only way I know of that you could let search engines in, but not regular default viewers is by sniffing the user agent string of the requesting agent. Each search engine will uniquely identify itself as such and you could look at that on each request you get and decide if they are allowed to bypass normal restrictions. But, just so you and your client know, any regular user could just configure their browser to include that user agent string and you'd be letting them right in - you can't really tell the difference. The Safari browser comes with the ability to control the user agent string (it's in their to help web developers with their own testing, but it can be used in other ways too).</p> <p>In certain cases, it may be possible to look at the requesting IP address to see if it appears to be what you would expect from a search engine, but unless the search engine publishes the IP address ranges they would use and somewhat guarantees that these would be adhered to, this is a risky proposition to rely on.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload