Base44 launch checklist: what to check before you share your app

1. Is your app indexable at all?

If your Base44 app renders in the browser with JavaScript, Googlebot's first pass sees an empty page. AI crawlers (ChatGPT, Perplexity) don't run JavaScript at all. The fastest check: open your live URL and use View Page Source (Cmd+U). If you see an empty root element and little else, nothing is being indexed.

The fix depends on how Base44 serves your app. If it supports server-side rendering or static generation for public pages, enable it. If not, a pre-render service can generate static HTML snapshots of your key pages and serve them to crawlers.

2. Metadata: title, description and Open Graph

A page with a default or missing title shows up in search results as the URL itself, which nobody clicks. Every public page needs:

• A specific `<title>` — not "My App" or the builder's default. Include your product name and what the page is for.
• A `<meta name="description">` — the snippet under the search result. Write it as a real sentence that tells someone what's on the page, not a keyword list.
• Open Graph tags — og:title, og:description, og:image, og:url. These power link previews when you share the URL in a chat, on social media, or in a directory listing.

3. Sitemap and robots.txt

A sitemap is a list of your URLs that search engines can read in one request. Without it, Google has to discover your pages through links from other sites — and a new app has none. Generate a sitemap.xml with your public routes and reference it from robots.txt.

Also check that robots.txt isn't blocking everything. A generated deploy sometimes ships with Disallow: / — which tells every crawler to go away. That's a one-line fix and a total indexing blocker.

4. Security headers

A generated app typically ships with no security headers. The ones that matter for a launched app:

• Content-Security-Policy. Restricts which scripts can run on your page. The most important defense against XSS.
• Strict-Transport-Security. Forces HTTPS. Without it, the first visit over HTTP is unprotected.
• X-Frame-Options. Prevents your app from being framed on another site (clickjacking).
• Referrer-Policy. Controls what URL info leaks when users click outbound links.

If your Base44 app doesn't let you set HTTP headers directly, you can add them through your hosting platform (Netlify, Vercel, Cloudflare) as response headers on every request.

5. Analytics that actually fires

It's common for the analytics snippet to be present in the code but never actually send events — it's installed, not running. Actuant watches the real network requests your deployed page makes and can tell "no analytics" from "installed but silent." If you're using a tool like PostHog or Plausible, open the network tab on your live URL and confirm you see events being sent.

6. AI visibility

Being indexed by Google and being recommended by ChatGPT are different problems. AI assistants cite apps they find in directories, comparison articles, and trusted sources. The two highest-leverage things you can do:

1. 1

   Add an llms.txt

   A markdown file at yourapp.com/llms.txt that tells a language model what your app is and which pages are worth reading. See the llms.txt guide for the format.

2. 2

   Submit to directories

   AI assistants train on and retrieve from app directories. Being listed on the right ones puts your app in the sources models pull from. Actuant can submit your app to directories with a live browser session.

How to run the full checklist

Every item above maps to a deterministic check in Actuant's audit. It loads your deployed URL in a real browser, reads the raw HTML, grades every header, checks for analytics activity, probes for data leaks, and scores the whole thing 0–100. The report shows each check as pass or fail with the exact thing to fix.