Launching an AI-built app: domain, SEO and analytics
The launch basics AI builders skip: your own domain, page titles, sitemap, share images, analytics and the app stores. A practical checklist with examples.
Tommy Pham
Short answer: before you share your AI-built app publicly, move it to your own domain with HTTPS, give every page a unique title and description, add a sitemap and robots.txt, set share images so links look right on LinkedIn and X, install analytics that tracks signups, and submit the site to Google Search Console. Most of it takes an afternoon, and none of it is done for you by default.
This is the hub for my launch guides. For security and data checks, see the production checklist.
1. Get off the preview domain
yourapp.lovable.app or something.bolt.host is fine for testing. For launch, use your own domain: it’s what people remember, what search engines build reputation for, and it stays yours if you change hosts.
→ Choosing a registrar and connecting your domain
After the switch, update every place that stores the old URL: auth redirect URLs in Supabase or Firebase, OAuth apps (Google, GitHub), payment webhooks, and email templates.
2. Make each page findable
AI builders often ship a single-page app where every URL has the same <title>. Search engines and AI assistants then see one page, not twenty.
- Unique title per page, under about 60 characters, main topic first.
- Meta description of 130 to 155 characters that says what the page offers.
- One
<h1>per page that matches the title’s intent. - Real URLs (
/pricing,/blog/post-name), not just#sections. - Pre-rendered HTML for public pages. A client-only React app shows crawlers an empty
<div>. Use a framework with static or server rendering (Astro, Next.js) for marketing pages, even if the app itself stays a single-page app.
3. Sitemap and robots.txt
sitemap.xmllists every public URL, withlastmoddates for content pages.robots.txtallows crawling and points to the sitemap.- Keep private areas (dashboards, admin) out of the sitemap, and protect them with login, not just robots.txt.
This site generates its sitemap at build time from the same data the pages use, so a new post or project can’t be forgotten.
4. Share images and structured data
When someone shares your link, LinkedIn, X and Slack read Open Graph tags:
<meta property="og:title" content="Your page title" />
<meta property="og:description" content="One-line summary" />
<meta property="og:image" content="https://yourdomain.com/og.png" />
<meta name="twitter:card" content="summary_large_image" />
Use a 1200x630 image. On this site, each case study gets its own share image, generated from its screenshot at build time.
Add structured data (JSON-LD) so search engines and AI assistants understand what a page is: Organization or Person on the homepage, SoftwareApplication for an app, BlogPosting for articles.
5. Make it readable by AI assistants
ChatGPT, Claude, Perplexity and Google’s AI features increasingly answer questions by citing pages. To be citable:
- Answer the question in the first paragraph, then explain.
- Use headings phrased as questions people actually ask.
- Back claims with specifics and sources: numbers, dates, links.
- Don’t block AI search crawlers (such as
OAI-SearchBot,Claude-SearchBotandPerplexityBot) in robots.txt if you want to appear in their answers. - Optionally publish an
/llms.txtmap of your site. It’s a community proposal that Google ignores, but it’s cheap to add. This site has one.
6. Analytics you’ll actually use
Pageviews alone don’t tell you much. Track the events that matter: signup, activation (the user did the core thing) and payment. GA4, PostHog and Plausible all work. PostHog also gives you session replays, which show exactly where new users get stuck.
Then add your site to Google Search Console and submit the sitemap. It tells you which searches show your pages and flags indexing problems.
7. Going to the app stores?
- → Publish your web app on Google Play as a TWA: reuse your PWA, no rewrite.
- → Ship an Expo app to the App Store: what AI builders don’t do for you.
FAQ
Do I need a custom domain to rank on Google?
No, but it helps. Reputation builds on the domain you own, and you keep it if you switch hosts. A free subdomain works for testing.
Will Google index a React single-page app?
Google can render JavaScript, but it’s slower and less reliable than serving HTML. Pre-render public pages to be safe, and remember that many AI crawlers don’t run JavaScript at all.
What’s the minimum analytics setup?
One tool, three events: signup, activation and payment. Add more when you have a question they can’t answer.
Launching soon and want a second pair of eyes on the setup? I do launch reviews and fixes. See my work or get in touch below.
Sources
- Google Search Central: Build and submit a sitemap and Introduction to structured data
- OpenAI: Overview of OpenAI crawlers
- llms.txt proposal