HTTP and HTML change monitoring
Track the page content that matters.
Watch pricing, release notes, policy text or product information with scheduled HTTP checks. Select a section of HTML to keep unrelated changes out of the comparison.
Find meaningful changes in a busy page
Start with a question such as: did this price or announcement change?
A page can change its terms, remove a product or publish a release note while remaining available. Checking the HTTP status alone misses that. RegressionRadar compares both status and response content, then groups matching results into streaks.
For HTML, you can monitor the entire response or supply a CSS selector such as main .price. Selecting a stable section helps keep a changing footer or unrelated news feed from dominating your history.
Set up a focused HTTP monitor
The selector is optional; a blank selector keeps the original response.
- 01
Add the page URL
Create a web monitor and choose HTTP content. Set its name, interval and timeout, and enable it when ready.
- 02
Select the relevant HTML
Enter a CSS selector if you want only part of the response. Selection runs on the returned HTML without executing scripts or loading resources. Make sure the target element exists in that response, not only in the browser after JavaScript runs.
- 03
Check the first result
Review the stored content to confirm that your selector captured the right section. The first-ever streak sets the baseline and sends no change notification.
- 04
Review changes and set notification rules
A change in HTTP status or content hash starts a new streak. Compare available historical content with the text diff and configure email or Teams rules. Changing a selector preserves history and follows the same streak and notification rules.
Examples of focused HTML monitoring
Select the smallest useful section that answers your question.
Pricing and product information
Watch a public product page with .product-price or an availability section. A changed price or label starts a new streak even if the page still returns 200. Check that the selector also captures currency or context you need.
Release notes and announcements
Select the release-notes area to follow additions and removals. If the page appends every release, the whole selected history changes; the text diff helps identify what was added when content is stored.
Terms and policy text
Select main on a policy page to compare the published markup over time. Review the diff yourself: a text change does not automatically explain its legal or operational significance.
Before: <span class="product-price">US $29</span>
After: <span class="product-price">US $35</span>
This illustrative selection changes the monitored content even though the surrounding page may be identical.
Know what is being compared
HTTP content is the response, not the browser-rendered appearance.
- CSS selection requires a
text/htmlresponse. Invalid selectors or selections that match nothing fail the measurement; they do not silently fall back to the full page. - Selected elements are serialized as outer HTML in document order. Attributes and markup changes count, even if the visible wording stays the same.
- Scripts are not run. Use screenshot monitoring for content or layout that only appears after browser rendering.
- Dynamic values inside your selected region still trigger changes. Select stable content; there is no field-level ignore rule for arbitrary text.
- Response and selection sizes are bounded. Responses over the download limit fail; content over the storage limit can be hashed without being stored. Diffs need both historical bodies to be available.
- Periodic checks can miss short-lived changes between runs. Notification rules evaluate streak changes rather than every individual measurement.
For JSON or other public endpoint responses, see API response monitoring.
Plan the cost of your checks
Choose a schedule, then leave room for notifications and your other monitors.
Each HTTP check uses 1 credit, including failed checks. Each successfully sent email or Teams notification uses 1 credit. Failed or skipped notifications use none.
For one URL over a 30-day month, daily checks use 30 credits; hourly checks use 720 credits, before alerts. Actual totals depend on the number of days and completed checks. Adding monitors multiplies the check budget.
The Free plan includes 50 credits per month: up to 50 checks if you spend the entire allowance on this method and send no notifications.
- Bronze: 1,000 credits per month at US $9.99 per month, excluding VAT.
- Silver: 10,000 credits per month at US $19.99 per month, excluding VAT.
- Gold: 100,000 credits per month at US $29.99 per month, excluding VAT.
Credits are shared across all monitors and sent notifications and reset each calendar month (UTC). An action needs enough credits for its full cost; when the allowance is exhausted, checks and alerts pause until the next month or a plan upgrade. A paid plan has an end date; Free limits apply after expiry.
Compare plans, trial and extension terms and review usage forecasts in your account before increasing check frequency.
Explore monitoring by use case
Start with the change you need to detect, then choose the right probe.
Screenshot monitoring
Track landing pages, product availability and visible layout changes with full-page Chromium captures.
HTTP and HTML change monitoring
Watch pricing, release notes or important page sections with response comparisons and CSS selectors.
API response monitoring
Follow public JSON responses and status changes without rendering a browser page.
Start for free
Make the next change easier to spot.
Choose a page and start monitoring with the free plan. No obligations whatsoever. Free forever.
