Half-built AI website? How to finish it and take it live
Short answer: An AI-built website, made with a tool such as Lovable (an AI service that writes website and app code from a chat), Bolt or v0 (two similar tools that write code from a chat), usually looks finished long before it is ready for customers. The last stretch is plain work: make sure Google can read the pages (Google Search Console, its free tool for site owners, will show you), forms reach you, secrets and data are protected, the domain and legal pages are in place, and someone owns upkeep. Work through the checklist below, then decide whether to finish it yourself or hand the last part to a developer.
Your AI-built site looks almost done, but something stops you from putting your name on it and sending customers there.
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.
A site that looks finished on screen is not the same as a site that is ready for customers. The preview shows the design. It does not show whether Google can read your pages, whether a form sends mail to a real inbox, whether a secret key is sitting in code anyone can inspect, or who fixes it next month. The gap is usually small and fixable. It is also the part AI tools are weakest at, because nobody asked them for it.
This guide is for owners of a marketing or lead site (not a complicated app) built with an AI website tool. It lists the common stalls, a go-live checklist with pass and fail checks, a rule for finish-it-yourself versus hire-help, and what to hand a developer so the job is quick. Facts about Lovable come from its own documentation as read in November 2026. For other tools, check the vendor's pages, because rules and plans change.
Why AI-built sites stall near the finish line
- The credits ran out. Tools like Lovable and Bolt meter work in credits or tokens, so a long back-and-forth to fix small details can use the plan up. See what to do when Lovable runs out of credits.
- Fixing one thing breaks another. A change to the contact page alters the header. The AI forgets earlier decisions. This is common in long chats.
- Nobody picked the "boring" parts. Forms, email delivery, analytics, a privacy page, a custom domain and a sitemap are not exciting prompts, so they never get done.
- The owner cannot read the code. You cannot tell whether a page is safe, fast or crawlable, so you hesitate to launch. That hesitation is sensible.
- A split between design and function. The site looks right but the booking, payment or CRM (customer list software) link does not work yet.
If your project is more app than website, see how to move an AI-built app to production and what finishing a half-built AI app costs. If your AI tool only produced a folder of plain files, this publishing guide covers that case.
Check 1: Can Google and AI tools read your pages
This is the one most owners miss. Lovable's docs say older projects are built with React and Vite (common web code tools) and render in the visitor's browser. Lovable serves pre-rendered copies of those published pages to verified search engines, social preview bots and AI crawlers, and its docs say tools outside that verified list see very little. Projects created from 13 May 2026 use TanStack Start, which renders pages on the server, and Lovable says eligible older projects can be upgraded. It does not let you pick a different framework, such as Next.js (another popular web framework). If you need one, you keep a Git copy (Git is a tool that tracks code changes) of the code and continue outside Lovable.
What this means for you:
- Test: in Search Console, run URL Inspection on your home page and one inner page, then look at the rendered page and the text it found. Pass: your headline and body text appear. Fail: the page looks empty or only a loading message appears.
- Check page basics. Each page needs its own title and description, one clear heading, readable web addresses and links between pages.
- Submit a sitemap. A sitemap is a list of your pages that you give to Google. Google says a sitemap helps discovery but does not guarantee indexing. For a new site with few links pointing to it, it helps.
- Remove any "noindex" setting. Test builds often tell Google not to list the page. Left on after launch, it keeps your pages out of Google.
Do not promise yourself rankings. Google says crawling can take from a few days to a few weeks, and a page being indexed (stored by Google) does not mean it ranks.
Check 2: Forms, email and tracking
Many AI-built sites show a contact form that looks perfect and sends nothing.
- Test: submit the form three times from your phone. Pass: all three arrive in the inbox you named, within a minute, and a copy lands in a place you can search later (a spreadsheet, CRM or database). Fail: any are missing or go to spam.
- Set up the sender. If the form sends email on your behalf, ask your developer to set SPF and DKIM (records that prove an email really came from you), or use a form service that handles it.
- Add analytics and a goal for form sends, then confirm a test visit and a test form show up.
- Add a thank-you message so visitors know the form worked, and an error message when it did not.
If leads vanish into a mailbox, see how to send website leads to where you follow up.
Check 3: Security and data
Lovable's docs say frontend code runs in the browser, so API keys and other secrets cannot be stored safely in it. Calls to other services should go through server-side functions that read keys from a secrets store. The docs also say misconfigured row-level security (the rules that decide which user can see which database rows) is a common cause of data leaks. Lovable runs a quick scan on publish, and offers a deeper scan you start yourself. It states that these tools help find common problems but cannot guarantee security, and that for sensitive data you should consider a professional review. You are responsible for meeting the security needs of your use.
- If the site only shows pages and sends a form: risk is small. Make sure no keys appear in the page source, and the form cannot be used to send spam at will.
- If it stores customer names, bookings, uploads or payments: get a human review before launch. See the AI-built app security checklist and the row-level security fix guide.
- Test: open the site in a private window, view the page source and search for "key", "secret" and "token". Pass: nothing sensitive shows. Fail: any key appears, which means rotate it (replace it with a new one) and move it to a server-side secret.
Check 4: Domain, hosting and ownership
- A custom domain. Lovable's hosting docs say custom domains require a paid plan. Check the plan you will be on, and see how to put an AI-built app under your own domain.
- Keep the domain in your own registrar account. Do not let a freelancer register it in their name.
- Know where the code lives. Lovable's docs say its Git sync keeps your code in your own repository, available on all plans, and that the .zip download needs a paid plan. They also say the database and uploaded files are exported separately. Switch Git sync on now, before you need it.
- Know the exit path. The docs say apps built with Lovable can be hosted anywhere, but the editor itself cannot be self-hosted. Moving the database alone does not move login, storage or functions. For the general question, see how to avoid getting locked in to an app builder.
- Back up. Keep a copy of content, images and the database outside the tool.
Check 5: Legal pages, accessibility and speed
- Privacy policy and cookie notice if you collect form data or use analytics. Rules differ by country, so check local law. See privacy policy and terms for an AI-built app.
- Accessibility. AI output is not reliably accessible. Check that images have text descriptions, that buttons can be reached with a keyboard, and that text has enough contrast. Do not claim the site meets any standard unless someone has tested it.
- Mobile and speed. Load the site on a real phone on mobile data. Pass: the main message shows quickly and nothing is cut off. Fail: large images or videos make the page crawl.
- Facts and claims. AI-written copy can be wrong. Read every price, service area, licence number and guarantee yourself.
- A 404 page and working links. Click every link in the menu and footer.
Copy-ready go-live checklist
- Home page and one inner page pass URL Inspection with text visible.
- Each page has its own title and description, one main heading.
- Sitemap submitted, no leftover noindex.
- Form tested three times, replies land in the right inbox, copy saved.
- Analytics shows a test visit and a test form send.
- No secrets in the page source, database rules reviewed if data is stored.
- Custom domain connected, HTTPS works, www and non-www go to one version.
- Code in your own Git repository, domain in your own account.
- Privacy policy and cookie notice live, if needed.
- Mobile check, speed check, accessibility basics checked.
- A named person owns updates, backups and renewals.
Finish it yourself or get help: a decision rule
| Your situation | Better route |
|---|---|
| Brochure site, no logins, no stored customer data, form only | Finish yourself with the checklist. Ask a developer for a one-off review if any check fails. |
| Site stores leads, bookings, uploads or customer logins | Hire a developer for the security and data checks, then run the rest yourself. |
| Site must connect to a CRM, calendar, payment or email tool | Hire help. Integrations fail in ways that are hard to see. |
| You are out of credits and the same bug keeps coming back | Export the code to Git and hand it to a developer rather than buying more credits. |
| You need the site to rank for local search soon | Fix the crawl checks first, then get an SEO review. Rankings are never guaranteed. |
For vendor-neutral help choosing, see how to hire a Lovable developer and half-built app: can AI finish it or do you need a developer.
What to hand a developer so the job is short
- Your Git repository link, or the .zip download.
- A list of what is done and what is not, in plain words.
- Logins for the domain registrar, analytics and Search Console, given through an invite, never by pasting passwords in chat.
- The failing items from the checklist above, with the test that failed.
- The credit and plan situation of the AI tool.
See what to give a developer taking over your AI-built app.
How I'd approach this
My rule: do not launch a site you have not tested like a customer. Run the checklist before you spend more credits, because most "one more prompt" fixes are really missing basics, not missing features.
Blur Studio finishes half-built sites and flows: it takes over the code, fixes what fails the checks, connects forms, CRM and calendar, takes the site live on your own domain, and then looks after it. If the checklist shows more problems than you want to handle, see what that includes.
First-week plan.
- Day 1: turn on Git sync and save the code, or download the .zip if your plan allows it.
- Day 2: run the Search Console check and the form test, and write down every fail.
- Day 3: view the page source for secrets, and note whether the site stores any customer data.
- Day 4: apply the decision table. Fix the items that are simple. List the ones that are not.
- Day 5: connect the domain and add the legal pages.
- Days 6 and 7: test on two phones, then launch to a small group (staff, a few customers) before you promote it.
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 does my AI-built site look finished but not work properly?
AI tools build what you ask for, and most prompts describe how a site should look. Forms, email delivery, analytics, security rules, legal pages and search setup are rarely asked for. Run the five checks above and you will usually find the gap.
Can Google read a site built with Lovable?
Lovable's docs say older projects render in the browser and it serves pre-rendered copies to verified search engines and AI crawlers, while newer projects (from 13 May 2026) render on the server. Check with Google's URL Inspection tool in Search Console, which shows what Google saw. Indexing can still take days to weeks.
Is a Lovable, Bolt or v0 site secure enough to launch?
For a brochure site with a form, usually the risk is low if no secrets sit in the page code. If you store customer data, get a human review first. Lovable's own docs say its scans cannot guarantee security. See the AI-built app security checklist.
Do I need a developer to put an AI-built website live?
Not always. A simple site with a form can go live with a custom domain and the checklist above. You need a developer when the site stores customer data, takes payments, connects to a CRM or calendar, or keeps breaking after fixes.
Can I move my AI-built website to another host?
Lovable's docs say apps built with it can be hosted anywhere, and code can sync to your own Git repository. The database and uploaded files are exported separately, and moving the database alone does not move login, storage or functions. Check your tool's docs for its own rules.
How much does it cost to finish a half-built AI website?
It depends on how many checks fail and whether data and integrations are involved. A simple review is much smaller than a rebuild. Ask for a written scope that lists each fix. For app-sized projects see what finishing a half-built AI app costs.
Will Google penalise a website written by AI?
Google says appropriate use of AI is not against its guidelines, and that using AI does not give content any special gains. It judges quality and purpose. Have a person review the facts, and do not mass-produce near-identical pages. Check Google's current guidance on AI content.
More in this topic: Websites: build, move and cost for small business (8 guides) →