What UsercentricsBot does
The Usercentrics DPS scanner scans websites for the Usercentrics consent platform to detect data-processing services and third-party technologies. Scanning is done from a published pool of static IP addresses that Usercentrics keeps up to date but does not guarantee as fixed. The scanner identifies itself with a user agent containing 'Usercentricsbot/1.0; +http://usercentrics.com/dps-scanner/', and Usercentrics recommends matching the 'Usercentricsbot/1.0' substring because the full string will change over time.
How to control UsercentricsBot
Target UsercentricsBot in your robots.txt with the Usercentricsbot token. Rules apply per bot, so you can allow this one while blocking others, or the reverse.
Allow UsercentricsBot
User-agent: Usercentricsbot
Allow: /Block UsercentricsBot
User-agent: Usercentricsbot
Disallow: /Usercentrics publishes the static IP pool its DPS scanner uses and recommends allowlisting or filtering its traffic by the 'Usercentricsbot/1.0' user agent substring, since both the IP list and the full user agent string can change over time.
How to identify UsercentricsBot
Temso identifies UsercentricsBottraffic by matching the request's User-Agent header against this pattern. User-agent strings can be spoofed, so treat a match as an indication, not proof.
UsercentricsbotUsercentricsBot FAQ
What is UsercentricsBot?
UsercentricsBot is the user agent of the Usercentrics DPS scanner, which scans websites as part of the Usercentrics consent management platform. It identifies itself with 'Usercentricsbot/1.0' in its user agent string and scans from a published pool of static IP addresses.
How do I block UsercentricsBot?
Add a robots.txt group with 'User-agent: Usercentricsbot' and 'Disallow: /'. The documentation does not state whether the scanner obeys robots.txt; its traffic can be identified by the 'Usercentricsbot/1.0' user agent substring and the published static IP pool, and blocking those will prevent scans run through a Usercentrics account for your site.
About Operational Bots
Monitoring, security scanning, link previews, webhooks, and feed fetchers: the utility traffic that keeps integrations and shared links working.
Most of this traffic is service-critical or user-triggered. Webhooks and previews don't follow robots.txt, and blocking them tends to break things you rely on.
