How to publish a ChatGPT HTML website

Turn the answer into real files

Ask ChatGPT to provide a complete file tree, not one giant snippet. A simple site normally needs index.html, 404.html, and assets/styles.css. Add assets/app.js only when the page genuinely needs browser behavior.

Keep links relative and verify capitalization. A file named Logo.PNG may work on one laptop while a link to logo.png fails on a case-sensitive host.

my-site/
├── small-site.json
└── site/
    ├── index.html
    ├── 404.html
    └── assets/
        ├── styles.css
        └── app.js

Use a manifest that matches the files

{
  "spec": "small-static-site/1",
  "name": "my-useful-site",
  "framework": "plain",
  "site": {
    "title": "My useful site",
    "description": "A short, accurate description",
    "language": "en",
    "basePath": "/",
    "indexable": true
  },
  "build": { "profile": "static-files", "source": "site", "output": "site" },
  "routing": { "mode": "files", "notFound": "404.html" },
  "network": { "connect": [], "images": [], "media": [], "fonts": [], "frames": [] },
  "environment": { "publicBuildVariables": [] },
  "quality": { "accessibility": "WCAG2.2-AA" }
}

Test the same thing visitors will receive

• Open the built index page and follow every local link.
• Check the page at phone and desktop widths, with a keyboard, and with reduced motion enabled.
• Confirm there are no placeholders, invented contact details, secrets, source maps, or development-only URLs.
• ZIP the manifest and site directory at the archive root—not a parent folder containing the project.