Frequently asked questions

You pay per URL monitored — not per site. One bank domain with twelve rate pages counts as twelve URLs. Your monthly bill is your URL count times your plan’s per-URL rate; for example, 11 URLs costs less than 12. See the Pricing page and interactive calculator for tiers.

Version 1 is in development and private beta. Account registration is available; subscription billing is not enabled yet. Launch prices on the Pricing page are illustrative and may change before public billing opens.

Webmonitor is built for public rate tables, policy pages, disclosure content, and similar reference pages your team is authorized to monitor — with reliable daily checks and side-by-side diff review. Examples include public bank rate schedules, regulator disclosure pages, and insurance product disclosure pages.

Most pages are fetched directly from our infrastructure using HTTP and headless browser automation. For some difficult public pages (for example repeated 403 responses or bot-check screens), our operators may enable additional retrieval options during the private beta — only where you are authorized to monitor the content. This is not self-service in Version 1; contact us if pages fail to add or stay blocked.

Webmonitor records fetch status per URL. Blocked (403), rate-limited, and challenge-style responses may appear on Broken links or in Monitoring until access succeeds. Challenge pages may be stored so you can see that the site returned a bot-check shell rather than the real content. Authorized pages that stay blocked during beta may be candidates for operator-managed enhanced retrieval — contact support.

All plans include daily checks. A scheduled resubmit run fetches each monitored URL, compares it to the latest stored snapshot, and records a new version and diff only when content changes.

When a page changes, Webmonitor stores a side-by-side highlighted diff. You can review the full page or a text-only summary of changed fragments. Opening a diff marks it as reviewed in your Main view inbox.

Webmonitor tracks consecutive not-found responses. Pages that stay broken appear on the Broken links screen so you can review and remove them manually. URLs are not auto-deleted.

Before fetching, Webmonitor checks robots.txt for the target site. Disallowed URLs are blocked unless you explicitly authorize an override after acknowledging the Terms of Service. Blocked pages appear on a dedicated Robots.txt screen.

Yes, where supported. PDF URLs are downloaded, converted to HTML for diffing, and follow the same resubmit and review workflow as normal web pages.

During development, up to three snapshots are stored per page. Paid plan tiers on the Pricing page describe higher version limits planned for launch.