Seventeen kinds of check
Wording, elements, links, response and metadata, so a rule can express the actual requirement rather than approximating it with a text search.
Content monitoring
Write the requirement as a rule once. Auditwolf checks it against every page it captures, on the schedule you set, and keeps sealed evidence of the result whether it passed or failed.
Create a free accountRead the API docs
Required risk wording is presentPASS
Company number is presentPASS
Withdrawn offer is absentFAIL
found: “...limited time 0% offer ends...”
The problem
The wording that matters is spread across pages nobody reviews weekly. A template change reinstates an old claim, a release drops a disclosure from one layout, a withdrawn promotion survives on a page the migration missed. The first time anyone notices is usually when it is a problem.
A rule states the requirement once and is checked on every capture. It can require presence, and it can require absence, which is the half a manual review is worst at. Every result is kept with the evidence that produced it.
POST /auditwolf/v1/sites/{siteID}/rules
Authorization: Bearer ...
{
"kind": "text_not_contains",
"contains": "limited time 0% offer",
"case_insensitive": true
}
{
"kind": "element_text",
"selector": "footer .registration",
"contains": "Registered in England"
}Capabilities
Seventeen kinds, grouped by the job rather than by the parameter, so a rule says what you mean.
Wording, elements, links, response and metadata, so a rule can express the actual requirement rather than approximating it with a text search.
Require the risk warning, and require that last year withdrawn claim is gone. Absence is as checkable as presence, and usually the harder half.
The same page and rule produce the same result every time. When an outcome changes, the page changed, not the checker.
Every result records what was expected, what was found and the text around the match, so a failure points at the sentence that caused it.
Attach a monitor and it runs on your plan cadence, from daily to hourly, with pause, resume and run-now whenever you need them.
A failing check is captured and signed like any other observation, so you keep proof of the failure and of the fix that followed it.
Use cases
The wording, links and headers that carry a consequence when they change without anyone noticing.
Prove the disclosure was present on every page that needed it, on the dates it needed to be.
Check that a promotion, price or claim you retired is absent everywhere, not just on the page you remembered.
Company number, registered address and regulatory footer text present on every page that must carry them.
The link exists, and it points at the current document rather than a stale one.
Pages served over HTTPS, returning the status you expect, with the security headers you require.
Titles, descriptions, canonicals and robots directives staying as intended after a release.
The catalogue
Each kind takes its own parameters, and every result records what was expected, what was found and the text around the match.
Required text is present, forbidden text is absent, an exact phrase matches, or a pattern does. Case sensitivity is yours to set.
A CSS selector exists, the text inside it contains what it should, or a named asset is referenced by an img, script or link tag.
A link exists, or a link with particular text points where it is supposed to point.
The page returns the status you expect, is served over HTTPS, and carries the headers you require, with values you specify.
Title, description, canonical URL and robots directive are what they should be, checked as values rather than as page text.
Every result is sealed with the observation that produced it. See how the evidence works.
Pricing
Rules cost nothing extra: you are charged for the pages captured, however many rules run against them. Evidence integrity is identical on every plan, infrastructure failures on our side cost nothing, and there are no overage charges.
Questions
The details that decide whether this fits, without reading the whole reference first.
Add rules to a site. Each one names a kind, what it is looking for and where, and Auditwolf evaluates every rule against every page it captures in an audit.
Yes. Rules are deterministic and versioned, so the same page and the same rule produce the same result, and a change in outcome means the page changed rather than the checker did.
Yes. A result carries what was expected, what was found, and an excerpt of the surrounding text, so a failure is something you can act on rather than a red light.
Yes, and it is one of the more useful kinds. A rule can require that an old offer, a withdrawn claim or a discontinued product name no longer appears anywhere on the page.
Yes. Attach a monitor to a site and it runs on the cadence your plan allows, from daily to hourly, with pause, resume and run-now available at any time.
The observation is captured and sealed like any other, so you get the evidence of the failure as well as the notification. Email and signed webhooks can carry it into wherever you already work.
No. A rule proves that what you asked to be checked was or was not the case at the moment of capture. Auditwolf does not provide a legal opinion.
Create an account, add a site and state one requirement. The audit that checks it is inside your free credits.
Evidence integrity is identical on every plan, with no overage charges and no card required to start.