AI-built sites such as Lovable, Bolt and v0 can rank on Google when every page has its own title, description, H1 and canonical URL, internal links are real links, and the content is visible to crawlers. Check what Google actually renders with URL Inspection, because client-side rendering can leave pages thin. Google still recommends server-side or pre-rendering.
By the SEO Company Bangkok team, technical SEO · Updated 27 October 2026
AI website builders have made it possible to launch a polished site in an afternoon. Many founders then discover a problem a few weeks later: Google has indexed the home page and little else, or every page shows the same title in search results. This guide explains why that happens and what to fix, based on Google’s own documentation and on a real Lovable-built site we worked on.
A note on scope: Lovable, Bolt and v0 change quickly, and each offers different hosting, rendering and pre-rendering options. Check your platform’s current documentation before you choose a fix. What follows is what Google documents and what happened on our project.
Why do AI-built sites often under-index?
Most AI builders generate JavaScript applications, commonly React. In a basic setup, the server sends the browser an almost empty HTML “app shell”, and JavaScript then builds the page in the browser. This is called client-side rendering.
Google can render JavaScript, but its JavaScript SEO basics guide explains that it happens in stages: crawl, then render, then index. Rendering can be delayed, and anything that fails to load in that step is missing from what Google sees. The common symptoms on AI-built sites are:
- every URL shares one title and description set in the app shell
- content appears only after a click or a script that Google does not run
- navigation uses click handlers instead of real
<a href>links, so Google cannot discover pages - the server returns 200 for URLs that should be 404
Google’s guide notes that server-side rendering or pre-rendering is still a good idea, because it makes content available faster to users and to all crawlers, not just Google.
How do you check your site in 10 minutes?
You need Google Search Console access for the site. Then:
- Open URL Inspection and enter an important inner page, not the home page.
- Check the indexing status. “URL is on Google” is what you want. “Crawled – currently not indexed” or “Discovered – currently not indexed” are warning signs.
- Click “Test live URL”, then “View tested page”. Look at the rendered HTML and the screenshot.
- Compare the rendered HTML with what users see. Is your main text there? Are your headings there? Is the title specific to this page?
- Check the links. Search the HTML for
<a href=. Your menu and in-text links should appear as real links. - Repeat for two or three other page types (a service page, an article, a contact page).
If the rendered HTML is thin or the titles are identical, you have found your main problem.
What per-page basics did Koh Mak get right?
Koh Mak Inside Information is a travel guide and accommodation site for an island in the Gulf of Thailand. It was built and edited with Lovable. In the Koh Mak case study, the first job was per-page foundations. Across the 47 pages we crawled:
| Element | Koh Mak after the work |
|---|---|
| Title tag | Unique on every page, leading with the search term |
| Meta description | Unique on every page |
| H1 | One per page, matching the page’s main question |
| Status code | 200 on every page |
| Canonical | Each page points to itself |
If any of those terms are unfamiliar, our technical SEO glossary explains canonicals, status codes and the rest. For how these on-page basics combine with links and mentions from other sites, see on-page and off-page SEO.
Are your internal links, sitemap and robots crawlable?
Once each page stands on its own, make sure Google can find them all.
- Real links. Every menu item and in-text link should be an
<a>element with anhref. Buttons that change the view with JavaScript do not count as links for discovery. - Clean URLs. Use path URLs such as
/where-to-stay, not fragments like/#/where-to-stay, which Google treats as the same page. - An XML sitemap listing every indexable URL, submitted in Search Console.
- robots.txt that does not block your JavaScript, CSS or content folders.
- Real 404s. A missing page should return a 404 status, not a 200 with a “not found” message.
Why consolidate www, non-www, http and https?
If your site answers on several hostnames, for example with and without www, or on both http and https, Google may treat them as separate URLs and split signals between them. Choose one version, redirect the others to it with a 301, and make canonicals and sitemaps use only that version. On Koh Mak this was listed as a next step after the first 30 days, because the per-page basics came first.
How do you write pages that answer engines can quote?
Indexing gets you into Google. Being quoted in AI answers needs pages built around real questions. On Koh Mak, pages were built or rebuilt for what travellers ask before booking: Koh Mak vs Koh Kood, how to get there, and where to stay. Each page leads with a short direct answer, then the detail.
The same approach works for any AI-built site: one question per page, a 40–60 word answer under the heading, then supporting detail and tables. Our AEO and GEO checklist walks through it week by week.
Do speed and Core Web Vitals matter?
Yes, as part of overall page experience. Google’s Core Web Vitals measure loading (Largest Contentful Paint), responsiveness (Interaction to Next Paint) and visual stability (Cumulative Layout Shift). The targets are set out on web.dev’s Web Vitals page. AI-built sites often ship large JavaScript bundles and unoptimised images, so check them. Our sister agency Digital Agency Bangkok has a guide to Core Web Vitals and INP on Thai sites.
When should you add pre-rendering or move stacks?
Work through these in order:
- Fix per-page metadata and links first. Many sites index well once each page has its own title, H1, canonical and real links.
- Add server-side rendering or pre-rendering if URL Inspection still shows thin rendered HTML. Check which options your platform and host support today.
- Consider moving stacks if the platform cannot deliver crawlable HTML or the controls you need. For guidance, see Digital Agency Bangkok on when to move to WordPress or Laravel.
What were the results on Koh Mak?
For the whole site, impressions rose from 2,105 to 3,372 (+60%) comparing 18 Aug–18 Sep 2026 with the previous 30 days. Two pages show what the basics can do:
| Page | Impressions before | Impressions after | Position before | Position after |
|---|---|---|---|---|
| Where to stay on Koh Mak | 56 | 768 | 31.5 | 4.3 |
| Direct booking page | 11 | 322 | 13.3 | 1.9 |
Source: Google Search Console, 18 Aug–18 Sep 2026 vs the prior 30 days. Full details are in the Koh Mak case study.
Frequently asked questions
Can a Lovable site rank on Google?
Yes. The Koh Mak site was built with Lovable and grew impressions 60% in 30 days once each page had its own title, description, H1 and canonical, with crawlable links and question-led content.
Do I need to leave Lovable, Bolt or v0 to rank?
Not usually. Fix per-page basics and check rendering first. Moving stacks is a last step, only when the platform cannot deliver crawlable HTML.
Why does Google show the same title for all my pages?
Your app probably sets one title in the shared app shell. Each route needs its own title and description in the rendered HTML.
Built your site with AI and need it indexed?
We audit and fix AI-built sites as part of our SEO services, working inside your builder’s workflow so design and speed stay intact. SEO services start from ฿12,000/month.