Bot intelligence record

Alertsite by Smartbear

Usually allow

Use the AlertSite identifier to separate Smartbear uptime, accessibility, or site-health monitoring traffic from normal visitor requests in server logs.

Monitoring Monitoring Verified Bot Confidence: Medium Verified: Yes robots.txt: No

User-Agent Pattern

Smartbear
AlertSite

Robots.txt Snippet

Copy-ready
User-agent: AlertSite Disallow: /

Handling Guidance

No

This bot is usually safe to allow when the request source is verified and the traffic matches your site policy.

Uptime checks, managed website monitoring, synthetic tests, accessibility scans, or site-health reviews.

Record Details

Structured data
Operator
Smartbear
Family
Smartbear
Type
Monitoring
Purpose
Monitoring
Identity type
Verified Bot
Confidence
Medium
Last verified
2026-04-01
Last checked
2026-05-20
Source type
Verified Directory
Spoofing risk
User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.

Notes

Alertsite by Smartbear is listed in the Botcrawl directory as a monitoring bot from Smartbear. The primary identifier for log review is AlertSite.

Identification

  • User-agent pattern: AlertSite
  • Family: Smartbear
  • Type: Monitoring
  • Kind: Monitor

Common use

Uptime checks, managed website monitoring, synthetic tests, accessibility scans, or site-health reviews.

Verification and handling

Confirm the user-agent against server logs and use published operator documentation, IP ranges, reverse DNS, or other trust signals when available.

Directory guidance marks the risk level as Safe and the blocking decision as No. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.

Robots.txt handling: No.

Evidence and Source

  • Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
  • Match `AlertSite` as a case-insensitive substring in HTTP user-agent logs. Use bot_http_agent for full user-agent examples when the client sends a longer browser-like string. Do not treat a user-agent match alone as proof of identity for allow-listing.
  • Uptime checks, managed website monitoring, synthetic tests, accessibility scans, or site-health reviews.
  • User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.

WordPress Bot Protection

Bot Blocker for WordPress

Monitor bot traffic, review live activity, and control AI crawlers, scrapers, scanners, spam bots, and fake trusted bots from one clean WordPress dashboard.