The Traffic Redirection module converts unwanted traffic to boost the marketing campaign of an e-shop. Bad traffic utilization includes conversion of hack attempts, redirection of attempts to post forms with spam content and protection against hosts, isp and individual IPs that can be configured separately from the administration panel. A reports page offers detailed information of the redirected traffic, including date, and reason of the individual IPs along with the enabled/disabled status of each.

There are 3 different levels of integration for the Traffic Redirection. The first level of integration is inside the server .htaccess where the 401, 403 and 404 handlers are hooked by an osCommerce script. On the web-application end, the Traffic Redirection includes a header pre-processing determining attempts in 2 different ways.
  a). For spiders pre-processing ensures the request will be processed by a spider only. For instance spiders do not post forms.
  b) For humans pre-processing verifies the browser headers.
At the first level there is no decision making of a particular request, but a redirect can be issued to a separate page where the final decision will be made. Destinations of the redirection can be setup from the administration panel.

The second level of integration takes place before any of the web scripts begins processing. The second level of the Traffic Redirection, includes IP/rdns bidirectional checkup to verify whether a specific visit is legitimate, ie: from a human or spider.

There are options for external services where the server connects to, requesting information for a particular IP once. Invalid requests can be redirected at this point externally or internally based on the keywords criteria entered with the request, configuration options the administrator preselects for individual IPs, groups of IPs or entire hosts/ISPs. The second level is recorded and logged in the MySQL database of the osCommerce. At this point the Traffic redirection system eliminates artificial traffic and has countermeasures against scrapping and other automated keyword retrieval tools. This helps the web store against competition as automated content extraction is voided. Based on customer requirements, different block access options are available from the administration panel.

The 3nd level of integration is an SEO-G extension that converts an invalid URL that is asserted via the 401, 403 and 404 Apache handlers. The request is converted into a friendly URL and feeds back the SEO-G queue for re-processing via a 301 redirect.

Configuration options also has an exclusion list where the merchant can specify an IP or a range of IPs for exclusion from the whole Traffic Redirection process.

The Traffic redirection has other custom features targeting competition, taking advantages of weak points of competitor sites. The system utilizes an anti-honeypot add-on, that can boost the natural traffic to your site. Traffic that otherwise could never materialize due to customer preferences.

Traffic redirection also eliminates bandwidth consumption of  these unwanted requests as the headers emitted are only the redirected ones. There is no HTML or MySQL processing by the web scripts of your e-commerce store.

Custom requirements may include other safeguard like to guarantee content exposure to popular spiders first before a page becomes available. Apart of spider sitemaps new pages and new content may be accessible initially to spiders only and published after a short period of time.

The Traffic Redirection module can be integrated with the I-Metrics Layer . For optimum performance the Anti-Bot verification system designed by Asymmetrics is also recommended to add an extra layer of protection to your e-commerce store.