Is your AI-built site (Lovable, Bolt, v0) ready for real customers?

By Ranjit Bhinge, founder of Blur Studio · Updated · 10 min read

Short answer: An AI-built site, made with a tool such as Lovable (a service that writes website and app code from a chat), Bolt (a similar chat-to-code tool) or v0 (another chat-to-code tool that publishes to a hosting company called Vercel), is ready for customers only after you check six things: search settings, forms, speed, security, legal pages and ownership. It often looks finished long before it passes them. Run the checklist below on the live address, not the preview, and fix any failure before you spend on ads.

Ranjit Bhinge

You built a site with an AI tool, it looks good on your screen, and you want to know what could still go wrong once real customers and Google see it.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Most AI-built sites fail in the same quiet ways. The page looks right, but the contact form sends mail to nowhere, Google cannot read the text, the page loads slowly on a phone, or a secret key sits in code that anyone can view. None of these show up when you look at the preview. All of them cost you customers.

This page lists the common gaps, how to test each one in a few minutes with free tools, and what counts as a pass. It covers sites built with Lovable, Bolt and v0, and the same checks work for any AI builder. If you want the shorter version aimed at agencies handing a site to a client, see the 20-point quality control checklist. If your site is half built, start with finishing a half-built AI website.

Why it looks ready but is not

An AI builder is good at the visible part: layout, text, colors. It is weaker at the invisible part: how search engines read the page, where form data goes, who can see your database, and what happens when something breaks. Lovable's own documentation says strong search performance still needs regular review, and that new projects start with generic page titles and descriptions. Its security notes say scans do not guarantee a site is secure and recommend a professional review if you hold sensitive data. That is the vendor being straight with you, and it is a good reason to test.

Also be clear about what you have. Some tools give you a finished site on their own hosting. Others give you code you must put somewhere yourself. The checks below apply either way, but who fixes what changes. See what to do when an AI tool hands you files if that is your case.

This is the most common reason a Lovable site is not ranking or a Bolt website shows nothing in Google. Several different problems look the same from the outside.

How the page is built

Some AI tools build a single-page app, which sends the browser a nearly empty page and then fills it in with code. Search engines and AI assistants can struggle with that. Lovable's docs say apps created from 13 May 2026 use server-side rendering, which means the server sends fully built text on every request. Older Lovable apps built with React and Vite are pre-rendered only for verified crawlers, and unverified bots see the empty app. Check which kind you have by viewing the page source (right-click, then View Page Source). If you see your headings and paragraph text in the source, search engines can read it. If you see only an empty container and script files, treat this as a fail and ask your builder or a developer about server rendering or pre-rendering.

The basics Google needs

  • Published, on a real domain. Lovable says unpublished projects and its own branded addresses do not appear in search, and recommends a custom domain for building a presence.
  • Not blocked. A file called robots.txt tells crawlers what to skip. A stray "Disallow: /" line blocks everything. Open yourdomain.com/robots.txt and read it. Google's own guidance says robots.txt is not a way to hide a page, and that a blocked page cannot show its noindex tag, so a blocked page can still linger in results.
  • A sitemap. A sitemap is a list of your pages for Google. Lovable says new projects always get a robots.txt but not always a sitemap. Google says a sitemap helps most on a new site with few links, and does not guarantee indexing.
  • Real titles and descriptions. Each page needs its own title (under about 60 characters) and description. Generic placeholder text on every page is a common fail.
  • Search Console. Google Search Console is Google's free tool for site owners. Add your site, submit the sitemap and use URL Inspection on your home page. Google says indexing can take from a few days to a few weeks, repeated requests for one page do not speed it up, and "Request indexing" has a daily limit.

Be patient and realistic. Being indexed is not the same as ranking. If your site is new and not showing, work through the steps in why a new AI-built site is not showing on Google.

Gap 2: The contact form does not reach you

A form that fails silently is the most expensive gap, because you never learn about the lost enquiries. Common causes: the form posts to nothing, the email goes through an unauthenticated sender and lands in spam, or it sends to a wrong address.

Gmail's sender rules, in force since February 2024, ask every sender for SPF or DKIM (two ways a domain proves its mail is real) and a low spam rate, and ask bulk senders for DMARC (a rule that tells receivers what to do with mail that fails the check). A simple site form is not a bulk sender, but unauthenticated mail still lands in spam folders.

Test it like this:

  1. Submit the form from your phone on mobile data, using a Gmail address and then an Outlook address.
  2. Pass: the message reaches the real inbox of the person who will answer, within two minutes, with the sender's reply address correct. Fail: nothing arrives, it goes to spam, or the reply goes to a no-reply address.
  3. Check that submissions are also stored somewhere you can see, such as a database table or a sheet. Never rely on email alone.
  4. Add spam protection, such as a hidden field or a challenge, because bots find public forms fast.

More on forms, booking and payments is in forms, booking and payments on your website. If enquiries already vanish into a shared inbox, see enquiry follow-up for small firms.

Gap 3: It is slow on a phone

Google's Web Vitals guidance sets "good" targets measured for most real visits: the biggest item on the page appears within 2.5 seconds (called LCP), the page responds to a tap within 200 milliseconds (INP), and the layout does not jump around (CLS, under 0.1). AI builders often add heavy images, many fonts and large scripts.

Test: open PageSpeed Insights (Google's free page test) on your home page and your most important landing page, on the mobile tab. Pass: all three measures are in the green range. Fail: LCP over 4 seconds, which web.dev calls poor. Usual fixes: shrink and compress images, set the biggest image to load first without lazy loading it, cut unused scripts and fonts, and use a content delivery network (servers that cache your site near the visitor). More in hosting, speed and security for small business websites.

Gap 4: Security and data exposure

Code on a website is visible to anyone who looks. That means a secret key, a password or an admin address placed in the front-end code is public. Lovable's docs say secrets must not live in front-end code and that database access rules (called row-level security) must be configured. If you use a database, such as Supabase (a hosted database service many AI builders connect to), a table left open can let strangers read customer data.

Test: search your project for words like "key", "secret", "token" and "password". Log out, then try to reach any admin or customer page by its web address. Ask the builder to list every database table and who can read it. Pass: no secrets in front-end code, no customer data readable without login. Fail: anything else, which you fix before launch. Details are in the AI-built app security checklist and, for Lovable and Supabase, the row-level security fix. Be wary of any article that quotes a percentage of insecure AI-built apps without naming its data.

  • Privacy policy and terms. If you collect names, emails or phone numbers, you need a privacy policy that matches what the site really does. See privacy policy and terms before launch.
  • Cookie consent. Rules differ by place: the UK and EU lean on opt-in consent, while US state laws are mostly opt-out, and California treats a browser privacy signal as a valid opt-out. Check local law and the regulator's page. See cookie banners and consent.
  • Accessibility. AI builders do not reliably produce accessible code. WAVE, a free checker, states "Only a human can determine true accessibility", so use it as a start. WCAG 2.2, the web accessibility standard, includes a minimum touch target of 24 by 24 pixels. Do a quick check: use only the keyboard (Tab key) to reach every button and form field, zoom to 200 percent, and look for text that is hard to read. See accessibility basics.
  • Claims and AI-written text. Google says AI content is not banned, but outputs "may contain inaccuracies" and must be reviewed. Check every price, service area, licence number and claim on every page. See whether Google penalizes AI-written pages.

Gap 6: Ownership, backups and who maintains it

Ask who holds the domain, hosting login, code copy and database. Hosted AI tools bill by plan and by credits, so a stopped subscription can take the site down. Know how you would move it. Check your tool's plan page to see whether a custom domain needs a paid plan. Read who owns your website and how to export it, and set up backups, since a deleted database is hard to recover (see AI-built app backups).

Copy-ready go-live checklist

AreaTestPassFail
Search readingView page source on the live addressHeadings and text visible in sourceEmpty container and scripts only
Crawl rulesOpen /robots.txt and /sitemap.xmlNo site-wide block, sitemap loads"Disallow: /" or sitemap missing
TitlesCheck each key pageUnique title and description per pageSame text everywhere
Search ConsoleInspect home page URLSite added, sitemap submittedNot added
FormSubmit from phone, two mail providersInbox in under 2 minutes, stored copySpam, nothing, or no-reply
SpeedPageSpeed Insights, mobileLCP 2.5 s or less, INP 200 ms or lessLCP over 4 s
SecretsSearch code, log out and probeNone exposed, data privateAny key or open table
LegalRead the pagesPolicy matches real data useTemplate text, mismatch
AccessibilityKeyboard, zoom, WAVEAll controls reachable, no errorsTrapped focus, tiny text
FactsA named person reads every pageSigned offUnchecked claims
OwnershipList domain, host, code, databaseYou hold the loginsA freelancer or tool holds them
BackupsRestore onceRestore worksNever tested

Worked example with made-up numbers

A plumber's AI-built site gets 40 visits a day from a small ad. The form is broken: mail goes to spam. Suppose 3 percent of visits would normally become an enquiry, which is about 1 a day, around 30 a month. If half of them are lost and a job is worth 300 dollars with a one-in-three close rate, the loss is 15 lost enquiries x one-third x 300 = 1,500 dollars a month, against an ad bill that kept running. These numbers are invented to show the method. A ten-minute form test would have found it.

Who can skip parts of this

  • A throwaway demo or an internal tool needs only the security and ownership checks.
  • A brochure site with no form and no logins can skip the database checks.
  • A site that will never need Google traffic, for example one shared by QR code, can skip search work.

How I'd approach this

Do not argue about whether an AI-built site is "good enough". Test it. If it passes the table above, launch. If it fails on security or ownership, fix those first, because they can hurt you today. If it fails on several areas and the code is tangled, a rebuild may cost less than patching, and the rebuild or fix decision rule helps you choose. For a bigger picture on running a real app, read making a vibe coded app safe for real users.

Blur Studio finishes half-built AI sites: the form, search settings, security, legal pages and handover, with ongoing care if you want it. You can see what that includes.

First week plan.

  1. Day 1: View source, robots.txt and sitemap on the live address. Fix blocks.
  2. Day 2: Add Search Console, submit the sitemap, write real titles and descriptions.
  3. Day 3: Test the form from two mail providers. Fix sending and add a stored copy.
  4. Day 4: Run PageSpeed Insights on mobile. Compress images and remove unused scripts.
  5. Day 5: Run the security and ownership checks. Move any secret out of front-end code.
  6. Day 6: Read every page for false claims. Add privacy policy, consent and accessibility fixes.
  7. Day 7: Fill in the table. Launch only when every row passes, then recheck in Search Console after two weeks.

Related guide: the mobile layout fix checklist.

I'm not a lawyer, accountant or other licensed adviser, and this page is general information, not advice. Rules and prices differ by country and change often, so treat it as a direction to think along, and please check with a lawyer or the relevant regulator before you act on it.

Questions people ask

Why is my Lovable site not ranking on Google?

There are usually several causes. The site may be unpublished or on a branded address, blocked by robots.txt, missing a sitemap, or showing generic titles. Older Lovable apps pre-render only for verified crawlers, while apps created from 13 May 2026 use server rendering, per Lovable's docs. Google also says indexing can take days to weeks, and being indexed does not mean ranking. See why a new site is not showing on Google.

What are the most common Bolt website issues?

The same ones as other AI builders: a form that sends nothing, generic page titles, slow images, secrets in front-end code, and a custom domain that may need a paid plan. Check what form handling your Bolt project actually has, and test it. See hiring a Bolt developer if you want help.

Is an AI-built website safe for customer data?

Only if you check. Lovable's docs say its scans do not guarantee security, and that secrets must stay out of front-end code and database access rules must be set. If you hold sensitive data, get a professional review. See the security checklist.

How long until Google shows my new AI-built site?

Google says crawling can take from a few days to a few weeks, and that requesting indexing again for the same page does not speed it up. Submitting a sitemap helps on a new site. Ranking takes longer and cannot be promised.

Do I need a developer to launch an AI-built site?

Not always. A simple brochure site can pass the checklist with your own effort. Get help if you take payments, hold customer data, use logins, or fail the security checks. See vibe coding versus hiring a developer.

Does Google penalize AI-built or AI-written sites?

Google says AI content is not banned and that it judges quality, not the method. It warns that outputs may contain inaccuracies and that mass-producing low-value pages can break its spam policy. Review every page. See does Google penalize AI-written pages.

Is my AI-built site accessible?

Do not assume so. Free tools such as WAVE catch some problems, but WAVE itself says only a human can determine true accessibility. Test with the keyboard and at 200 percent zoom. This is information, not legal advice.

Should I rebuild or fix my AI-built site?

Fix it if it passes most checks and the code is understandable. Rebuild if security and structure both fail. Use the rebuild or fix decision rule.

More in this topic: Websites: visitors, leads, hosting and AI search for owners (9 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…