When Sitewrap fetches a page from your origin — to warm cache, check health, or refresh assets — it uses a documented User-Agent that points here. It is not a visitor browser, and it is not third-party scanner traffic.
Outbound Sitewrap requests use this string. The token after the semicolon is the job that triggered the fetch.
Sitewrap/1.0 (+https://sitewrap.io/edge; preload)
Allow Sitewrap/1.0 (or this URL) in origin firewalls, bot maps, and rate limits if you want Sitewrap to warm and refresh your site. The string does not contain the word “bot”, because many default nginx maps block ~*bot.
Only Sitewrap infrastructure sends these requests. Roles you may see:
| Role | Why it runs |
|---|---|
preload | Warms HTML from your sitemap and known pages so visitors hit cache instead of origin. |
discovery | Reads sitemaps and discovers URLs during setup and refresh. |
origin-health | Checks whether your origin is reachable for status and visitor notices. |
asset-refresh / asset-warmer | Keeps CSS, JS, images, and other assets current in cache. |
mirror-css / critical-css | Captures and generates CSS used for fast first paint. |
favicon-discover / favicon-fetch | Finds and caches the site icon shown in the dashboard. |
not-found-page | Loads your configured error page template. |
queue / provisioner / site-detect | Background jobs for onboarding, site detection, and queued fetches. |
These requests come from Sitewrap edge servers on behalf of a wrapped website. They do not execute ads, run browsers, or harvest personal data beyond what is needed to cache and operate the site.
Sitewrap hides this User-Agent from the website request log so preload and health checks do not look like real visitors. Your origin logs may still show them — that is expected.
Confirm the User-Agent starts with Sitewrap/1.0 and includes this page URL. Then check the Sitewrap dashboard for that domain, or contact support with the request time and path.
Add speed, cache, analytics, and security in front of the site you already have.