WRTNBot user agent
Operated by Wrtn
WRTNBot is a user agent reported for Wrtn, an AI assistant service in South Korea.
The WRTNBot bot at a glance
- WRTNBot is operated by Wrtn and fetches a page when a person asks an AI assistant about it or shares its link.
- The robots.txt token for WRTNBot is WRTNBot.
- Blocking an AI assistant fetcher has no effect on search rankings.
- WRTNBot robots.txt support: Not documented.
- Recommendation for Generative Engine Optimization (GEO): Your choice.
What is WRTNBot?
WRTNBot is listed as an undocumented AI agent.
Wrtn has not published a crawler page.
Should you block WRTNBot?
Blocking WRTNBot is a business decision: it protects your content but can lower how well AI products know your brand.
| Effect on search rankings | Blocking an AI assistant fetcher has no effect on search rankings. |
|---|---|
| Effect on AI visibility | Blocking stops the assistant from reading your page when a user asks about it or pastes your link, so its answer falls back to other sources. |
| Follows robots.txt | Not documented |
| Recommendation | Your choice |
How to block or allow WRTNBot
Put the robots.txt rule in the file at the root of every domain and subdomain, for example https://example.com/robots.txt. The token WRTNBot is matched case-insensitively. robots.txt alone may not stop WRTNBot, so add the Nginx, Apache or Cloudflare rule as well.
robots.txt: block
# Block WRTNBot
User-agent: WRTNBot
Disallow: /robots.txt: allow
# Allow WRTNBot
User-agent: WRTNBot
Allow: /robots.txt: partial
# Keep WRTNBot out of private areas only
User-agent: WRTNBot
Disallow: /wp-admin/
Disallow: /cart/
Disallow: /checkout/
Disallow: /my-account/
Allow: /Nginx
# Nginx: return 403 to WRTNBot
if ($http_user_agent ~* "(WRTNBot)") {
return 403;
}Apache
# Apache .htaccess: return 403 to WRTNBot
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} (WRTNBot) [NC]
RewriteRule .* - [F,L]Cloudflare WAF
# Cloudflare > Security > WAF > Custom rule, action: Block
(http.user_agent contains "WRTNBot")How to verify real WRTNBot traffic
Wrtn publishes no IP list or reverse DNS pattern for WRTNBot, so the user agent cannot be verified. Anyone can send the same string. Rate-limit unusual volume instead of trusting the name.
How to find WRTNBot in your server logs
Search the web server access log for the token. The command below counts WRTNBot requests per URL on Nginx or Apache.
grep -i "WRTNBot" access.log | awk '{print $7}' | sort | uniq -c | sort -rn | head -20For a full report per AI bot, upload the log to the AI Log File Analyzer, a free tool by Justin Hà.
WRTNBot FAQ
WRTNBot uses the robots.txt token "WRTNBot". Wrtn does not publish a full user-agent string, so match the token inside the User-Agent header.
Wrtn has not documented how WRTNBot treats robots.txt. Add a robots.txt rule and back it with a server rule if the traffic matters to you.
Blocking an AI assistant fetcher has no effect on search rankings. Blocking stops the assistant from reading your page when a user asks about it or pastes your link, so its answer falls back to other sources.
Add two lines to the robots.txt file at the root of each domain and subdomain: "User-agent: WRTNBot" followed by "Disallow: /". The token is case-insensitive. Changes can take up to 24 hours to be picked up.
Not reliably. Wrtn publishes no IP list or reverse DNS pattern for WRTNBot, so anyone can send the same user agent. Rate-limit unusual volume instead of trusting the name.
Search your server access log for "WRTNBot", for example with: grep -i "WRTNBot" access.log. The AI Log File Analyzer by Justin Hà counts visits per AI bot from an uploaded log file.
Sources: Public bot registry. Last reviewed by Justin Hà.
See which of these bots actually reach your website
The AI Log File Analyzer by Justin Hà counts visits from GPTBot, ClaudeBot, PerplexityBot and other AI crawlers in your server log, for free. The GEO Technical Package sets up robots.txt, llms.txt and crawler access for AI search.
