WP-CompressSaaS is a bot in the other bots category, operated by WP Compress.
OptimizerBot (WP-Compress/SaaS) scans client
Bots that do not fit the other categories. Review their purpose and allow only what you need.
WP-CompressSaaS identifies itself with this user agent string:
WP-Compress/SaaS Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36Anyone can copy a user agent string. Transfon Security also checks where each request comes from, so a request that claims to be a known crawler but comes from the wrong network is treated as a fake, not as the real crawler.
We have not confirmed whether WP-CompressSaaS follows robots.txt. Add a rule, then check your logs to see that it stopped. robots.txt is a plain text file at the root of your domain, such as https://example.com/robots.txt.
User-agent: WP-Compress Disallow: /
User-agent: WP-Compress Disallow: /private/ Disallow: /search
User-agent: WP-Compress Allow: /blog/ Disallow: /
User-agent: WP-Compress Allow: / User-agent: * Disallow: /
User-agent: WP-Compress group, WP-CompressSaaS ignores your User-agent: * rules, so repeat any that should still apply.WP-Compress from WP-CompressSaaS's user agent; check WP Compress's own documentation if it publishes a different robots.txt name.Treat robots.txt as a statement of your policy, and enforce it where requests arrive.
Allow WP-CompressSaaS if it is a service you use, and keep its visits out of page views and ad requests either way.
Transfon Security for publishersWP-CompressSaaS is not a person. Exclude it from campaign and conversion data so reports reflect real visitors.
Transfon Security for advertisersAllow WP-CompressSaaS only if it works for your store, and keep it away from cart and checkout.
Transfon Security for e-commerceIf WP-CompressSaaS is a service you use, allow it on the endpoints it needs and block it elsewhere.
Transfon Security for SaaS and APIsrobots.txt is a request, not an enforcement. Transfon Security shows WP-CompressSaaS by name in the Top Bots report, so you can see how often it visits and which pages it reads. Block or allow it with a User Agent rule, or slow it down with a rate limit decision rule.
Transfon Security
WP-CompressSaaS is a bot in the other bots category, operated by WP Compress. OptimizerBot (WP-Compress/SaaS) scans client
We have not confirmed whether WP-CompressSaaS follows robots.txt. Add a robots.txt rule, then check your logs to see that it stopped, and block it by user agent if it did not.
Add "User-agent: WP-Compress" followed by "Disallow: /" to the robots.txt file at the root of your site. To enforce it, block requests whose user agent contains "WP-Compress/SaaS" at your WAF. In Transfon Security that is one User Agent block rule.
No. robots.txt is voluntary, so WP-CompressSaaS may not follow it, and anyone can send WP-CompressSaaS's user agent, so a fake WP-CompressSaaS ignores your rule. Enforce the rule where requests arrive, at your WAF, and check the source network.
Bots that do not fit the other categories. Review their purpose and allow only what you need.
Transfon Security identifies every bot in this directory in your traffic reports, flags fake search crawlers, and lets you allow, block or rate limit each bot.
Privacy, security, monetization, and performance insights. A few emails a month, no spam.