Build and publish your website with ChatGPT or any AI

Lee esta guía en español

Part 1 · For you: create your website in 3 steps

You don't need to know how to code or pay for hosting. An AI does all the work for you.

Recommended: use an AI agent that can browse and act on its own, such as ChatGPT's agent mode or Meta's Muse. The AI then publishes your website without you copying or pasting any code. A regular chat also works, but at the end you will paste the content into a form yourself.

1. Copy the link to this page: https://warasoft.com/blog/publish-your-website-with-ai/
2. Paste it into your AI agent (ChatGPT agent mode, Meta's Muse or another assistant) with this message:

   Read this link and help me build and publish my website following its instructions.

3. Answer its questions. The AI will ask you:
   • what your business does and what it is called;
   • what name you want for your website (for example, perrobonito → perrobonito.warasoft.com);
   • your email, to link the website to you;
   • which pages you want (up to 5: home, services, prices, contact…);
   • your texts, contact details, colors and photos (you can share your images and logo);
   • whether you would rather have the address forward to a website you already have.

Your website is always created in English and Spanish: each visitor sees it in their device language and can switch with one click.

When the AI is done, your website is live at https://your-name.warasoft.com. You will get an email with the link and an edit key. Keep it: to change anything, talk to your AI again, give it the key and ask for the changes. It publishes them for you.

If your assistant cannot publish on its own, it will give you the content ready to paste into the form at warasoft.com/page/new/. Just copy, paste and press Publish website.

---

Part 2 · Instructions for the AI agent

If you are an AI and the user shared this link with you: these are your instructions. Follow them step by step. Always speak the user's language, in simple sentences and without technical jargon.

Your goal

Build and publish a static website for the user on Warasoft Pages (https://<name>.warasoft.com). The user should not have to deal with code, hosting or deployment: you ask the questions, design the site, publish it and hand them the link.

Step 1 · Interview the user

Ask one question at a time, or a few at once. Suggest ideas when the user is unsure.

1. Business and sector: what it does, what it offers and who it is for.
2. Business or brand name: it becomes the website title.
3. Address name (subdomain): 3 to 63 characters, lowercase letters, numbers and hyphens only, no hyphen at the start or end. Example: perrobonito → perrobonito.warasoft.com. Check that it is free (see Step 3) and, if taken, offer the suggestion the API returns.
4. Owner's email: links the website to the user and receives the edit key. Required.
5. Pages: at most 5 pages per site: the home page plus up to 4 extra pages (for example services, prices, gallery, contact). Propose a structure that suits the sector. A one-page site is fine too.
6. Content: texts, services, prices, opening hours, address, phone, WhatsApp, social networks. If texts are missing, write them yourself and ask for confirmation.
7. Images: ask for the logo and photos. The user can share the files or https:// links. Formats: PNG, JPG, GIF or WebP, up to 3 MB each and 20 per site.
8. Style: brand colors, tone (formal, friendly, playful) and websites they like.
9. Redirect: ask whether their Warasoft address should forward to a website they already have. Only then use redirect_url (it must start with https://): visitors go straight to that address and do not see the pages. You still have to send a simple html for the home page, because it is required.
10. Languages: the site is always created in English and Spanish. Ask for the texts in the language the user prefers and translate them yourself into the other one.

Before publishing, show a summary (name, subdomain, email, pages, images) and ask for confirmation.

Step 2 · Build the site

Mandatory rules. Anything that breaks them is removed automatically when publishing.

• Always in Spanish and English. Every page has a Spanish version (title, html) and an English version (title_en, html_en), with the same design and translated content. Warasoft serves the version that matches the visitor's device language (other languages get English). If the English version is missing, the API answers 400.
• Language switch: add a link to change language to the menu of every page: ?lang=en labeled English in the Spanish version, and ?lang=es labeled Español in the English version. The choice is remembered across pages.
• Warasoft credit: Warasoft automatically appends a horizontal, centered banner, “Built with warasoft.com” or “Construido con warasoft.com”, with the language switch at the end of every page. Do not hide or duplicate it. Let it be the last element on the page.
• HTML and CSS only. Do not use JavaScript: <script>, attributes such as onclick, javascript: links, <iframe>, <form> and <input> are removed.
• CSS inside <style> tags in each page's HTML. Google Fonts are allowed with <link rel="stylesheet" href="https://fonts.googleapis.com/...">.
• Each page is sent as the content of the <body> (with its <style>). Warasoft adds <html>, <head>, <meta charset>, <meta viewport> and the <title>.
• Mobile-first, responsive design with good contrast and readable text.
• Links between pages: / for the home page and /<slug>/ for the others (for example, /services/). Use the same menu on every page.
• Contact without forms: use mailto:, tel: and https://wa.me/<number> links for WhatsApp.
• Images: use https:// URLs or uploaded images, served at /assets/<file-name>. Names are normalized to lowercase with hyphens: Logo Final.PNG → /assets/logo-final.png.
• Page slugs: lowercase letters, numbers and hyphens, up to 40 characters; assets is reserved.
• Size: at most 500 KB of HTML per page.
• Do not include analytics, tracking pixels, embedded videos or third-party content that needs scripts.

Step 3 · Publish

Pick the method that matches what you can do:

A. If you can make HTTP requests (JSON API). This is the preferred method. Agents with a cloud terminal or browser, such as ChatGPT's agent mode or Meta's Muse, can do it with curl or fetch.

1. Check the subdomain:

GET https://warasoft.com/api/pages/availability/?subdomain=perrobonito

Response: {"subdomain": "perrobonito", "available": true} or, if taken, "available": false with a "suggestion".

1. Create the site:

POST https://warasoft.com/api/pages/
Content-Type: application/json

{
  "email": "owner@example.com",
  "subdomain": "perrobonito",
  "title": "Perro Bonito · Peluquería canina",
  "html": "<style>...</style><nav>... <a href=\"?lang=en\">English</a></nav><main>...</main>",
  "title_en": "Perro Bonito · Dog grooming",
  "html_en": "<style>...</style><nav>... <a href=\"?lang=es\">Español</a></nav><main>...</main>",
  "pages": [
    {"slug": "services", "title": "Servicios", "html": "...", "title_en": "Services", "html_en": "..."},
    {"slug": "contact", "title": "Contacto", "html": "...", "title_en": "Contact", "html_en": "..."}
  ],
  "redirect_url": ""
}

201 response: url, the pages list with the address of each page, and edit_key (starts with wpk_). The key is also emailed to the owner. If the subdomain is taken you get 409 with a suggestion.

1. Upload the images (needs the email and the edit_key). You can already reference them in the HTML of the previous step as /assets/<name> and upload them right after with those same names:

curl -X POST https://warasoft.com/api/pages/perrobonito/assets/ \
  -F email=owner@example.com \
  -F edit_key=wpk_... \
  -F files=@logo.png \
  -F files=@photo-1.jpg

201 response with the public URL of each image. Uploading another image with the same name replaces it. If an image is rejected, the response explains why in errors and the rest are saved anyway: fix that file and upload it again with the same name. The page shows the image as soon as it exists.

If the image is at a public https:// URL (for example, a link the user gave you), send JSON and Warasoft downloads it:

POST https://warasoft.com/api/pages/perrobonito/assets/
Content-Type: application/json

{"email": "owner@example.com", "edit_key": "wpk_...", "url": "https://example.com/logo.png", "filename": "logo"}

The full OpenAPI specification is at warasoft.com/api/pages/openapi.json, useful to set up an Action in a custom GPT.

B. If you can use a browser. Open warasoft.com/page/new/ and fill in: Owner email, Name (subdomain), the home page title and HTML in Spanish and English (Home page title/HTML · Spanish and · English), the extra pages (Slug plus its title and HTML in both languages), Images (attach the files) and, only if needed, Redirect to. Press Publish website. The result shows the addresses and the edit key.

C. If you cannot publish on your own. Give the user each part in a separate, labeled code block (home page title, home page HTML and, for each extra page, its slug, title and HTML). Tell them to open warasoft.com/page/new/, paste each block into its field, attach their images with the file names you used and press Publish website.

Step 4 · Hand over

Share the address of the website and of every page with the user. Remind them that the edit key was sent to their email, that they should not share it publicly and that they will need it for future changes. If something does not look as expected, fix it and update the site.

Updating a site

PATCH https://warasoft.com/api/pages/perrobonito/
Content-Type: application/json

{"email": "owner@example.com", "edit_key": "wpk_...", "html": "...", "html_en": "...", "pages": [...]}

• Send only what changes: title, html, title_en, html_en, pages and/or redirect_url. When you change a text, update both versions.
• pages replaces all extra pages: always send the full list, each with both versions.
• With the right key, the change goes live immediately (200).
• Without a key, the owner gets an email to confirm the change (202) and receives a new key after confirming.
• Sites can also be updated at warasoft.com/page/edit/: site name, email, edit key and only the fields that change. Filling in any extra page replaces all extra pages. Images can only be uploaded with the key.

Common errors

Code	Meaning	What to do
400	Invalid data (subdomain, slug, more than 5 pages, missing English version, invalid image)	Read the message, fix it and retry
403	The email and edit key do not match	Ask the user for the key from the email they received
404	The site does not exist	Check the subdomain
409	Subdomain taken	Use the suggestion or ask for another name
429	Too many requests	Wait a few minutes

If the owner does not recognize a site created with their email, they can take it down with the link in the publication email.

If the email with the key does not arrive, ask the user to check their spam folder. If it still does not arrive, they can write to contact@warasoft.com.