The launch-readiness audit
The launch-readiness audit: 52 checks, explained
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.
Last updated 2026-07-19
The audit is 52 deterministic checks. Each one inspects your live page — its HTML, its real response headers, or a well-known sibling URL like /robots.txt — and returns pass / partial / fail with human-readable evidence. Every check carries a weight; the weights add up to 172 points, which is normalised to a 0–100 score.
No model decides the numbers. Inference only writes the narrative on top — the score is a pure function of what's on your page, so it's reproducible and honest.
Where the points are
Checks are grouped into categories. The audit runs and reports in this order:
| Category | Checks | Points |
|---|---|---|
| Reachability & delivery | 6 | 19 |
| Security | 8 | 15 |
| Measurement | 1 | 16 |
| Search (SEO) | 11 | 42 |
| AI-search visibility | 4 | 19 |
| Structured data | 2 | 5 |
| Social & identity | 6 | 16 |
| Performance | 5 | 11 |
| Mobile | 2 | 6 |
| Trust & legitimacy | 5 | 14 |
| Conversion | 2 | 9 |
| Total | 52 | 172 |
How scoring works
A pass earns the check's full weight, a partial earns half, a fail earns zero. Your score is your earned points divided by the 172 available, rounded to a whole number. Because Analytics carries the single largest weight (16), it is almost always the biggest single jump available.
Timeouts don't count as failures
Slow or unreachable sibling files (robots.txt, llms.txt) score as "couldn't reach — partial", not "missing". A network timeout is never counted against you as an absent file.
All 52 checks
This list is generated from the audit engine itself, so it is always exactly what runs against your site. Every check is also explainable in-product and over MCP with explain_check.
Reachability & delivery
6 checks, 19 of the 172 points.
| Check | Weight | Group |
|---|---|---|
| Reachability & speed | 6 | Availability |
| HTTPS enforced | 6 | Transport |
| Compression | 2 | Transport |
| Modern HTTP | 1 | Transport |
| Redirect hygiene | 2 | Transport |
| Asset caching | 2 | Transport |
Security
8 checks, 15 of the 172 points.
| Check | Weight | Group |
|---|---|---|
| HSTS | 3 | Headers |
| Content-Security-Policy | 3 | Headers |
| MIME-sniff guard | 2 | Headers |
| Clickjacking guard | 3 | Headers |
| Referrer-Policy | 1 | Headers |
| Permissions-Policy | 1 | Headers |
| No version leak | 1 | Hardening |
| security.txt | 1 | Hardening |
Measurement
1 check, 16 of the 172 points.
| Check | Weight | Group |
|---|---|---|
| Analytics | 16 | Analytics |
Search (SEO)
11 checks, 42 of the 172 points.
| Check | Weight | Group |
|---|---|---|
| Title & description | 8 | Metadata |
| Canonical URL | 4 | Metadata |
| Indexable | 4 | Metadata |
| Title length | 3 | Metadata |
| Description length | 3 | Metadata |
| robots.txt & sitemap | 8 | Indexing |
| Single H1 | 3 | Structure |
| Heading order | 2 | Structure |
| Image alt text | 3 | Structure |
| Internal links | 2 | Structure |
| Language declared | 2 | Structure |
AI-search visibility
4 checks, 19 of the 172 points.
| Check | Weight | Group |
|---|---|---|
| llms.txt | 8 | Crawlers |
| AI crawlers allowed | 4 | Crawlers |
| Readable without JS | 5 | Rendering |
| Semantic landmarks | 2 | Rendering |
Structured data
2 checks, 5 of the 172 points.
| Check | Weight | Group |
|---|---|---|
| Structured data | 3 | Schema |
| Organization schema | 2 | Schema |
Social & identity
6 checks, 16 of the 172 points.
| Check | Weight | Group |
|---|---|---|
| Social preview | 6 | Open Graph |
| Open Graph completeness | 3 | Open Graph |
| Twitter card | 2 | |
| Favicon | 3 | Identity |
| Apple touch icon | 1 | Identity |
| Web app manifest | 1 | Identity |
Performance
5 checks, 11 of the 172 points.
| Check | Weight | Group |
|---|---|---|
| Document weight | 2 | Weight |
| Third-party scripts | 2 | Weight |
| Render-blocking scripts | 3 | Loading |
| Lazy-loaded images | 2 | Loading |
| Image dimensions | 2 | Loading |
Mobile
2 checks, 6 of the 172 points.
| Check | Weight | Group |
|---|---|---|
| Mobile viewport | 5 | Viewport |
| Theme color | 1 | Viewport |
Trust & legitimacy
5 checks, 14 of the 172 points.
| Check | Weight | Group |
|---|---|---|
| Privacy policy | 3 | Legitimacy |
| Terms | 2 | Legitimacy |
| Company identity | 2 | Legitimacy |
| Contact method | 3 | Contact |
| Social presence | 4 | Contact |
Conversion
2 checks, 9 of the 172 points.
| Check | Weight | Group |
|---|---|---|
| Payment path | 6 | Payments |
| Primary call to action | 3 | Call to action |
Deep dives
The heaviest checks have a page of their own — what they verify, why it matters, and how to fix them:
Analytics
Weight 16 — The heaviest single check — you can't launch blind.
Title & description
Weight 8 — Your search result, in your words.
robots.txt & sitemap
Weight 8 — robots.txt + sitemap.xml.
llms.txt
Weight 8 — The llms.txt brief for AI crawlers.
Social preview
Weight 6 — The Open Graph card.
Reachability & speed
Weight 6 — Clean, fast first byte.
Payment path
Weight 6 — A visible way to pay.
Social presence
Weight 4 — Linked, live profiles.
Mobile viewport
Weight 5 — Render correctly on phones.
Favicon
Weight 3 — Don't look unfinished.
Keep reading
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.