New: SEO & AEO scanning — see how Google ranks you and how ChatGPT, Claude & Perplexity cite youSee how it works
AEO for vibe-coded apps is the practice of making AI-generated websites readable, quotable, and citable by AI answer engines like ChatGPT, Claude, and Perplexity. It matters because vibe-coded apps are disproportionately invisible to those engines: the same AI tools that build your app ship it in a form AI crawlers cannot read.
There's a real irony here, and it's worth sitting with: apps built by AI are the apps least visible to AI.
TL;DR
If you ask "what is AEO" in general, we have a full primer. This post is about the specific, structural problem with AI-built apps. Four defaults conspire against you:
Lovable and Bolt scaffold Vite/React single-page applications. The HTML document those apps serve is essentially:
<!doctype html>
<html>
<head><title>My App</title></head>
<body>
<div id="root"></div>
<script src="/assets/index-a1b2c3.js"></script>
</body>
</html>
Everything users see is assembled by JavaScript in the browser. But AI crawlers fetch pages the cheap way — HTTP request, parse the HTML, move on. GPTBot, ClaudeBot, and PerplexityBot do not run your JavaScript. What they index is the empty shell above. Your content, for their purposes, does not exist.
AI builders don't generate robots.txt entries for AI crawlers, don't create sitemaps for multi-route SPAs, and have never heard of llms.txt. The engines that would cite you can't even find the front door.
Schema.org JSON-LD is how engines resolve what your product is — name, category, pricing, FAQs. AI-generated apps ship none of it unless you explicitly prompt for it.
AI builders write interface copy, not answers. AI engines lift short, self-contained, factual passages. A hero that says "Supercharge your workflow ✨" gives an answer engine nothing to quote.
Work through these five layers in order — each one depends on the previous.
This is the hard prerequisite. Options by situation:
vite-plugin-prerender and similar), or put a prerendering proxy in front for bot user-agents.Test it the way a crawler experiences it:
curl -s https://yourapp.com | grep -i "your actual content"
If your content isn't in that response, no AI engine has ever read it.
Explicitly allow the AI crawlers and point at your sitemap:
User-agent: GPTBot
Allow: /
User-agent: OAI-SearchBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Google-Extended
Allow: /
Sitemap: https://yourapp.com/sitemap.xml
A plain-text file at /llms.txt that tells AI engines what your product is, what it does, and where the important pages are. Think of it as a README for answer engines. Keep it factual and current — one consistent product description, your pricing, your key URLs.
Minimum viable JSON-LD for a product site: Organization + WebSite sitewide, SoftwareApplication (with offers) on the homepage, FAQPage wherever you answer questions. AI editors generate valid JSON-LD reliably when asked — then validate with Google's Rich Results Test.
Every public page should open with a direct answer (≤50 words) to the question the page targets, carry a visible FAQ, and show when it was last updated. Engines lift passages that are already shaped like answers.
Don't guess — measure twice:
Readability comes first. Tracking mentions of a site engines can't read just measures zero with extra steps.
It's Answer Engine Optimization applied to AI-generated apps: making a Lovable, Bolt, v0, or Cursor-built site technically readable (rendered HTML, crawler access, llms.txt, structured data) and content-wise quotable for AI answer engines, so ChatGPT, Claude, and Perplexity can cite it.
Because AI builders default to client-only rendering, which serves AI crawlers an empty HTML shell, and they generate none of the crawler signals (robots rules, sitemaps, llms.txt, schema) engines rely on. A WordPress site from 2015 is more AI-readable than most 2026 vibe-coded apps.
No — it's the same direction. Server-rendered HTML, structured data, fast pages, and answer-shaped content improve classic Google rankings and AI citability simultaneously. The work pays twice.
Crawlers typically re-fetch within days to weeks; citation depends on whether your content actually answers questions people ask. Freshness signals (visible updated dates, accurate dateModified) and entity consistency speed up trust. Expect weeks, not hours — and verify with a re-scan immediately rather than waiting.
Usually, yes. Prerendering public routes, adding robots.txt + llms.txt, and injecting JSON-LD are all additive changes. The only deep change is rendering architecture, and even that can be scoped to public pages while your app stays an SPA behind login.
Paste your URL and get a security report in 30 seconds. 100+ automated checks with AI-powered fix prompts.
Scan your site freeRelated articles
SEO gets you ranked. AEO gets you cited by ChatGPT, Claude, and Perplexity. Where they overlap, where they diverge, and how to win both in one workflow.
AEO (Answer Engine Optimization) is how you get cited by ChatGPT, Claude, Perplexity, and Google AI. What it is, how it differs from SEO, how to optimize.
Client-only SPAs are invisible to AI crawlers. The exact steps to make a vibe-coded React SPA rank in ChatGPT, Perplexity, and Claude: prerendering, robots.txt, llms.txt, schema, answer-first content.