Text, visual and rules
A normalised text diff, a visual score from comparing the previous screenshot, and any rule that flipped between pass and fail. Three answers to "what changed", not one.
Change monitoring
Know what changed, and prove it changed
Auditwolf checks your pages on a schedule and tells you what moved: the text that differs, how much the page shifted visually, and any rule that flipped. Every change arrives with evidence somebody else can verify.
Create a free accountRead the API docs
- Text, visual and rule changes
- Noise filtered by policy
- Daily to hourly
- Every change is evidence
/terms · observed 19 Aug 10:07Material change
REVIEW- Capital is at risk. Returns are not guaranteed.
+ Returns are not guaranteed.
- TEXT
- 0.41
- VISUAL
- 0.02
- RULE
- PASS → FAIL
The problem
An alert that says something changed is not much use
Most change monitoring tells you a page is different and shows you a diff. That is fine until the page has a carousel, a timestamp, a visitor counter or a price that moves daily, at which point every run is a change and the alerts become something you filter into a folder and stop reading.
Auditwolf classifies the change instead. Text and visual scores are measured separately, rules record whether they flipped, and a materiality policy decides what deserves your attention. What survives is a small number of changes that matter, each with evidence attached.
POST /auditwolf/v1/sites/{siteID}/monitors
Authorization: Bearer ...
{
"name": "Terms and disclosures",
"cadence": "daily",
"change_policy": {
"min_text_change": 0.02,
"ignored_selectors": [".cookie-bar", "#visitor-count"],
"ignore_numbers": true,
"notify_only_on_rule_change": false
}
}Capabilities
What arrives when something moves
The classification, the filtering and the record, rather than a notification and a link to a diff.
A policy for what matters
Minimum text and visual scores, ignored selectors, ignore numbers, or notify only when a rule changes state. Tune out the carousel and the timestamp without tuning out the page.
On a schedule you set
Daily to hourly depending on the plan, with run-now, pause and resume. Archiving a monitor keeps its history rather than discarding it.
History that survives a move
Observations are tied to the logical page, so changing a URL does not restart the record and comparisons still work across the move.
Every change is evidence
The observation behind an alert is hashed, signed and timestamped like any other, so a change is something you can prove rather than something you noticed.
Into your workflow
Email with per-account preferences, and signed webhooks with delivery history, retry and secret rotation, so changes land where the work already happens.
Use cases
Pages worth watching
Anywhere a change has a consequence, and finding out late is the expensive part.
Your own site after a release
Catch the disclosure a template change dropped, or the claim a rollback reinstated, before anyone else does.
Terms and policy pages
Know when a supplier, processor or platform changes the document you agreed to, with proof of both versions.
Competitor pricing and claims
Track what a competitor publishes, on a schedule, with a record of what it said and when.
Regulated wording drift
Alert only when a rule flips, so routine editing stays quiet and a missing risk warning does not.
Partner and franchise pages
Watch pages published in your name by people who do not tell you when they change them.
Post-incident verification
Confirm a correction actually went live everywhere, and keep the evidence that it did.
Watching for specific wording?
A change policy tells you when a page moved. A rule tells you whether the thing you require is still there, which is a different and usually more useful question.
Need to prove it later?
Every observation behind a change is hashed, signed and timestamped, and can be verified by somebody with no account and no reason to trust us.
Pricing
One credit per successful page capture
A monitor costs what its captures cost, so a daily monitor over ten pages is ten credits a day. Infrastructure failures on our side cost nothing, there are no overage charges on any plan, and evidence integrity is identical on every plan including the free one.
Questions
Before you integrate
The details that decide whether this fits, without reading the whole reference first.
What counts as a change?
Text is normalised and diffed into hunks, the new screenshot is compared with the previous one for a visual score, and any rule that flipped between pass and fail is recorded as a transition. You see all three.
How do I stop being alerted about noise?
A monitor carries a change policy. Set a minimum text or visual score before a change counts, ignore elements by CSS selector, ignore numbers so counters and prices do not trigger, or notify only when a rule changes state.
How often does it check?
On the cadence your plan allows, from daily to hourly, and you can run a monitor immediately at any time. Monitors can be paused, resumed and archived without losing their history.
What happens if the URL changes?
The history follows the logical page rather than the address, so a move does not start the record again and you can still compare what that page said before and after.
Do I get proof, or just a notification?
Both. Every observation is captured and sealed the same way as any other audit evidence, so the change comes with a record somebody outside your company can verify.
How do changes reach my team?
Email with per-account preferences, and signed webhooks with delivery history, retry and secret rotation, so a change can open a ticket or post to a channel rather than sit in an inbox.
Can I monitor a site I do not own?
Yes, for any publicly reachable page. Crawling follows sitemaps and links within the boundary you set, and respects robots.
Start watching your first page
Create an account, add a site and attach a monitor. The first run is inside your free credits.
Evidence integrity is identical on every plan, with no overage charges and no card required to start.