Custom User Agent
By default, Sitepager already identifies itself in its user agent, so you do not need to configure a custom user agent to recognize or allow it. See SitepagerBot & User Agent for the default.
A custom user agent lets you change that identifier or replace the user agent entirely if you want to use your own identifier.
Where to find it
Section titled “Where to find it”The Custom user agent toggle is in the Advanced Settings section when creating or editing a scan. It is disabled by default.
How it works
Section titled “How it works”By default, Sitepager appends its own identity to the browser user agent, ending with the sitepager bot identifier. Your site can already recognize it.
When you enable a custom user agent in Browser-like (Recommended) mode, that trailing identifier becomes a label you choose:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 SitepagerBot/1.0 (your-workspace-id; my-bot-label)SitepagerBot stays in the string, so any rule matching it keeps working. You can also match your own label if you want a rule that is specific to this scan.
There is also a Raw mode where you provide the entire user agent string yourself. Sitepager sends that value exactly as supplied and does not add SitepagerBot, so your rule must match the value you supplied. Use this only if you need full control over the string.
Setting it up
Section titled “Setting it up”- Open your scan settings and go to Advanced Settings
- Enable Custom user agent
- Select Browser-like (Recommended)
- Enter a short bot identifier (for example,
marketing-site) - Check the preview to confirm the full string looks correct
- Save the scan
If your site is blocking Sitepager, see Allow Sitepager Through Your Firewall.
Default user agents
Section titled “Default user agents”If you do not set a custom user agent, Sitepager uses the browser string for the scan’s device, with its own identity appended:
| Device | Browser portion |
|---|---|
| Desktop | Chrome on macOS |
| Mobile | Safari on iPhone |
| Tablet | Safari on iPad |
Each one ends with SitepagerBot/1.0 (<workspace-id>; sitepager), so your site can identify the request without any configuration.
Use Browser-like (Recommended) unless you have a specific reason not to. It keeps SitepagerBot in the user agent, so rules that match it keep working.
Keep the bot identifier short and descriptive. Something like marketing-site is enough.
Test after adding the rule. Run a scan to confirm pages load correctly. If you still see blank screenshots or errors, the rule may not be matching. Check your server logs for the full user agent string.
Sitepager does not use static IP addresses. IP-based rules are therefore not reliable for identifying Sitepager. Use the user agent instead.