Build a One-Page Website by Talking to AI

Say what it's for, not how to build it

Start with purpose, not with technology or jargon you've half-picked-up from somewhere. "A one-page site for my freelance photography — a hero section with my best photo, three packages with clear prices, a small gallery, and a contact button that opens WhatsApp directly." That's a genuinely complete brief AI can build a real first version from, without you needing to know a single technical term.

You're playing the role of the client describing exactly what you want; AI is playing the role of the developer translating that into an actual working page. The clearer your description of the goal and of who's actually going to visit the page, the noticeably better the first version comes out, which saves you several rounds of correction later.

It helps enormously to describe the one action you most want a visitor to take before you describe anything else — book a call, message you on WhatsApp, buy something specific. Everything else on the page exists to support that one action, and saying it upfront keeps both you and the AI focused on what actually matters for the page to succeed.

Refine entirely by conversation

The very first draft is almost never the final one, and that's completely fine — you fix it simply by talking, the same way you'd give feedback to a designer sitting across the table from you. "Make the header smaller, move the prices further up the page, use warmer colours throughout, add one line about your typical turnaround time." Each message you send nudges the page a little closer to what you actually pictured in your head.

This is the real skill involved here, and importantly, it isn't a technical one at all: knowing what "better" genuinely means for the specific person visiting your page, and being able to ask for that improvement clearly and specifically rather than vaguely. If you're capable of giving someone honest, specific feedback on a piece of work, you are already fully capable of building a website this way — the missing piece was never coding ability.

Get it properly live, and keep it honest

A site that never actually gets published helps precisely nobody, no matter how polished it looks sitting on your own screen. Aim to genuinely ship it, following roughly this order:

• Describe, generate, and refine in that order, repeatedly, until the page does its one specific job well rather than trying to do five things adequately.
• Publish it to a free hosting option so it has a real, permanent, shareable link you can actually put on a business card or in a bio.
• Check every single claim, price, and contact detail yourself before sharing the link — never ship an AI-invented fact about your own business, however plausible it happened to sound in the draft.

A single page is a door

A single good page genuinely changes how you're seen by the people who matter to you professionally. A freelancer with a real, working link looks noticeably more established than one without; a job-seeker with a small portfolio site stands out clearly from a stack of identical CVs; a small business idea with even a basic launch page can start quietly collecting genuine interest overnight, while you're asleep.

You don't need to become a developer to get any of this. You need to be able to describe clearly what you want and honestly judge whether what came back actually matches it — both of which you're already fully capable of doing today, without a single new technical skill. The gap between "I have an idea" and "here's the actual link" is now genuinely about one focused evening wide, not the weeks or months it used to be.

What tends to trip people up first

The most common early mistake isn't a technical one at all — it's trying to cram everything you could possibly say about yourself or your business onto one page. Resist that instinct. A single page that does one job clearly and cleanly will always outperform a cluttered page trying to be a full website, especially for the specific goal of getting one visitor to take one action.

The second most common mistake is publishing the very first draft without reading it properly from a stranger's point of view. Show it to one person who's never heard you describe the idea before asking for the site, and watch where they hesitate or look confused — that's exactly where your next round of refinement should go, and it's a far more reliable signal than your own judgement, since you already know what every section is supposed to mean.

Choosing what actually goes on the one page

Beginners often assume a website needs several pages to feel legitimate — a separate About, a separate Services, a separate Contact. In practice, a single well-organised page that a visitor can scroll through in under a minute usually converts better than a multi-page site nobody bothers clicking through fully. Structure it as sections within the one page: a clear opening statement of what you do, proof that you're good at it, and one obvious way to get in touch, in that order.

If you genuinely have more to say later — a blog, a detailed case study, a proper shop — you can always add further pages once the one-page version is live and already working for you. Shipping something real and simple today beats holding out for a more complete site that never quite gets finished, which is the fate of most ambitious personal website projects that never see daylight at all, sitting half-built in someone's notes for years on end.