01 · Operator
Who operates WeSEE
02 · Behavior
What WeSEE does
Bot databases list WeSEE under the name WeSEE:Search with an info page at wesee.com/bot. That page is no longer available, so details about its crawling could not be checked.
03 · Impact
Why WeSEE matters for your site
If you allow it
- Operator is identified in bot databases
If you block it
- Documentation is offline
- No clear benefit to site owners
04 · Allow
How to allow WeSEE
robots.txt
User-agent: WeSEE
Allow: /Cloudflare
# Security › WAF › Custom rules › Create rule
Expression: (http.user_agent contains "WeSEE")
Action: Skip › All Super Bot Fight Mode rules
# Also check Security › Bots: "Block AI bots" can block it regardless of robots.txt.WordPress
# WordPress serves a virtual robots.txt. Edit it with your SEO plugin:
# Yoast: SEO › Tools › File editor · Rank Math: General Settings › Edit robots.txt
User-agent: WeSEE
Allow: /nginx
# nginx serves every user agent by default.
# Make sure no rule like this blocks it:
# if ($http_user_agent ~* "WeSEE") { return 403; }Apache
# Apache serves every user agent by default.
# Make sure .htaccess has no rule like this:
# RewriteCond %{HTTP_USER_AGENT} WeSEE [NC]
# RewriteRule .* - [F,L]05 · Block
How to block WeSEE
Start with robots.txt. If WeSEE keeps showing up in your logs, block it at your CDN or web server.
robots.txt
User-agent: WeSEE
Disallow: /Cloudflare
# Security › WAF › Custom rules › Create rule
Expression: (http.user_agent contains "WeSEE")
Action: BlockWordPress
# WordPress serves a virtual robots.txt. Edit it with your SEO plugin:
# Yoast: SEO › Tools › File editor · Rank Math: General Settings › Edit robots.txt
User-agent: WeSEE
Disallow: /nginx
# In your server { } block:
if ($http_user_agent ~* "WeSEE") {
return 403;
}Apache
# .htaccess
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} WeSEE [NC]
RewriteRule .* - [F,L]
</IfModule>06 · User agents
User agents we see for WeSEE
The operator does not publish a full user agent string. Requests contain the token “WeSEE”.
07 · Verification
Is it really WeSEE?
WeSEE’s operator publishes no IP ranges or hostnames, so requests cannot be verified. Treat the user agent as a claim, and watch your logs for unusual request rates.
FAQ
Questions about WeSEE
Is WeSEE still active?
Its bot page at wesee.com/bot is no longer available. Check your logs to see if it still visits.
Should I block WeSEE?
That is your call. You can block it with "User-agent: WeSEE" and "Disallow: /" in robots.txt or on your server.
Last reviewed Oct 8, 2026