Advanced

This option is not available when the Javascript platform is selected. This is due to the fact that Javascript is a client-side scripting language and logging of user searches is not possible.

This enables search word logging so that searches made on your website will be recorded into a server-side log file. Note that you will have to specify the filename and path of the location of the log file on the server-side relative to the location where you will place the search script.

Note: You will need to be able to change server-side file permissions to allow write access to the log file you specify. We recommend this option to more advanced users familiar with server side file permissions only. Note that many cheaper web-hosting services do not allow you to change your file permissions, so consult your web hosting company regarding this beforehand. This can normally be done via your FTP client or through a Unix shell account by using the "chmod" command. For more help and information on setting up your server-side permissions for logging, please refer to our online FAQ:
http://www.wrensoft.com/zoom/support/logging.html

Logged search results contain, the date (YYYY-MM-DD), the time, the IP address of the user, the search query, and the search options used. The following is an example of a log file record (on one line).

2004-03-05, 09:52:08, 127.0.0.1, "test search query", Matches = 6, OR, PerPage = 10, PageNum = 0, No cats, Time = 0.084, Rec = 0

Since the log file is in CSV format, you could also import the file directly into Excel.

Note to CGI users: if you are hosting on an Apache server (in a “cgi-bin” directory), remember that most Apache servers do not allow text files to be accessed via HTTP from the cgi-bin directory. This means that if you store your log file in “/cgi-bin/logs/”, you will not be able to access this file via HTTP using your browser or Zoom’s Statistics Report tool – instead, you will only be able to download the file with FTP and analyse it locally. Alternatively, make sure you specify a log file path outside of the “cgi-bin” directory.

If you wish to use a copy of the search script (search.asp, search.php or search.js) that is located in a different folder besides the one in the Zoom installation directory, then you can change the path here. This is only necessary if you are making modifications to the search script source code, and you wish to maintain multiple versions to be used with different sites.

This option allows you to specify the URL used to link back to the search script. By default, it should be left blank.

However, if you wish to embed the search script in your own server-side scripts (eg. you have included search.php into your own PHP file, or included the CGI within a PHP script, etc.) you can then specify the filename of your embedded script here so that it will link to the correct file.

Users of the Enterprise Edition of Zoom can modify the User-Agent text that is used to identify the spider when it crawls web servers. By default, the spider identifies itself as "ZoomSpider - wrensoft.com [ZSEBOT]".

If you specify a name here, e.g. "mysearchengine.com", your spider will then identify itself as "mysearchengine.com [ZSEBOT]". This allows you to include your website name or other contact information, should you wish to allow third-party websites to identify you, or be able to contact you if required. It can also be helpful if you wish to add specialized behaviour to your website, so that, for example, you could allow your personal spider exclusive access to certain pages on your site, and prohibit access for any other user-agents.

This option disables the search script’s attempt at specifying the charset via a HTTP header. This is done to ensure that the corresponding character set used for the encoding of the index data, is also used for the search page. However, if you are an advanced user trying to embed the search script within your own scripted pages, this extra HTTP header may not be required (as you may already have HTTP output before the search script is executed). In this case, you can safely disable this feature here.

The CGI version can now return search results in XML/RSS format. Selecting this checkbox will enable the XML output as default, and clicking "Configure" will allow you to specify some XML specific settings. See "XML/RSS output" for more information.