Bot & user agent

Every warming request identifies itself. If you run a site, this page tells you exactly what you'll see in your logs — and how to allow, filter or block it.

The user agent string

Mozilla/5.0 (compatible; WarmupRocks/1.0; +https://warmup.rocks/bot)

Two variants add a purpose marker to the string:

• … +https://warmup.rocks/bot; sitemap discovery — fetching your sitemap before a run.
• … +https://warmup.rocks/bot; domain verification — checking the verification header.

Match on the token WarmupRocks to catch all of them. The bot always sends a real, branded user agent — we don't disguise warming traffic as browser traffic.

What the bot does

• Requests only URLs from the site's public sitemap, plus URLs the project owner added manually.
• Sends plain GET requests with Accept-Encoding: gzip, br — the same shape as a real browser request, so the cached response is the one visitors get.
• Downloads the response body fully (many CDNs only cache completed responses).
• Comes from multiple geographic locations, so source IPs vary by design.

What the bot doesn't do

• No JavaScript execution — client-side analytics never sees it.
• No link following, no form submission, no POST requests.
• No crawling of unverified sites on a schedule — see Domain verification.
• No ignoring of HTTP errors: URLs that consistently fail are surfaced in the dashboard instead of being retried aggressively.

Request pacing

Runs are paced and rate-limited. A typical warming pass requests each URL once per proxy location, spread over the duration of the run — not in a burst. Once the edge cache is warm, most requests are answered by the CDN and never reach your origin at all.

Don't want us on your site?

Warming only runs for projects whose owners have proven domain ownership. If you still see WarmupRocks traffic you didn't ask for, block the user agent or email [email protected] — we'll remove the project.