Most AI-built web apps are client-side rendered single-page apps, so crawlers that do not execute JavaScript, including many AI crawlers, see an almost empty page. Fix this by prerendering or server-rendering public pages, giving every route its own title, description and canonical URL, publishing a sitemap, improving Core Web Vitals and structuring content with clear headings and structured data.
On this page
Lovable, Bolt, v0 and similar tools produce attractive web apps quickly, and many founders use them for landing pages, directories and content sites as well as for logged-in apps. Then the traffic does not come. Search Console shows pages "discovered, currently not indexed", social previews show the same title everywhere and AI answer engines never mention the product. The cause is usually technical, not editorial. This article explains why AI-built apps struggle with search and how to fix it.
Why AI-built apps are often invisible
Most builders generate a React single-page application with Vite. The server sends a nearly empty HTML document and a JavaScript bundle, which then renders the content in the browser. Google can render JavaScript, but rendering happens in a second phase that may be delayed, and errors in data fetching mean the crawler sees a spinner. Many other crawlers, including several used by AI search and answer engines and social networks for link previews, do not execute JavaScript at all. For them, every page of your app looks the same: a title tag, an empty div and a script.
A second issue is routing. Client-side routes often share one set of meta tags from index.html, so every page has the same title and description. Some hosts also return the index page with a 200 status for URLs that do not exist, creating soft 404s.
Separate public pages from the app
Not every screen needs SEO. Dashboards, settings and anything behind login should be excluded from indexing. Public pages, such as the home page, features, pricing, use cases, blog posts and public listings, need to be crawlable. Draw this line explicitly. A common and robust setup is a separate marketing site built with a framework that outputs static or server-rendered HTML, such as Astro or Next.js, on the main domain, with the app on a subdomain or path. Agentic tools make this split cheap: Claude Code or Codex can port existing React components into a static site generator in a day or two.
Rendering options compared
| Option | How it works | Good for | Trade-off |
|---|---|---|---|
| Static prerendering | Public routes are rendered to HTML at build time | Marketing pages, docs, blogs with a known set of URLs | Content changes require a rebuild |
| Server-side rendering | HTML is generated per request on the server | Large or dynamic catalogues, listings, user-generated public pages | Requires a server or functions and a framework such as Next.js |
| Prerendering service | A proxy serves rendered snapshots to bots | Quick fix for an existing SPA | Extra moving part, snapshots can go stale, must not differ from what users see |
| Client-side only | Browser renders everything | Logged-in app screens | Weak visibility for non-JavaScript crawlers |
A technical SEO checklist for AI-built apps
- Decide which routes are public and make sure each returns meaningful HTML without JavaScript; test with
curlor by disabling JavaScript. - Give every public route a unique title, meta description, canonical URL and Open Graph tags, set on the server or at build time.
- Return real 404 status codes for unknown URLs and 301 redirects for moved ones.
- Publish an XML sitemap and a
robots.txtthat blocks app-only areas but not CSS or JavaScript files. - Add structured data with JSON-LD where it fits, for example Organization, Product, Article or FAQPage.
- Meet Core Web Vitals on mobile, especially Largest Contentful Paint.
- Use one heading hierarchy per page, descriptive link text and alt text for meaningful images.
Speed is part of ranking signals and of user satisfaction; our guide to performance optimization for AI-generated web apps covers bundle size, images and caching.
Structure for AI answer engines
Generative search engines quote content they can parse and trust. Pages that answer one question clearly near the top, use descriptive headings, define terms, include concrete numbers and steps and name the organisation behind them are easier to cite. Avoid hiding key content in tabs, carousels or modals that only render after interaction. Accessible markup and good SEO overlap heavily here, which our article on accessibility audits for AI-generated interfaces explores.
Pitfalls to avoid
Do not block the builder's preview domain only after it has been indexed; set canonical URLs to your custom domain from the start and redirect the preview domain where possible, as described in our guide to custom domains for AI-built apps. Do not let AI generate hundreds of thin pages to target keyword variations; search engines treat scaled low-value content as spam. And do not serve bots content that differs from what users see, which counts as cloaking.
Review content and experience together
Technical fixes get you indexed; usefulness gets you ranked and cited. A structured expert review from uxreviewer evaluates whether your public pages are clear, scannable and trustworthy, with concrete action steps. If the fix requires restructuring the app, such as splitting marketing and product or introducing server rendering, the OnlineAppCreator custom development team can implement it. We apply the same principles to the products we build and launch ourselves: visibility is designed in, not bolted on.
Frequently asked questions
Can Google index a Lovable app?
Google can render JavaScript, but indexing of client-rendered apps is slower and less reliable. Prerender or server-render public pages for consistent results.
Do AI search engines read JavaScript-rendered content?
Many AI crawlers do not execute JavaScript, so they see only the initial HTML. Serving rendered HTML for public pages is the safest approach.
Should the logged-in part of my app be indexed?
No. Exclude dashboards and account areas from indexing and focus SEO on public pages such as features, pricing, use cases and content.
Is a separate marketing site worth it?
Often yes. A static or server-rendered marketing site on the main domain gives full control over SEO, while the app can remain a client-side application.