Prompting · 12 min read
Prompting for Websites: How to Write Prompts That Ship Great Sites
The complete prompt-engineering guide for AI website builders. Anatomy of a great prompt, seven patterns that work, common mistakes, and chat-edit iteration. Specific examples by site type.
The single biggest variable in AI website-builder output quality isn't the AI model. It's the prompt. The same builder, given the same model, will produce a forgettable site from a vague prompt and a memorable site from a specific one. The good news: prompts are easy to learn. The skill compounds in minutes, not weeks.
This guide covers the anatomy of a strong website prompt, seven proven prompt patterns (organized by site type), the mistakes that produce bad output, and how to iterate via chat editing once the first generation is live.
The anatomy of a great website prompt
A strong website prompt has five components. Not all five are required for every prompt, but the good ones usually hit four or five:
- Who the site is for. The audience — not just demographics, but the specific person reading the site. 'For founders at pre-seed AI startups raising their first round' beats 'for businesses.'
- What the site is selling or showcasing. The thing the visitor is here to evaluate. Be specific — 'a $99/month observability SaaS for Node.js teams' beats 'software.'
- The action you want the visitor to take. Sign up, book a demo, apply, buy, subscribe, RSVP. The site optimizes around this.
- The brand reference or design direction. 'Like Linear's homepage' or 'agency-portfolio cinematic' or 'editorial magazine restrained.' Specific references beat generic adjectives.
- Tone or voice. Founder-direct, dry technical, warm and conversational, playful indie. Tone shapes copy more than any other input.
Seven prompt patterns that work
Pattern 1: SaaS marketing site
Best structure for a SaaS product marketing site:
A marketing site for [product name], a [one-line product description] for [specific audience]. The site should sell a $[X]/month subscription with a free trial. Tone: [Linear-clean / Stripe-flow / dev-tools direct]. Sections: hero with strong value prop, social proof, three feature blocks tied to outcomes (not features), pricing with three tiers, FAQ, contact. CTA: 'Start free trial.'
Pattern 2: Landing page for paid ads
Optimized for conversion from a specific traffic source:
A high-converting landing page for [product/service] targeting [traffic source — Google Ads, Meta Ads, podcast listener, X audience]. The visitor arrives with [intent — researching a problem / comparing alternatives / ready to buy]. One conversion action: [sign up / book demo / buy]. Above-fold value prop + social proof, three benefit blocks, objection-handling FAQ, single CTA repeated. No navigation distractions. Tone: [confident-direct].
Pattern 3: Agency / consultancy site
An agency website for [agency name], a [type] consultancy serving [client type]. Style: agency-portfolio-dark, cinematic, scroll-driven. Sections: hero with positioning statement, services (3-5), selected work / case studies, process, team (or 'team of N'), contact. CTA: 'Get in touch' or 'Book a discovery call.' Tone: confident, founder-direct.
Pattern 4: Portfolio (designer / developer / creator)
A portfolio site for [name], a [role — designer/developer/photographer/creator] specializing in [niche]. Goal: hiring managers and prospective clients should understand what I do in 5 seconds and want to see more. Sections: hero with one-line positioning, selected work (3-6 case studies), about (story + tools), services or contact. Style: [editorial-magazine / linear-clean / brutalist-dev / cinematic-showcase]. Tone: [matched to the work].
Pattern 5: Small business / local service
A website for [business name], a [type — restaurant/salon/gym/agency/etc.] in [city]. We want [primary goal — bookings / reservations / phone calls / online orders]. Sections: hero, services (with prices if appropriate), hours and location, [reservation/booking system mention], gallery, testimonials, contact. Tone: [warm/professional/playful — match the brand]. Schema: LocalBusiness with full hours and address.
Pattern 6: Personal brand / creator site
A personal-brand site for [name], a [role — writer/coach/speaker/founder]. The site collects email subscribers and routes visitors to: [products/services]. Sections: hero with story-led headline, what I do, books/articles/talks, testimonials, signup form (newsletter or course waitlist). Style: editorial-magazine or anthropic-warm. Tone: first-person, slow-paced, opinionated.
Pattern 7: Event / launch / coming-soon
A [coming-soon / event / launch] page for [product/event]. Single goal: capture email signups for [launch date / event registration]. One-pager with minimal scroll: hero with countdown + value prop, what to expect (3 bullets), email capture, social proof (founders/backers/speakers if any), social links. Style: minimal, high-impact, brand-led.
Common prompting mistakes
Mistake 1: Generic prompts
The most common mistake. 'A website for a startup' generates a generic site. 'A marketing site for an AI observability SaaS targeting senior backend engineers at Series A startups, charging $99/month, replacing Datadog' generates a specific site you can actually ship. Specificity is the multiplier.
Mistake 2: Listing features instead of outcomes
Bad: 'list our features: dashboard, alerts, integrations, API.' Good: 'show how customers cut MTTR from 4 hours to 12 minutes, ship features faster, sleep through their on-call rotation.' Outcomes convert; features describe.
Mistake 3: No conversion action
If you don't tell the AI what action you want the visitor to take, it picks one — usually a generic 'Contact Us' or 'Get Started.' Be explicit: 'Start free trial' / 'Book a 30-minute demo' / 'Apply for a slot' / 'RSVP for the event.' The action shapes every CTA and conversion section.
Mistake 4: Mixing audiences
A site for 'founders, marketers, and developers' tries to please three different readers and pleases none. Pick the primary audience. Other audiences land on persona-specific pages or industry-specific pages — not a one-size-fits-all home page.
Mistake 5: Asking for everything at once
First-generation prompts that try to specify every section, color, layout, and detail tend to over-constrain the AI and produce muddled output. Start with the big picture (who/what/action/style), let the AI generate, then refine specific sections via chat editing.
Iterating: chat-edit patterns
The first prompt rarely gives you the final site. The good builders let you chat-edit the rendered output — describe a change, see it apply. Here are the iteration patterns that work:
- Point and adjust. 'Make the hero subtitle shorter and more specific — mention the $99/month price.' Point at a section, describe the change.
- Tone shift. 'The pricing section reads too corporate. Make it more direct, more founder-flavored.' Tone shifts are some of the cheapest, highest-impact edits.
- Add or remove sections. 'Add a testimonials section between features and pricing — three testimonials, each with a name and company.' Sections rearrange easily on modern builders.
- Brand reference shift. 'The home page feels too Linear. Make it more agency-portfolio — darker, more cinematic, scroll-driven.' Whole-site tone shifts.
- Specific copy edits. 'Change the H1 from "Faster observability" to "Cut MTTR by 90%."' The AI handles the surrounding copy adjustments.
- Bug fixes. 'The contact form on the contact page isn't showing the dropdown options.' AI builders auto-fix obvious bugs.
Real prompt examples (what to copy)
Example A: SaaS marketing site
A marketing site for Latency.dev, an AI observability SaaS for Node.js teams. We replace Datadog at 1/5 the cost. Target audience: backend engineers + tech leads at Series A startups. Tone: Linear-clean, founder-direct, no marketing fluff. Sections: hero with 'Cut MTTR by 90%' headline, social proof (3 customer logos), three feature blocks tied to outcomes (faster debugging, cheaper bill, fewer 2am pages), pricing ($99/$499/Enterprise), FAQ, contact. CTA: 'Start free trial' (no credit card).
Example B: Restaurant
A website for Sapore, a wood-fired pizza restaurant in Brooklyn (Williamsburg). Dinner-only, reservations via Resy, no online ordering. Sections: hero with food photography, menu (with prices), hours + Williamsburg location with map embed, reservations CTA linking to Resy, press quotes (Eater, NY Mag), Instagram embed. Tone: warm, food-forward, slightly cinematic. LocalBusiness schema with full address and hours.
Example C: Personal brand
A personal-brand site for Maya Chen, a writer covering the economics of independent media. The site collects email subscribers to her newsletter (currently 12K subscribers) and links to her book, speaking, and consulting. Style: editorial-magazine, serif headlines, restrained, slow-paced. Sections: hero with one-line positioning and email capture, the newsletter (link out), the book (with buy links), selected articles (3-5), speaking + consulting (with rates or contact), about (story + photo). Tone: first-person, specific, opinionated.
Frequently asked questions
How long should a website prompt be?
Aim for 80–200 words. Long enough to cover audience, product, action, style, and tone; short enough that you're not over-constraining the AI. The real examples in this guide land in that range.
Can I paste a brief or pitch deck into the prompt?
Yes — most modern AI builders accept multi-paragraph prompts. Pasting a one-page brand brief or the relevant slides from a pitch deck works well. Just make sure the audience and conversion action are explicit.
Should I tell the AI the exact colors I want?
Usually no. Describe the brand feeling ('Linear-clean,' 'warm cream and deep navy,' 'high-contrast brutalist') instead of specific hex codes. The AI picks better color palettes from references than from constrained hex pairs.
Can the AI write good copy if I don't write my own?
It can write functional copy, but the strongest sites have copy that came from a real human voice. A common pattern: let the AI generate the first draft, then chat-edit key sections (hero, CTAs, value props) in your own voice.
Do I need to know what design system I want?
Helpful but not required. If you don't specify, the AI picks based on your prompt — a SaaS brief gets Linear or Stripe; an agency brief gets agency-portfolio; a creative brief gets editorial-magazine. You can iterate the design system via chat-edit if the first pick isn't right.
Can I prompt for a multilingual site?
Some builders support this in the initial prompt; most are stronger if you generate in one language and then translate via chat-edit per page. The translation quality depends on the AI's training in your target language.
Why does my AI-generated site feel generic?
Almost always a prompt issue. Generic prompts produce generic sites. Re-read the seven patterns and the real examples — most people make one or more of: vague audience, no conversion action, mixed audiences, listing features instead of outcomes.
How many iterations does a typical site take?
On modern builders, 5–15 chat-edits over an hour gets most marketing sites from first-generation to publish-ready. For complex sites or strong brand voice, 20–30 edits over a longer iteration period is normal.
Can I save and reuse prompts across projects?
Some builders save prompt history per project; few save reusable prompt templates today. Pragmatic workaround: keep a markdown file with your prompt templates for the site types you ship often, paste in adjustments per project.
Does prompt length affect token costs?
Yes — longer prompts cost more tokens. But the cost differential between an 80-word prompt and a 200-word prompt is negligible relative to the output-quality difference. Optimize for output quality.