Help · Projects built with AI
How to publish a website built with AI
It depends on what the AI delivered. A single HTML file goes to any hosting in minutes; a React or Vite project has to be built first; an app with a server and a database needs hosting that runs Node.js. Find out which one you have and follow the right path, instead of dropping everything into the public folder.
Reviewed on
First, find out what kind of project you have
Open the folder the AI generated. If there is only an index.html file, maybe with an images folder and a stylesheet, it is a static website. It needs nothing more than ordinary hosting.
If there is a package.json file and a src folder, it is a JavaScript project, almost always React with Vite. It has to be built (the command is usually npm run build), and what goes live is the generated folder, normally dist, not the whole project.
If package.json mentions next, express or a database, or there is an api or server folder, it is an application with a server. It needs hosting that runs Node.js, with environment variables configured, and it won't work on ordinary file hosting.
The public folder myth
Many people hear it's just a matter of “dropping it in the public folder”. But there are two different folders with similar names. The hosting's public_html is where the files the browser receives live. The public folder of a React or Next project is a folder of images and static files inside the code.
Copying the whole project into public_html makes the browser receive code that hasn't been built: you get a blank screen or a list of files. For a static site, the files go into public_html. For a React project, the contents of the build folder go there. For an app with a server, neither works.
The publishing path for each type
Static website: upload the files through the hosting's file manager or use a service like Netlify, Vercel or Cloudflare Pages, which publish the folder directly. Then connect the domain.
React or Vite: run the build on your computer, check that the generated folder opens, and upload only that folder. If the site has several routes (/about, /contact), configure the hosting to return index.html for any address. Without that, reloading an inner page gives a 404 error.
App with a server: needs Node.js hosting, the right Node version, the environment variables (API keys, database address) and a start command. Platforms that connect to GitHub and deploy on every change are usually the safest path.
After publishing: domain, padlock and Google
With the site live on a temporary address, connect your domain: in the panel where it was registered, point the A record (or the CNAME) to the hosting. The security certificate, the browser padlock, is usually issued automatically a few minutes after the domain points correctly.
Finally, check that the text shows up in the page source (right click, “view page source”). If the content only appears after JavaScript runs, Google and ChatGPT may read an empty page, and that weighs on the company being found.
When to call someone
You don't always need to. When you do, this is it.
When the build fails and the message makes no sense, when the project has a server and a database, or when the site will receive customer data, a review before launch is worth it. That's what we do with projects built with AI: we identify the type of project, publish it on your domain and leave instructions so you can keep working on it.
Related service
Projects built with AI→Review, deploy on your domain and maintenance.
Frequently asked questions
Can I publish for free?
A static website, yes: Netlify, Vercel and Cloudflare Pages have free plans with a temporary address and let you connect your domain. The domain itself is still paid. Apps with a server and a database almost always need a paid plan.
Do I need to know how to code to publish?
For a static website, no. For a React project, you run one command and follow the steps, but a build error means reading the message carefully. For an app with a server, it helps to have someone who has done it before.
Can't the AI tool publish it for me?
Some tools publish on their own address, like a Lovable link. To have your own domain, with email and certificate working, you, or someone for you, still has to connect the pieces.
How long until the domain works?
After the DNS change, usually from a few minutes to a few hours. In some cases up to 48 hours, because of internet providers' cache.
Keep going
You talk to the people doing the work
Stuck at publishing?
You talk directly to Gabriel, on WhatsApp, in English or Portuguese. Send what happened and the project or website address, if there is one.