Skip to content

How it works

How to monitor website changes

Tell RegressionRadar which page to check and how to check it. Each scheduled measurement adds another piece to the story of your website.

Free forever

Start with a free plan.

No obligations whatsoever. The free plan stays free forever.

You can always use the Free plan within its monthly allowances. Upgrading to a paid plan starts with a free trial period of 5 days.

From setup to investigation

Four steps to make website changes easier to follow.

  1. 01

    Add your web monitor

    Give it a name, enter the page URL, choose a probe method, and set the measurement interval. Enable the monitor when you are ready to start checking.

  2. 02

    Choose what matters

    Use HTTP content to monitor the response, optionally selecting part of an HTML page. Choose a screenshot probe when the rendered appearance matters.

  3. 03

    Build a measurement history

    Each check records a result. Matching HTTP status and content hash continue the same streak; a change to either starts a new streak.

  4. 04

    Review changes and configure alerts

    Investigate recorded results with text diffs or screenshot comparisons when captures are available. Add email or Teams notification rules to hear about streak changes.

Choose the right probe

Each monitor uses one method. Choose it to match the page and the question you want to answer.

HTTP content

Checks the HTTP response and hashes its content. Useful for pages, APIs, and responses where the text or markup matters.

  • Detect HTTP status and content changes.
  • Optionally select HTML elements with a CSS selector.
  • Review stored content and textual differences.

Full-page screenshot

Uses Chromium to capture the rendered page. Useful when you want to track how a page looks in the browser.

  • Detect changes in captured image bytes.
  • Review thumbnails and available screenshots.
  • Compare captures to inspect appearance changes.

Keep your checks focused

A detected change is a starting point for investigation.

Dynamic content changes too

Clocks, rotating banners, and other changing content can start new streaks. For HTTP checks, a CSS selector can help focus on stable HTML.

Your first check sets the baseline

The first-ever streak does not send a change notification. Subsequent streak changes are evaluated against your notification rules.

Plan for your usage

Measurements and notifications share monthly credits. HTTP checks use 1 credit, screenshots use 5 credits, and each sent notification uses 1 credit. More frequent checks use more credits.

Try a practical monitoring guide

Follow a worked example with screenshots from the application.

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.