Claude built your website. How do you put it online?

You have three options: upload the HTML file Claude gave you to a static host, push it to GitHub and deploy it from there, or connect Claude to a web platform so it publishes the site itself and can keep editing it later. The first is quickest for a one-off page, the second suits developers, and the third is the one that still works when you need to change your opening hours next month.

People ask this all the time. On r/ClaudeAI alone: "Claude built me a static HTML website, what do I do next?", "Best and easiest way to publish a Claude-made website and edit/add pages later?" and "Built a site with Claude. How do I deploy it and hand it over to a client?" The building part has become easy. Getting it online, on your own domain, in a way you can still change, is where people get stuck.

Option 1: Upload the file to a static host

Claude usually gives you an artifact or a single index.html. Static hosts such as Netlify, Cloudflare Pages or GitHub Pages will put that file online for free, often by dragging a folder into the browser.

Good for: a one-page site you won't change often.

Where it gets hard:

• Every change means asking Claude again, downloading the new file and uploading it again. Claude doesn't see what's live, so small edits can quietly undo earlier ones.
• Contact forms, analytics, a blog and a custom domain are each a separate job.
• Handing it to a client means handing over a hosting account and a file.

Option 2: Put it in GitHub and deploy from there

If you're comfortable with Git, or you use Claude Code, keep the site in a GitHub repository and connect it to Vercel, Netlify or Cloudflare Pages. Each commit redeploys the site.

Good for: developers, and sites with a build step.

Where it gets hard: anyone who isn't a developer can't edit the site without you. A typo fix on the "About" page becomes a commit.

Option 3: Let Claude publish it to a web platform over MCP

MCP (Model Context Protocol) lets Claude use tools from other services directly in the chat. When you connect a web platform to Claude this way, Claude can create the site, write the pages, check them and publish, and the site lives somewhere you (and Claude) can keep editing.

This is what we built Dotsy for. Here's how it works.

1. Connect Dotsy to Claude. Add https://mcp.dotsy.ai/mcp as a custom connector (in Claude: Customize → Connectors → + → Add custom connector), then sign in (Dotsy is in early access, so new accounts are let in in waves ). Full steps for Claude, ChatGPT, Cursor and Claude Code: How do I connect Dotsy to Claude, ChatGPT or Cursor?
2. Ask Claude to publish your site. In the chat where Claude built it: "Use the Dotsy connector to publish this site as a new Dotsy site." Or start fresh: "Use the Dotsy connector to build me a site for my bakery in Austin."
3. Check the draft. Claude gives you a preview link. Nothing is public until you publish.
4. Publish. Your site goes live on a free yoursite.dotsy.site address. No card needed.
5. Add your domain when you're ready (Core plan and up): How do I connect my own domain?

Already have a site somewhere else? Claude can import it instead: How do I move my existing website to Dotsy?

What about Claude Code?

If Claude Code built the site as a folder of files, it can use the same connector, or push the folder with the Dotsy CLI:

npx -y @dotsy-ai/cli@latest login
npx -y @dotsy-ai/cli@latest push my-site ./site --create --publish

push uploads only the files that changed, so later updates are quick.

How do I edit the site later?

This is the part that decides which option you'll be happy with in six months.

• Ask Claude. "Change our Saturday hours to 9–2 on every page" works because Claude reads your site's current pages through the connector before it edits.
• Click and type. In the Dotsy editor you click any text on the real page, type, and publish. No AI needed for a quick fix.
• Undo mistakes. Every publish is saved as a version, and Undo puts the previous one back: How do I undo a publish?
• Keep the AI in its lane. You choose per site whether an agent may only read, only save drafts, or also publish, and every change it makes is logged.

How do I hand the site to a client?

With options 1 and 2 you hand over hosting logins. On Dotsy you can invite the client to your workspace (every plan has unlimited users at no extra cost) or move the site into their own workspace. Their Claude, ChatGPT or Cursor can then connect to the same site.

Which option should you choose?

If you only need a single page that will never change, option 1 is fine. If you want a site you, your team and your AI can all keep working on, connect Claude to a platform built for it.

FAQ