AI Artifacts & Generated Sites

AI-Generated Website

Definition

Ask for a site and you get files, not magic. The common output is a single page — header, sections, a contact form, some styling, occasionally a bit of script for a menu or a carousel — with the CSS in a style tag and any JavaScript in a script tag. Multi-page output arrives as several HTML files linking to each other with relative paths, which works on a static host as long as every filename matches its link exactly. There is nothing unusual in the code itself: a browser cannot tell it was generated, search engines index it like any other page, and it can be edited by hand afterwards. What generation does not produce is the parts a site normally needs a service for. A contact form is markup and nothing more until something is standing behind it to receive the message.

Why It Matters

For a small site — a business page, an event, a portfolio, a landing page — generation removes the part that stops most people, which is producing a decent-looking first draft. That draft is often live within an hour, against a week of evenings with a template. The traps are consistent: forms that appear to work but send nowhere, placeholder text that survives into production, images referenced by names that do not exist, and invented details in the copy. Checking those four things takes ten minutes and prevents most of the embarrassment.

How It Works

Save the generated page as index.html, put it alongside any images and additional pages it refers to, and upload the lot. A static host answers the root of your address with index.html and serves each other file at its own path, so about.html appears at /about.html. Links between pages must use relative paths and the exact filename, including case: a link to About.html will 404 on a host whose file is about.html, even though it worked on your desktop. Add the small things generation usually skips — a favicon, a meta description, Open Graph tags so the link previews properly when it is shared. For the form, either point it at a form-handling service and let it post there, or replace it with an email address, because a static host has nothing to run when the form is submitted.

Real-World Example

A cabinetmaker describes his workshop and gets a four-page site: home, gallery, process, contact. He drops the folder onto 99helpers, which keeps the structure intact and serves it at oakfield-joinery.99helpers.site, then points his own domain at it. The generated contact form posted to a URL that did not exist, so he swapped it for a mailto link and a phone number — thirty seconds of editing that saved him every enquiry sent in the first week.

Common Mistakes

  • Publishing a generated contact form without a receiving service — the page shows a thank-you message and quietly loses every submission
  • Leaving image tags pointing at filenames that were never generated — the page comes up with broken icons where the photographs should be
  • Ignoring case in links between pages — desktop file systems often ignore it and web servers do not, so a site that worked locally breaks the moment it is uploaded
  • Keeping the model's invented copy — an address, a founding year or a testimonial that reads well but is not true is worse than a blank section

Related Terms

Put a file online in seconds

Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.

Host a file free →