For websites and landing pages
Bots spoil your statistics and requests.
Strazh stops them
Short robot visits, empty form submissions and page copying distort your statistics: you cannot tell how many real visitors you have and where they come from. Strazh lets people and search crawlers through and sends the rest to a check.
Free pilot: we block nothing. In 1–2 weeks we show how many bots visit your site.
On a similar site (a store) the median visit time of real people grew from 4 to 14 seconds. Data for 6 Oct – 1 Nov 2026, details below.
What bots do on a website or a landing page
A bot does not leave a request or buy anything, but it gets into your statistics and your forms.
They distort statistics
Short bot visits drag down time on site and raise the bounce rate (when a person leaves after one page). Bots that run scripts get into your counters. Such numbers make it hard to tell what works, especially if you pay for ads.
They clog forms
Robots send requests and subscriptions. Managers sort through junk while real requests get lost in it.
They copy content and load the server
Scrapers take texts, prices and images, and every bot request spends server resources and slows pages down for people.
Example on a similar site: an online car paint store
6 Oct – 1 Nov 2026This is a store, not a landing page: other sites will show other numbers, your pilot shows yours. A store on 1C Bitrix. We compared one week when Strazh only observed with 12 days when it sent bots to a check.
−84%
bot visits per day
From about 1,130 to about 180. Only bots that execute JavaScript are counted.
4 s → 14 s
median visit time of real people
Half of human visits last longer than 14 seconds.
33 s → 54 s
75th percentile of human visit time
One in four human visits lasts longer than 54 seconds; before, longer than 33.
60% → 44%
human visits shorter than 10 seconds
Precisely, 60.0% → 44.4%.
Human bounce rate barely changed: 88.2% → 84.7%. That is the honest picture: Strazh removes bots, it does not change the site itself.
Data period 6 Oct – 1 Nov 2026. The “before” window is 6–12 Oct, with Strazh in observe mode; it is only 7 days, there is no earlier history. The “after” window is 17–28 Oct; the transition days 13–16 Oct are excluded. Human metrics for 29 Oct – 1 Nov are the same.
A visit here is a session in the visit counter; a bot is a visit the counter flagged as a bot. Bots without JavaScript are not visible in these figures. CPU and PHP load were not measured in this study.
Fewer bots in your statistics and requests.
You see what real visitors do.
How the pilot works
We connect in observe mode
We install Strazh next to your web server and turn on a check for every request. The site and CMS stay as they are. Strazh lets everyone through and only records whom it would have stopped.
We collect data for 1–2 weeks
How many bots come, from where, what they look at and how many requests they make. Shoppers notice nothing.
We show you the report
You see the bots on your site and decide whether to turn protection on. The pilot commits you to nothing.
How it works
For whoever runs the server
A check on every request. Before responding, the web server asks Strazh (auth_request). Strazh runs on the same server, so the answer takes milliseconds. There are three outcomes: let through, show a check page, or refuse.
What it looks at. The browser TLS handshake fingerprint (JA4), the network and hosting the request comes from (ASN), country, browser headers and whether they match the User‑Agent, and the address history. Declared bots and automation are recognized immediately; for the rest, signals add up to a score.
Search crawlers. Their pass is set in the rules; usually Google, Yandex and Bing are let through without limits. Strazh recognizes real crawlers by reverse DNS: anyone who only calls themselves Googlebot is treated as a fake.
Two ways to connect. On your own web server (Strazh sits next to it) or through our front: you change the DNS record of your domain, and we pass the traffic through Strazh to your site. The second way suits sites on builders and on hosting without server access, but only if the site has its own domain.
Two modes. In observe mode (observe) Strazh lets everyone through and logs whom it would have stopped. In enforce mode (enforce) decisions are applied. The pilot runs in observe mode.
If Strazh is unavailable. If the service does not answer within 300 ms, the web server lets the visitor through. The site opens as usual.
Client dashboard. A log of decisions for every request, allow and block lists by address, network, country and fingerprint.
What a visitor sees. People pass without a check: the decision takes milliseconds. Visitors that look like bots get a page with an “I am not a robot” button, and after the check the pass lasts a few hours. Bots you need (page-speed checks, link previews in messengers and social networks) can be allowed in the rules.
Frequently asked questions
Will the site suffer in Google and Yandex?
Search crawlers are set up in the rules. Usually we let Google, Yandex and Bing through without limits. Strazh stops those who only claim to be a search engine.
Will visitors see a captcha?
Not during the pilot: Strazh only observes. When protection is on, visitors who look like bots see a check. The report shows how many visitors of your site Strazh would have sent to a check.
What happens if Strazh breaks?
The web server waits for an answer no longer than 0.3 seconds. If Strazh did not answer, the visitor simply gets through to the site. The site keeps working.
My site is on a site builder or ordinary hosting. Will it work?
Yes. If you have no access to the web server configuration, we connect through our front: you change the DNS record of your domain, and traffic goes through Strazh to your site. Your code and the site itself do not change. The condition: the site must have its own domain (not a free builder address). We discuss the details after your request.
How is Strazh different from PHP scripts and a plain captcha?
Strazh sits on the web server, not inside the site: it does not matter what the site is built with (PHP, Bitrix, WordPress or plain pages). The decision is made before the page loads, and the pilot first only observes and shows a report, so you decide yourself whether to turn protection on.
What data does Strazh see?
The same as your web server log: visitor address, page address, browser headers and cookies. The content of forms does not reach Strazh.
How much does it cost?
The pilot is free and commits you to nothing. We talk about the price of protection when you have the report in hand.
Get a bot report for your website
Free pilot: we block nothing. In 1–2 weeks we show how many bots visit your site.
- How many visits to your site are made by bots
- What they open: pages, forms, service paths
- How many visitors Strazh would have sent to a check if protection were on