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.

The launch-readiness audit

robots.txt & sitemap.xml: letting search engines in

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.

Last updated 2026-07-19

This weight-8 check fetches your /robots.txt and /sitemap.xml and confirms crawlers are both allowed in and pointed at your pages.

What Actuant checks

/robots.txt responds, and does not disallow the whole site (Disallow: /).
/sitemap.xml responds and contains a real <urlset> or <sitemapindex>.
Both present → pass. One present → partial. A Disallow: / that blocks every crawler → fail ("you're invisible on purpose").

A separate Indexable check (weight 4) catches the other way to hide: a <meta name="robots" content="noindex"> left on the page.

The one line that hides you

The most common self-inflicted wound: a leftover Disallow: / from a staging config, shipped to production. It tells every search engine to skip your entire site. Actuant flags this explicitly.

Why it matters

Without a sitemap, crawlers discover pages only by following links — slow, and easy to miss deep pages. Without a sane robots.txt, you're relying on defaults. Together they cut indexing time from weeks to days.

How to fix it

1
Serve robots.txt
Allow crawlers and point at your sitemap. In Next.js, add a robots.ts that returns rules; most builders have a toggle.
2
Serve sitemap.xml
List your real URLs. Next.js generates one from a sitemap.ts; builders usually auto-generate.
3
Submit in Search Console
Add the site to Google Search Console and submit the sitemap URL to kick off indexing.

robots.txttxt

User-agent: *
Allow: /

Sitemap: https://yourapp.com/sitemap.xml

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.

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.

SEO for AI apps

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.