Which user-agent strings identify Termly?

The following user-agent strings identify Termly: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Safari/537.36 (compatible; TermlyBot/W.X; +http://www.termly.io/bot.html).

Does Termly respect robots.txt rules?

According to official documentation, Termly does not respect robots.txt rules.

How can I verify Termly traffic with live traffic data?

You can verify Termly requests by checking your server access logs for the documented user-agent strings. For accurate verification, correlate user-agent patterns with IP ranges or verification methods provided by Termly.

What is Termly?

Direct Answer: Termly bot scanners for site compliance

Operator: Termly Type: Other Bot Purpose: Web crawling

User-Agent Identification

The following user-agent strings identify Termly in your live traffic data:

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Safari/537.36 (compatible; TermlyBot/W.X; +http://www.termly.io/bot.html)

robots.txt Rules for Termly

Respects robots.txt: No

This bot does not commit to following robots.txt

Termly does not officially follow robots.txt directives. The only reliable way to control access is through server-side blocking (IP filtering, user-agent rules in your web server config) combined with log monitoring to verify effectiveness.

Need continuous verification across 500+ bots? Can AI See It automates this.

Crawl Activity Index

Relative crawl activity for Termly over the past 28 days. Higher values indicate increased crawling intensity compared to the period baseline.

View recent activity data (last 7 days)

Date	Activity Index
Mar 28, 2026	16.7
Mar 29, 2026	22.3
Mar 30, 2026	19.4
Mar 31, 2026	22.0
Apr 1, 2026	11.6
Apr 2, 2026	25.8
Apr 3, 2026	46.1

Source: Cloudflare Radar

Why track Termly traffic?

Identify and classify unknown crawler activity. Termly may appear in your live traffic data with varying frequency. Tracking its behavior helps you decide whether to allow, throttle, or block it based on actual data.

Protect your crawl budget. Every bot request consumes server resources. Understanding what Termly crawls helps you prioritize the crawlers that matter.

Log Verification

To verify Termly traffic in your live traffic data:

Search access logs for the user-agent strings listed above
Check if the IP addresses match documented ranges (if provided by Termly)
Verify the crawl pattern matches documented behavior
Use reverse DNS lookup for additional verification if available

Note: Observed behavior in production environments may differ from official documentation. Live traffic monitoring provides the only reliable verification of actual bot behavior.

Official Documentation

View Official Termly Documentation →

Information sourced from official documentation. Content generated with AI assistance.