The difference between a website you like and one you delete usually comes down to how you asked. Not prompt-engineering tricks — just being specific about things you already know and the AI does not.
This is what to say, in what order, and what to do when it goes sideways.
Before anything: give it the ability to publish
An AI cannot put a site online unless you have given it a way in. With BlueDeploy that is one line, pasted once:
Deploy my website with BlueDeploy.
Read https://bldeploy.com/llms.txt first — it explains how to publish, how to
check what my plan allows before you build, and what to do if I do not have an
account yet.
Your code goes on the end of that line — you will find it on your dashboard the moment you sign up. Paste the whole thing into ChatGPT, Claude, Cursor or Google Antigravity and it will read the instructions itself.
You only do this once per conversation.
Then describe the site like you would to a person
The single biggest improvement you can make is to stop writing prompts and start describing the thing. Compare:
Make me a bakery website.
with:
Make me a one-page site for Sunrise Bakery. We're a small place in Manchester. I want our opening hours (7am–3pm Tuesday to Sunday, closed Mondays), a short paragraph about us, our phone number, and a photo section I can put pictures into later. Warm and simple, not corporate.
The second gets you something usable first time. Everything in it is information only you have.
Things worth including:
- What it is for. A menu, a portfolio, a landing page.
- The actual content. Hours, prices, names, addresses. Otherwise you get placeholder text you then have to replace.
- A feeling. "Warm and simple", "clean and modern", "playful". Vague is fine — it is still more than nothing.
- What you do not want. "No stock photos of people in offices" saves a round trip.
Let it choose the address, then check it
Your site gets a web address, and it is permanent — there is no rename. So a good assistant will suggest one and ask you before creating anything:
I'll publish this at
sunrise-bakery.bldeploy.run— does that work?
Say yes, or give it a different one. Worth thinking about for a second, because changing it later means a new site and deleting the old one. Short and obvious beats clever.
If the name is taken, it will suggest another. Names are global, so common words go early.
Then just ask for changes
Once it is live, iterate in plain language:
- "Make the hours bigger and move them to the top."
- "The blue is too dark, warm it up."
- "Add a section for catering enquiries with an email link."
Each change republishes to the same address in a few seconds. You do not need to say "redeploy" or "push it live" — that is part of the change.
When something goes wrong
Most failures are handled without you. The errors are written to be read by the assistant, and they say what to change rather than just that something broke — so it usually fixes it and tries again without mentioning it.
The ones that do reach you:
"You need to verify your account." You asked for something that runs code on a server — a contact form that saves submissions, a login, anything with a database. Static pages work immediately; running code needs you to confirm you are a real person first. It is free.
"That name is taken." Someone else has it. Pick another.
"You've used your monthly allowance." The free plan covers 100,000 visits a month. Publishing new code will not bring the site back — it resets at the start of the month, or you can upgrade.
Your AI says it cannot connect. Usually the code. If you have already used it in this conversation, your code is no longer visible on the dashboard — that is deliberate, so nobody can read it off your screen later. Do not go hunting for it. Get a new one, which replaces the old, and paste that instead.
Things that will not work, and why
Worth knowing so you do not spend an afternoon on them:
- Uploading a video. Put it on YouTube or Vimeo and embed it. Video will exhaust any free storage tier immediately.
- Sending email directly. Email needs a protocol this platform deliberately does not allow, for spam reasons. An email API works.
- Anything needing a long-running process. Sites here respond to requests; they do not sit and run in the background.
If you ask for one of these, a good assistant should tell you before it starts building, not after.
The shortest version
- Sign up, paste the line into your AI.
- Describe the site like you would to a person, with the real details.
- Confirm the address.
- Ask for changes in plain language.
The AI does the parts that used to require knowing what a DNS record is.