You probably already ask Claude or ChatGPT to reword an email or tidy a price list. The job gets done. Your website, meanwhile, sits untouched, because it feels like a separate job that needs its own free evening.
So what else could that same assistant do for you? Quite a lot, as long as you ask clearly.
This guide walks through five kinds of request: page edits, new sections, bookings and forms, blog posts, and social posts. Then you'll see how to check what comes back before anything goes live.
Page edits and new sections: small, clear requests
Start with what you already have. Editing an existing page is the easiest first move, because the structure is there and you only need to describe the change.
Say you run a B&B. You could write: "On the Rooms page, change the double room price to £95 a night and add a line saying breakfast is included." One page. One price. One new line. Nothing left to guess.
Adding something new works the same way. A mechanic might ask: "Add a section to the Services page called MOT and servicing. List three services in plain words with a starting price for each, using £65, £110 and £180, and finish with a button to book." It's longer, but every part is spelled out.
Both requests follow the same pattern. Before you hit send, check that you've covered four things:
- Which page the change belongs on
- What to change or add
- The exact wording or numbers you want
- What should stay exactly as it is
That last one is easy to skip. And it's the one that stops your carefully written homepage from being rewritten while you're fixing a price.
One more tip. Keep it to one change per request. When something goes wrong, you'll see straight away which instruction caused it. Plus, if you can undo edits (a version history or an undo button), experimenting stops feeling risky. You can try a bolder idea knowing you can step back.
Bookings and forms: describe the customer, not the software
Once your pages say what you want them to say, the next job is letting customers act on them. Your customers don't think in software terms. They think in situations. So describe the situation, and let the assistant work out the settings.
Take a physio who wants online bookings. Don't ask for "a scheduling plugin with buffers." Try this instead:
"Set up bookings for 45-minute appointments, Monday to Friday, with a 15-minute gap between each. Ask for the person's name, phone number and whether this is their first visit."
That one sentence covers appointment length, working days, recovery time and the exact questions. Nothing left to guess.
Forms work the same way. A florist might write:
"Add an enquiry form for wedding flowers asking for the date, the venue, a rough budget in pounds and any colours they like."
Notice what both examples avoid. Neither asks for an address, a company name or a long free-text box "just in case." Ask only for what you'll actually use. Every extra field gives a busy customer one more reason to close the tab. (And one more thing for you to store and protect.)
One caution. Where you collect personal data, consent wording and privacy notices matter, and the rules differ by country. Check the current requirements where you operate rather than trusting the assistant's draft.
Blog posts and social posts: give it your facts, keep your voice
With the pages and bookings sorted, you can turn to the part that usually gets pushed to "later": writing regularly. The goal here is simple. You want a first draft that already sounds like you, so you're editing, not rewriting from scratch.
Start with a specific request. Say you run a flower shop and want a blog post. Try this: "Write a short post on caring for supermarket-bought tulips at home. Friendly, plain, no hype. Include a short tip list and end with an invitation to visit the shop." Notice what's in there. A topic, a tone, a format and a closing line. That's enough to get something usable.
Social posts work the same way. A B&B owner could write: "Plan three posts for next week from these notes: new breakfast menu, the garden room is free midweek, a walking route from the front door. Offer a caption for each and suggest a day to post." You supply the facts. The AI handles the shaping.
Now the tip that makes the biggest difference. Paste in your own material before you ask:
- Rough notes about the topic, even if they're messy
- A past product or room description you liked
- A sentence about your tone, such as "warm, a bit dry, never pushy"
The more of your own voice you hand over, the closer the draft starts.
One rule stays fixed. Nothing goes live until you've read it and approved it. Check the facts, the prices, the dates and the tone. It's your name on it.
How to review what comes back and keep the final say
Before you publish anything, run this checklist:
- Prices, opening hours, names and addresses
- Phone numbers and links (click every one)
- Does it sound like you?
- Is every claim something you can stand behind?
Next, ask the assistant to show its work. Try "List every change you made, in plain words." Then hold that list up against your original request. If you asked for a tighter intro and it also rewrote your service descriptions, you'll spot it right away.
Follow up the way you'd talk to a colleague. "Shorter, and take out the second paragraph." Or "Keep the price, change the wording." You don't need special prompts. Plain instructions work.
And you can always say no. Read it, approve it, or roll it back. Keep your previous version handy so an unwanted change is an easy fix.
One firm exception to "good enough." Anything touching legal, tax or accessibility rules needs a check against the current requirements in your country. Don't take the assistant's word for it. (Rules differ by place, and they change.)
Start with one request this week
You've seen the pattern. Specific requests beat vague ones. Small steps beat big overhauls. And nothing goes live until you've read it.
So pick one small website job this week. A price change, a booking form, a draft post. Then write it as a request: name the page, describe the change, and give the exact wording. For example: "On the Services page, change the logo design price from £450 to £520 and keep the rest as is."
Send it, read what comes back, and approve it only when it's right. The assistant handles the drafting, and you keep the decisions.