Concepts
Why Actuant's score is deterministic
Actuant's launch-readiness score is a pure function of what's on your page — the same URL always yields the same number. Learn why the model narrates but never scores.
Last updated 2026-07-18
Actuant's score is deterministic: run the same URL twice and you get the same number, because every check is a real, rule-based inspection of your page — not a language model's opinion.
The rule: the model narrates, never scores
A model can be persuasive and wrong, and it drifts run to run. So Actuant draws a hard line: the 52 checks compute the number with plain logic, and inference is only allowed to write the narrative on top — the "do this first" line and the tailored fix advice. The numbers never pass through a model.
Why this matters to you
- Trust — a score you can't reproduce is a score you can't act on. Yours moves only when your app changes.
- Progress tracking — because the scale is fixed, re-running the audit after a fix shows the real delta, not model noise.
- Honesty — Actuant runs the same audit on its own site and shows you the failing checks. The number isn't marketing.
This is also why re-runs are the feedback loop: fix a check, run the audit again, watch the exact weight move. It's a closed loop precisely because the scoring is deterministic.
Keep reading
Audit overview
Actuant scores any app URL 0–100 across 52 deterministic launch-readiness checks — delivery, security headers, analytics, SEO, AI-search visibility, structured data, social, performance, mobile, trust, and conversion. Here's every check and how it's weighted.
Your first audit
How to read an Actuant launch-readiness report: what the 0–100 score means, how weighting works, and how to turn the per-check breakdown into a prioritised launch to-do list.
Launch readiness
Launch readiness is how prepared a deployed app is to actually receive, measure, and convert visitors. Learn the fundamentals every app needs before it's worth driving traffic to.