Getting started
Supported builders (Lovable, Bolt, v0, Replit & more)
Actuant audits apps shipped by any builder. It auto-detects Lovable, Bolt, Base44, Replit, v0, Cursor, and Claude Code, and renders JavaScript SPA shells so single-page apps score on their real content.
Last updated 2026-07-19
Actuant audits any public URL, from any stack. It also detects the builder that shipped your app so the fix advice matches the tool you actually use.
Auto-detected builders
- Lovable
- Bolt
- Base44
- Replit
- v0
- Cursor
- Claude Code
Why single-page apps still score correctly
Most AI builders ship a JavaScript SPA shell — the initial HTML is nearly empty, and the title, meta tags, and analytics get injected at runtime. A naive crawler would score that as a blank page.
Actuant detects an empty shell and escalates to a browser render, then scores the real DOM. Your report flags when this happened, so a Lovable or Bolt app is judged on what visitors and crawlers actually see — not on the empty skeleton.
The shell is what many crawlers see
Crawlers that don't render JavaScript (including some search and AI crawlers) still see the empty shell. That's exactly why checks like server-side title, meta, and llms.txt matter even when your app "looks fine" in a browser.
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.
Title & description
A missing <title> or meta description means Google writes your search result for you — badly. Learn what Actuant checks, how long each should be, and how to set them in any builder.
AI-search visibility
AI answers from ChatGPT, Claude, and Perplexity are where discovery is moving. An llms.txt file is how they read your site accurately. Learn what Actuant checks and how to write one.