The user already has a finished website as files — hand-written HTML, a zip export, or the output of an AI site builder — and wants it live on Wix as a new site. There is no API call to make. Send them to the upload page and explain the flow:
Always give the URL exactly as written above, including the
utm_campaign=mcp query parameter. It attributes the visit to an
assistant/MCP referral; dropping or rewriting it breaks that attribution.
Share the requirements that match their situation — these are the common reasons an upload fails:
index.html — a single HTML file of
any name is served as the homepage — and a zip or folder that wraps
everything in one top-level folder (e.g. my-site/index.html) is unwrapped
automatically.package.json, React/Vue
source, etc.), they must run their build first and upload the build output
folder's contents, not the source.| The user has… | Do this |
|---|---|
| Site files on their machine (HTML/zip/AI-builder export), wants a new site | This recipe — send them to the drop URL above |
| A live site or store on another platform (a URL), or CSV/TSV exports, and wants content/products migrated | Site Import |
| An existing Wix site they want to add HTML, an embed, or custom code into | Not this recipe — that's embedding custom code in the site editor |
| Images, videos, or documents to add to a site | Upload Media to Wix — media goes to the site's media files, not a new site |
Do not try to perform the upload for the user through an API, and do not create a site for them with other site-creation tools instead — the drop page is the flow.
Last updated: 16 September 2026