Stop crawlers that look human.
Centinel helps publishers see which crawlers reach their content, decide who gets access, and stop the rest before they take it.
Request a site auditWhat changes
Clear rules for crawler traffic.
You choose which tools can reach your site and which ones need to stop. Your existing CDN or WAF stays in place.
How does Centinel work?
It gives you a simple way to find crawler traffic, set rules, and protect the parts of your site that matter most.
01
See who reaches your content
Centinel finds known crawlers and automation that tries to look like a normal reader.
02
Check the browser
Each new session starts with a quick browser check. Real browsers pass in less than a second, with no CAPTCHA or puzzle to solve. After that, the session continues without another check.
03
Decide who gets access
Set rules for each crawler and the pages it can reach. Allow the ones you want and block the rest.
Why do some crawlers get through?
Some crawlers use real browsers, home internet connections, or scraping APIs. That can make them look like readers. The browser check catches what server-side checks miss.
What should you protect first?
Start with the pages where scraping costs you the most. That may be paid content, signup flows, or the pages your subscribers use.
- Paid articles and downloads
- Account and signup flows
- Search and archive pages
- Comments and community areas
- Checkout and subscription paths
See how Centinel fits with your current stack in the integrations directory.
Want to see what reaches your site?
A site audit shows the crawler families reaching your domain and the pages where you may need more control.