Trae user agent
Operated by ByteDance
Trae is a user agent reported for Trae, ByteDance's AI coding IDE, when it fetches web pages.
The Trae bot at a glance
- Trae is operated by ByteDance and loads web pages in a browser to complete tasks on behalf of a user.
- The robots.txt token for Trae is Trae.
- Blocking an AI agent has no effect on search rankings.
- Trae robots.txt support: Not documented.
- Recommendation for Generative Engine Optimization (GEO): Your choice.
What is Trae?
Trae reads documentation and pages that its AI assistant needs.
ByteDance has not published a crawler page for it.
Should you block Trae?
Blocking Trae 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 agent has no effect on search rankings. |
|---|---|
| Effect on AI visibility | Blocking stops agents from completing tasks on your website for their users, which can cost bookings or sales that agents would have made. |
| Follows robots.txt | Not documented |
| Recommendation | Your choice |
How to block or allow Trae
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 Trae is matched case-insensitively. robots.txt alone may not stop Trae, so add the Nginx, Apache or Cloudflare rule as well.
robots.txt: block
# Block Trae
User-agent: Trae
Disallow: /robots.txt: allow
# Allow Trae
User-agent: Trae
Allow: /robots.txt: partial
# Keep Trae out of private areas only
User-agent: Trae
Disallow: /wp-admin/
Disallow: /cart/
Disallow: /checkout/
Disallow: /my-account/
Allow: /Nginx
# Nginx: return 403 to Trae
if ($http_user_agent ~* "(Trae)") {
return 403;
}Apache
# Apache .htaccess: return 403 to Trae
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} (Trae) [NC]
RewriteRule .* - [F,L]Cloudflare WAF
# Cloudflare > Security > WAF > Custom rule, action: Block
(http.user_agent contains "Trae")How to verify real Trae traffic
ByteDance publishes no IP list or reverse DNS pattern for Trae, 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 Trae in your server logs
Search the web server access log for the token. The command below counts Trae requests per URL on Nginx or Apache.
grep -i "Trae" 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à.
Trae FAQ
Trae uses the robots.txt token "Trae". ByteDance does not publish a full user-agent string, so match the token inside the User-Agent header.
ByteDance has not documented how Trae treats robots.txt. Add a robots.txt rule and back it with a server rule if the traffic matters to you.
Blocking an AI agent has no effect on search rankings. Blocking stops agents from completing tasks on your website for their users, which can cost bookings or sales that agents would have made.
Add two lines to the robots.txt file at the root of each domain and subdomain: "User-agent: Trae" followed by "Disallow: /". The token is case-insensitive. Changes can take up to 24 hours to be picked up.
Not reliably. ByteDance publishes no IP list or reverse DNS pattern for Trae, so anyone can send the same user agent. Rate-limit unusual volume instead of trusting the name.
Search your server access log for "Trae", for example with: grep -i "Trae" 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.
