# How to publish an AI-generated site on Netlify

> Publish a static folder or AI-generated site on Netlify, then compare when Revdoku is simpler for protected file-folder sharing.

![Netlify service page](/assets/blog/publish-ai-site-netlify/01-service-page.png)

Netlify Drop is one of the quickest ways to put a finished static website online. You drag in a folder or ZIP and get a public `.netlify.app` link without setting up Git first.

## Before you start

Use the built output, not an unfinished framework source folder. Your upload should contain `index.html` at its root.

```text
site/
├── index.html
├── styles.css
├── app.js
└── images/
```

Open the site locally and check its links and images. A static upload cannot run a traditional server, database, or background process.

## 1. Open Netlify Drop

Go to [Netlify Drop](https://app.netlify.com/drop). The upload area accepts a project folder, a ZIP file, or a single HTML file.

![Netlify Drop upload page](/assets/blog/publish-ai-site-netlify/02-drag-and-drop.png)

## 2. Drop in the built website

Drag the complete build folder into the upload area. Netlify uploads the files and creates a temporary public URL.

Wait for the deployment to finish before closing the tab. If the published page is blank, the most common cause is uploading the wrong folder. Find the folder that contains the final `index.html` and deploy that one instead.

## 3. Test the Netlify URL

Open the generated link and check:

- The homepage loads without a directory listing
- CSS, fonts, images, and JavaScript load
- Every internal link opens
- A deeper page survives a direct refresh
- The layout works on a phone

Single-page apps may need a rewrite rule so every route falls back to `index.html`. Add the framework’s recommended Netlify redirect before the next deploy.

## 4. Claim the site

A first Drop deployment can work without an account. Create or sign in to a free Netlify account to claim the site, choose a readable name, retain ownership, and publish updates.

The Drop page explains the flow from a temporary URL to an owned project and custom domain.

![What happens after a Netlify Drop deployment](/assets/blog/publish-ai-site-netlify/03-after-deploy.png)

## 5. Add a custom domain

Inside the claimed project, open **Domain management**, add your domain, and follow Netlify’s DNS instructions. Keep the `.netlify.app` address until the custom domain is active and HTTPS is ready.

Use the official [Netlify domain documentation](https://docs.netlify.com/manage/domains/configure-domains/bring-a-domain-to-netlify/) if your DNS is hosted elsewhere.

## Update the site

For occasional changes, drag the new build into the project’s deploy area. If the website will change frequently, connect a Git repository so each push creates a deployment and pull requests can get previews.

| Check | Ready when |
|---|---|
| Upload folder | `index.html` is at the root |
| Published page | The `.netlify.app` URL opens |
| Assets | Images, CSS, and JavaScript load |
| Routes | Direct page refreshes work |
| Ownership | The site is claimed before you rely on it |

Your site is live.

Start publishing for free

Connect this AI to Revdoku so it can store files, create, update, and publish websites for me. Read and follow https://revdoku.com/prompt.md. A Revdoku account is required. If I do not have one, send me https://app.revdoku.com/users/sign_up?utm_source=revdoku.com&utm_medium=ai-chat&utm_campaign=connect_ai_first and wait until I confirm signup is complete. For ChatGPT, Claude, or another cloud AI, connect https://app.revdoku.com/mcp and complete Revdoku OAuth. For a local agent, use Revdoku's browser device sign-in and complete the connection in Revdoku. Never ask me for a password or API key in chat, or for a verification code. When Revdoku tools are connected, verify the connection, tell me you’re ready, and ask what I want to publish.

Copy Prompt

or

Create Free Account

---

[View the canonical page](https://revdoku.com/blog/publish-ai-site-netlify/) · [Browse llms.txt](https://revdoku.com/llms.txt)