ChatGPT Made You a Website. Here's How to Put It Online

Asking an AI for a website is the easy part now. ChatGPT, Claude, or Gemini will produce a genuinely decent landing page in thirty seconds. Then comes the question every AI subreddit sees daily, in some form of: okay, it gave me the code, how do I make this a real website my customers can visit?

Here is the whole path, honestly, including the parts where a single HTML file is enough and the parts where it is not.

Step 1: see it before you ship it

Do not publish code you have never looked at. Paste it into a previewer first. MarkUpTo has a Web mode built for this: paste the code, and the site renders inside a browser frame you can switch between desktop, laptop, tablet, and phone widths.

The phone check is the one that matters most. The majority of real visitors arrive on phones, and AI-generated layouts frequently look perfect at 1440 pixels and fall apart at 390: text overflows, columns crush, buttons vanish. Catch it now, while fixing it is free. If something is broken at phone width, tell the AI exactly that: "the three feature cards overflow on mobile, stack them vertically below 640px." Specific bug reports get good fixes.

While you are previewing, do your small edits here too. Wrong wording, wrong colour, a headline you want punchier: click and change it directly instead of re-prompting, because every re-prompt rewrites the whole file and can disturb what already worked. More on that in editing without re-prompting.

Step 2: get it into a file

A website is ultimately a file on a server, so you need the code as a file. From MarkUpTo, click Download .html and you get a complete, self-contained page, with fonts and styling wired up, named and ready. (If the AI gave you a fragment rather than a full page, the download wraps it properly so it works standalone.) If you prefer doing it by hand, paste the code into a text editor and save it as index.html. That exact name matters for hosting: servers show index.html automatically when someone visits your URL.

Step 3: put it on the internet, free

You do not need to buy hosting for a single-page site. Three free options, in order of easiest first:

Netlify Drop (fastest)

1. Go to Netlify's drop page and drag your index.html onto it.
2. That is the whole process. You get a live URL like your-site-name.netlify.app immediately.
3. Make a free account to keep the site up permanently and to update it later by dropping a new file.

GitHub Pages (best if you might grow into coding)

1. Create a free GitHub account and a new repository.
2. Upload your index.html.
3. In the repository settings, turn on Pages. Your site appears at yourname.github.io/repository-name.

Cloudflare Pages (great performance, generous free tier)

Similar drag-and-drop or Git-connected deploys, with Cloudflare's network in front. Any of the three is a fine choice; Netlify Drop is simply the least clicking.

Optional: a real domain

The free URLs work, but yourbusiness.com looks better on a card than yourbusiness.netlify.app. A domain costs roughly 10 to 15 dollars a year from registrars like Namecheap, Cloudflare, or Porkbun. Buy it, then connect it in your host's domain settings; every host has a guided flow that tells you exactly which records to point where. Allow up to a day for it to take effect everywhere, though it is usually minutes.

Being honest about what one file can and cannot do

A single HTML file is genuinely enough for more than people think: a business landing page, a portfolio, an event page, a menu, a wedding site, a link-in-bio page, a product waitlist. It loads fast, costs nothing to run, and cannot be hacked in any interesting way because there is nothing behind it.

It stops being enough when you need: multiple pages with shared navigation, a blog you update weekly, user logins, payments, or content stored in a database. Those need real site builders or frameworks, and pretending otherwise would waste your time. A practical middle step: contact forms work on a static page using services like Netlify Forms or Formspree, so "people can reach me" does not require leaving the one-file world.

Updating the site later

Keep your HTML file as the source of truth. When something changes, edit the file (paste it back into the previewer, click, fix, re-download) and re-upload to your host. On Netlify that is dragging the new file onto your site's deploys page. The whole loop, edit to live, takes about a minute, and it costs zero tokens because the AI is only involved when you want genuinely new design work.

The whole journey, one paragraph

Prompt the AI for a complete single-file website. Paste the code into a previewer and check it at phone width, fixing small things by clicking. Download it as index.html. Drag it onto a free host like Netlify Drop. Share the URL, or connect a 12-dollar domain if you want to look established. Total cost: possibly nothing. Total time: the first coffee of the morning.

The five-minute pre-launch checklist

Before you drag the file onto a host, five things worth thirty seconds each, because they are the difference between "live" and "presentable":

• The browser tab title. The AI often leaves it as something generic like "Document" or "Landing Page." It lives in the title tag, shows in every tab and search result, and should say your actual name.
• The description. A one-sentence meta description is what search engines and link previews show under your title. Ask the AI to add one with your real pitch, or add it while editing.
• Phone width, again. Check 390 pixels one final time after your last edits. Edits made at desktop width have a habit of quietly breaking mobile.
• Every link. AI-generated pages love placeholder links that go nowhere, especially in footers and social icons. Click each one; delete or fix the dead ones. A mailto link with your real address is the simplest working contact method.
• Real contact info. Models scatter placeholder phone numbers and addresses that look plausible. Someone will call it.

What about being found on Google?

A static one-pager can absolutely rank for your name and niche, but be realistic about timelines: new domains take weeks to months to appear for anything competitive. The practical moves that cost nothing: a correct title and description as above, your city and service written in real sentences on the page if you are a local business, and your URL placed on the profiles you already have, since links from your social accounts help discovery. For a deeper content play, that is what a blog is for, and it is a different project than launching your one-pager tonight. Launch first.

When something breaks after deploy

Two failure modes account for most "it worked locally" complaints. If the live site loads but styling is gone, the page is probably a fragment that depended on your previewer's wrapping; re-download it as a complete .html from the tool, which bakes the framework and fonts in, and upload that. If images show locally but not live, they were pointing at files on your computer; either upload the images alongside the page and reference them by filename, or embed them into the file itself before downloading, which the previewer's image swapping does automatically. Neither problem means starting over. Both are five-minute fixes, and both are caught in advance by clicking through the live URL once on your phone before you share it anywhere.

Frequently asked questions