What exactly happens when Actuant “launches” my app?

An agent works through the launch checklist you'd otherwise do by hand: it writes your llms.txt, robots.txt and sitemap as a GitHub pull request, submits your app to 20 curated launch directories — filling each form live in a browser you can watch, and leaving the submit button to you. Anything that touches your code arrives as a pull request; nothing merges without your approval. Launch-copy drafting, analytics installed for you, and Stripe payments set up inside your app are on the roadmap, not shipped.

Does it work with my builder?

Yes. Actuant doesn't integrate with builders — it works on the app itself: the live URL, the GitHub repo, and your domain. If your app has a URL, Actuant can audit it; if it has a repo, Actuant can fix it. Lovable, Bolt, v0, Replit, Base44, Cursor, Claude Code, or hand-written all work the same way.

I've shipped five apps. Do I need five subscriptions?

No. One account covers your whole portfolio: the free plan covers 1 app, Launch covers 3, Portfolio is unlimited. Re-auditing an app you've already added is unlimited on every plan. The Signal dashboard that compares those apps side by side is still being built — today you get each app's audits, fixes and launch work in one place.

Will you spam directories with my half-finished app?

No. The audit runs first, and the agent only submits when your app clears the quality bar — that protects your launch and everyone else's. We maintain a curated list of directories that send real traffic, not a firehose of 400 link farms, and the agent never presses submit for you: it fills the form and hands the browser back.

What does the free plan actually include?

One app, unlimited re-audits of it, the full launch-readiness score and report with per-check fix guidance, and access to the MCP server for your coding agent. Agent runs are metered, and the free plan's usage is a one-time $5 of credit — roughly 16 deep audits — not a monthly allowance. Paid plans add a weekly usage allowance, monthly credit, and the agent doing the fixing and launching rather than just the diagnosing.

Can I share a report with someone else?

Not yet. Reports live in your dashboard behind your login today; public, shareable report links are on the roadmap. Anything on this site marked “coming soon” isn't built — we'd rather you buy the plan for what it does now.

Playbooks

SEO for AI-built apps: the SPA problem and how to fix it

AI builders ship JavaScript SPAs that look empty to crawlers. Learn why your Lovable or Bolt app may be invisible to search and AI engines, and the fixes that make it indexable.

Last updated 2026-07-18

Your app looks perfect in a browser. To a search or AI crawler that doesn't run JavaScript, it may be a blank page. This is the single biggest SEO trap for AI-built apps — and it's fixable.

The SPA problem

Lovable, Bolt, v0, and most AI builders ship a single-page app: the HTML the server sends is a near-empty shell, and the title, meta tags, content, and analytics are injected by JavaScript after load. Google renders JS eventually, but many crawlers — including several AI crawlers — don't, so they index nothing.

How to tell if you're affected

Run an Actuant audit. If the report is flagged as rendered, it means your static HTML was an empty shell that had to be browser-rendered to score. That's the exact content JS-blind crawlers can't see.

The fixes

1
Get critical content server-rendered
At minimum, ship a real <title>, meta description, and Open Graph tags in the initial HTML — not injected at runtime.
2
Serve robots.txt and sitemap.xml
So crawlers can enumerate your pages regardless of rendering. See Search indexing.
3
Publish an llms.txt
A plain-text brief every AI crawler can read without JavaScript. See AI-search visibility.
4
Consider a landing page that isn't a SPA
Even a static, server-rendered marketing page in front of your app fixes most of the visibility problem.

The goal isn't to abandon your SPA — it's to make sure the handful of things crawlers rely on (title, meta, OG, sitemap, llms.txt) exist without JavaScript.

Keep reading

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.

Search indexing

No robots.txt or sitemap means crawlers guess at your site and pages get missed. Learn what Actuant checks, the one line that accidentally blocks all crawlers, and how to fix indexing.

AI-search visibility

AI-search visibility is how findable and citable your app is inside AI answers from ChatGPT, Claude, and Perplexity. Learn why it's the new SEO and how llms.txt fits in.