These 12 AI website builder prompt templates are ready to copy, one for each kind of site: copy one, replace the [brackets] with your real details and send it. A good prompt says what your business is, what the site must do, which pages it needs and which real facts to show (name, hours, address, prices).
- Every template follows the same six parts: goal, audience, pages, data and features, integrations and look.
- Replace each [bracket] with a real fact. A builder that isn't given your hours, prices or address has to invent them.
- On the free Community plan you get one build per 5-hour window, and a first build covers the core of a large request. Put the core flow first, mark the extras as optional and ask for the rest in the next build.
- After every template is a short list of what to check before you share the link.
Jump to your template: Portfolio · Restaurant · Booking site · Online store · Waitlist · Event RSVP · Client portal · Membership site · Quiz · Directory · Internal tool · Browser game
What a good website prompt contains
Cover these six parts and the first build has far less to guess. The 12 templates are this table applied to twelve common kinds of site.
| Part | What to state | Weak | Strong |
|---|---|---|---|
| Goal | What the site must achieve, in one sentence | "A site for my yoga studio" | "Get new students to book a first class online" |
| Audience | Every type of user: visitors, members, clients, staff, you as admin | "Everyone" | "Beginners aged 30 to 60 nearby; I'm the only admin" |
| Pages | The pages, or the sections of a one-page site | "The usual pages" | "Home, Timetable, Prices, About, Contact" |
| Data and features | What is saved, who can see or change it, and the rules: capacity, required fields, statuses | "Bookings" | "Book a class of max 10; name and email required; no booking after the class starts" |
| Integrations | Payments, email or another service, and what each one does | "Payments" | "Stripe checkout for a 10-class pass; email a receipt through my own email account" |
| Look | Two or three adjectives, colors, your logo, the site's language | "Modern and clean" | "Calm and airy: off-white, sage green, rounded buttons, attached logo; English" |
How long should the prompt be? Long enough to cover the six parts: a few short paragraphs is usually enough. Move long lists into attached files. As a ceiling, a message can hold up to 5,000 characters, in the chat and through the WisyLink API or CLI.
Can I write the prompt in another language? Yes. Wisy, the chat assistant, answers in the language of your latest message. The site's own language is separate: say it in the prompt, for example "the site is in Spanish".
12 prompt templates to copy and paste
Replace everything in [brackets], delete the optional lines you do not need, attach your files (logo, price list, photos) and send. Each template is a ready-to-send first message; delete the optional lines if you want a lean first build.
1. Portfolio
For designers, photographers, developers and writers: anyone who needs to show past work to people who might hire them.
Build a portfolio website for [your name], a [profession] based in [city], for [who hires you: studios, agencies, private clients].
Pages: Home (a short intro and my [3 to 6] featured projects), Projects (a grid I can filter by [category]), one page per project (title, year, my role, [2 to 4] sentences on the brief and the result, images from the attached files), About (use the attached [about.txt] text exactly as written) and Contact.
Contact form with name, email and message, all required. Save every message and show a thank-you note. Admin page, only for me: add and edit projects, choose which ones appear on Home and in what order, read messages.
Show my real email [email] and my links [profile links] in the footer. Do not invent clients, awards or testimonials.
Look: [two or three adjectives], [colors], my attached logo, large photos and little text. Language: [language].
What to check in the result
- Every project page shows the right images and only the facts you gave (year, role, text). Nothing about clients or awards you never mentioned.
- The projects on Home are the ones you chose, and you can change their order from the admin page.
- Send a test message through the contact form: it appears in the admin page, and the form refuses an empty email.
- Open the site on a phone: photos fit the screen and the text reads without zooming.
Full guide: build a portfolio website with AI.
2. Restaurant or cafe
For a place where most visitors want three things: the menu, the hours and how to find you.
Build a website for [restaurant name], a [type of cuisine] restaurant at [full address], [city].
Pages: Home (photo, one sentence about the place, today's opening hours, the address with a map link, a button to [call or message on WhatsApp]), Menu (use the attached [menu.pdf]: sections, dish names, descriptions and prices exactly as in the file; mark [vegetarian, vegan, allergens] only where the file does), Hours and Location (opening hours: [Mon to Fri 12:00 to 23:00, Sat and Sun 11:00 to 00:00]; closed on [days or holidays]) and Contact ([phone], [email], [Instagram]).
[Optional: a booking request form with name, phone, date, time and number of people. Save the requests and let me mark each one as confirmed in an admin page, only for me.]
Admin page, only for me: edit dishes, prices and opening hours. Do not invent dishes, prices, awards or reviews.
Look: [warm, relaxed], [colors], my attached logo and photos. Language: [language].
What to check in the result
- Hours, address and phone number match what you wrote, character for character. Compare each one with your own source.
- Dishes and prices match the menu file. Check a few sections by hand, including the most expensive items. Allergen marks appear only where your file has them.
- The call or message button works on a phone, and the map link opens the right place.
- If you asked for booking requests: send one and confirm it reaches the admin page.
Full guide: make a restaurant website with AI.
3. Booking site
For salons, studios, clinics, tutors, courts: anything where a customer picks a time and that time must not be booked twice.
Build a booking website for [business name], a [type of business] in [city].
Services: [service, duration, price], [service, duration, price]. Opening hours: [days and hours] in [time zone]; closed on [dates].
Visitors pick a service, see the free times for the next [14] days and book with name, email and phone. Each time slot holds [1] booking; once it is taken, nobody else can book it. Block bookings in the past or less than [2] hours ahead. After booking, show a confirmation page with the date, time and our address [address]. [Optional: email the customer and me through my own email account.]
Admin page, only for me: add or remove available times, see bookings by day, cancel a booking.
Pages: Home, Services, Book, Contact. Look: [style]. Language: [language].
What to check in the result
- Book a slot yourself, then try to book the same slot from another browser. The second attempt must be refused.
- The free times match your opening hours and time zone. Look at a day when you are closed.
- Cancel your test booking in the admin page and confirm the time becomes free again.
- Confirmation emails only arrive after you add the SMTP details of your email account (host, port, username, password) under Integrations, so test them after that step.
Full guide: build a booking website with AI.
4. Small online store
For a shop with a catalog you already keep in a spreadsheet and customers who pay by card.
Lean first build: keep the products, the cart and the payment, and ask for the admin page in the next build. A few dozen products fit best on the free plan; load the rest later.
Build a small online store for [shop name], selling [what] to customers in [country or region].
The products are in the attached [products.csv] (columns: name, category, price, stock, description, photo file name). Use the attached photos and load every row of the file during the build. Each product has its own page. The shop page filters by category and price.
Cart and checkout with Stripe in [currency]. Delivery: [shipping rates, free above an amount, or local pickup]. Save each order first and mark it paid only when Stripe confirms the payment. Reduce stock when an order is paid and show "sold out" at zero.
Pages: Home, Shop, Product, Cart, Delivery and returns ([your policy, in your own words]), Contact ([email]).
Admin page, only for me: edit products and stock, see orders, mark them as shipped. Look: [style], my attached logo. Language: [language].
What to check in the result
- The number of products, names, prices and stock match your file. Spot-check a few rows, including the last one.
- After you add your Stripe secret key and webhook signing secret under Integrations (Wisy lists the steps), make a test payment in Stripe's test mode. The order is saved and marked paid, and the stock goes down by one.
- Start a checkout and abandon it: the order must not show as paid.
- The delivery and returns page says what you wrote, not generic text.
Full guide: build an online store with AI.
5. Waitlist landing page
For a product that is not ready yet and needs a list of interested people.
Build a one-page waitlist landing page for [product name]: [one sentence on what it does], for [who it is for].
Sections: headline and subheadline, three benefits, how it works in three steps, a short FAQ ([Q1 and A1], [Q2 and A2], [Q3 and A3]) and a waitlist form with email required and [optional: role or company size]. Add an unticked checkbox to agree to [be emailed about the launch], with a link to a privacy page.
Save every signup, reject duplicate emails and show a confirmation message on the page. Admin page, only for me: signups with their date, a total counter. [Optional: a CSV download.]
Launch date: [date, or "to be announced"]. Do not invent customer numbers, logos or testimonials.
Look: [two or three adjectives], [colors], my attached logo. Language: [language].
What to check in the result
- Sign up twice with the same email: the second attempt is refused with a clear message.
- The headline and benefits say only what the product does today. Rewrite anything that promises more.
- The consent checkbox starts unticked and the privacy link opens a page that says who collects the data, why and how to ask for deletion; replace it with your own policy text.
- Signups appear in the admin page. If you asked for the CSV download, open it in a spreadsheet: the columns must be the right ones.
Full guide: build a waitlist landing page with AI.
6. Event RSVP page
For weddings, meetups, workshops and parties where you need to know who is coming and stop at a headcount.
Build an RSVP page for [event name] on [date], [start to end time] in [time zone], at [venue and address].
Show the event details and a form: name, email, whether they are attending (yes or no), number of guests (up to [2], with a name for each), [meal choice: option, option, option] and dietary needs. Capacity: [60] people. When it is full, the form says so and offers a waitlist. RSVP deadline: [date]; after it the form closes. Show a confirmation page after each reply.
Admin page, only for me: the guest list with all answers, counts per meal, remaining capacity and a field to change the capacity. [Optional: a CSV download.]
[Optional, private event: only people with the invite code from the attached [guests.csv] can reply, and the page stays out of search engines.]
Look: [style], [colors]. Language: [language].
What to check in the result
- Set the capacity to 2 for a test, then send three replies: the third must get the "full" message or the waitlist.
- The counts in the admin page add up to your test answers, including meals and party sizes.
- Move the deadline to yesterday in a test: the form must be closed.
- Date, time, time zone and address are the ones you wrote.
Full guide: create an event RSVP page with AI.
7. Client portal
For agencies, accountants, consultants and studios that share status and files with each client privately.
Lean first build: keep the sign-in, each client's projects and their files; comments and emails can follow in the next build.
Build a client portal for [agency or firm name].
I create the client accounts in an admin page; clients cannot sign themselves up. Each client signs in and sees only their own projects: status ([Planning, In progress, In review, Done]), next steps and the files I upload for them, kept private. Clients can upload files to me, up to [25] MB each, and comment on a project.
Admin page, only for me: create clients and projects, change status, upload files, read comments and the files clients send. [Optional: email a client when their project status changes, through my own email account.]
Public pages: only a login page with [firm name] and [contact email].
Look: [professional, minimal], [brand colors], my attached logo. Language: [language].
What to check in the result
- Create two test clients with one project each. Sign in as one: you must not see the other's project, even by trying the other project's address.
- A file uploaded for client A cannot be downloaded when signed out or signed in as client B.
- Upload a file above the size limit: you get a clear error, not a blank page.
- A client cannot open the admin page.
- A client who forgot a password: you reset it in the admin page. Automatic reset emails only work after you add your email account under Integrations.
Full guide: build a client portal without code.
8. Membership site
For courses, communities and paid content where some pages are only for members.
Lean first build: keep the protected lessons, the payment and the access; downloads and manual access can follow in the next build.
Build a membership site for [name], teaching [topic] to [audience].
Tiers: Free (account only, the first [3] lessons) and [Member] (a one-time payment of [$49] through Stripe: all lessons and the downloads). Member access starts only when Stripe confirms the payment.
Pages: Home (what you get, the price, one free sample lesson), Pricing, Lessons (grouped by [module]), Lesson (text, downloads [and an embedded video: video link]), Account (your access level) and Sign in. People without the right tier see a short preview and a pay button. Locked content must not be readable without access.
Admin page, only for me: add and edit lessons, upload the [PDF worksheets] for each lesson, see who has access and grant access to one person.
Look: [style], [colors], my attached logo. Language: [language].
What to check in the result
- Open a locked lesson signed out, and again on the Free tier: you get the preview and the pay button, not the full lesson. Try a download too: it must not open without access.
- After you add your Stripe secret key and webhook signing secret under Integrations (Wisy lists the steps), make a test payment in Stripe's test mode: access starts only after the payment is confirmed.
- Start another payment and abandon it: it must not give access.
- Prices and tier names are the ones you wrote.
- In the admin page, grant access to a test account and confirm it sees the full lessons.
- Someone who forgot a password: you reset it in the admin page. Automatic reset emails only work after you add your email account under Integrations.
Full guide: build a membership site with AI.
9. Quiz that collects leads
For a short quiz that gives each person a result and asks for an email to send it.
Build a quiz called "[quiz title]" for [audience] that tells them [what result they get, for example which of three types they are].
[8] questions, one per screen, each with [4] answer options and a progress bar. Scoring: [each answer adds a point to outcome A, B or C; the highest total wins; on a tie, show the first]. Outcomes: [A: name, two-sentence description and a next step with a link], [B: same], [C: same].
After the last question, ask for first name and email to show the result. Add an unticked checkbox to agree to [receive the results and tips by email], with a link to a privacy page.
Save every submission with the answers, outcome, email and date. Admin page, only for me: completions, counts per outcome, a list of emails with their outcome. [Optional: a CSV download.]
Look: [style], [colors]. Language: [language].
What to check in the result
- Answer all A, then all B, then all C: each run must give the outcome you defined. Test a tie too.
- The result texts are the ones you wrote, not generic ones.
- The consent checkbox starts unticked and the privacy link opens a page that says who collects the data, why and how to ask for deletion; replace it with your own policy text.
- The counts in the admin page match your test runs.
Full guide: build a quiz lead magnet with AI.
10. Directory
For a list of places, providers or resources that people filter and that others can suggest additions to.
Build a directory of [places, providers or resources] in [city or niche] for [audience].
Each listing has: name, category ([list]), [area], address, [phone], website, short description, [price range], opening hours and up to [3] photos. Pages: Home (browse by category and area), one page per category, one page per listing, a "Suggest a listing" form (listing details, your email, up to 3 photos) and About.
Filters by category, area and price. New suggestions stay hidden until I approve them in an admin page, only for me, where I can also add, edit and hide listings and load the attached [listings.csv] with the first [N] listings.
Do not invent listings, ratings or reviews. Look: [style], [colors]. Language: [language].
What to check in the result
- Each listing page shows the data from your file. Spot-check a few, including names with accents or an ampersand.
- Filters combine (category and area together) and the results are the ones you expect.
- Submit a suggestion: it must not appear publicly until you approve it.
- Submit a suggestion with a JPG photo from a phone: it uploads, and a HEIC photo gets a clear error.
- Open a listing on a phone: photos and details fit the screen.
Full guide: build a directory website with AI.
11. Internal tool
For a team that tracks requests, stock or equipment in a spreadsheet and needs roles and statuses.
Lean first build: keep the sign-in, the roles and the record list with its statuses; the summary can follow in the next build.
Build an internal [request, inventory or equipment] tracker for our [team size]-person team at [company].
Staff sign in with accounts I create; there is no public sign-up. Roles: [staff] add records and see [only their own] records; [managers] see all records, change the status and assign a person; I am the admin and manage accounts.
Record fields: [field, type, required or optional], [field, type, required or optional]. Statuses: [New, In progress, Done]. Record who last changed the status, and when.
Screens: a list with filters by status, person and date; a page for one record; a summary with the count per status. Load the starting data from the attached [file.csv] during the build.
Look: clean and compact, desktop-first. Language: [language].
What to check in the result
- Sign in as staff and as a manager: each sees only what you decided.
- The record count and a few rows match your file, and dates and numbers did not turn into plain text.
- Change a status: the record shows who made the latest change and when.
- Opening the list while signed out leads to the sign-in page.
- Someone who forgot a password: you reset it in the admin page. Automatic reset emails only work after you add your email account under Integrations.
Full guide: build internal tools with AI.
12. Browser game
For a quiz, typing, memory or reaction game that runs in the browser on a phone or computer.
Lean first build: start with one player, one round and the leaderboard; multiplayer can follow in the next build.
Build a [typing, trivia, memory or reaction] game for [audience] that runs in the browser on phone and computer.
How it plays: [rules in three to five sentences: what the player sees, what they do, how they score, when the round ends]. A round lasts [60] seconds.
Mode: [single player, with a leaderboard of the top 20 scores] or [multiplayer: the host creates a room with a 4-letter code, up to 8 players join with a nickname and everyone sees the scores live].
Save scores with nickname and date. Reject scores outside the possible range and limit how often one player can submit. Admin page, only for me: hide a nickname or score and reset the leaderboard.
Art and sound: shapes drawn in code [or my attached images and MP3 sounds]. Look: [style]. Language: [language].
What to check in the result
- Play one full round alone. The score is the one the rules say, which you can work out by hand.
- In multiplayer, join from two devices with the room code: both see the same state within a moment, and a player who leaves does not break the room.
- Finish a round without playing: the score must not be a high one.
- On a phone, the controls work with a thumb and the text reads without zooming.
Full guide: make a multiplayer browser game with AI.
Ready to try one? Start free on Community, paste a template and attach your files.
Give the builder your real facts
Wherever a prompt leaves a gap, the builder fills it with plausible text. That is how wrong opening hours, invented prices and made-up reviews end up on a live page. Have these facts ready before you write:
| Type of site | Facts to have ready |
|---|---|
| Portfolio | Project names, years, your role, the text for About, the email you want shown |
| Restaurant | Opening hours and closed days, full address, phone, the menu with prices, allergen information |
| Booking | Services with duration and price, opening hours and time zone, how far ahead people can book, the cancellation rule |
| Store | The product file, shipping costs and areas, your returns policy, the currency |
| Event | Date, start and end time with time zone, venue address, capacity, RSVP deadline, a contact |
| Membership or quiz | Tier names and prices, what each tier includes, the quiz outcomes and their texts, your privacy page |
Put short facts straight into the prompt and lists into an attached file (a CSV for products, a PDF for the menu, a text file for your About copy). Say what each file is for: "take prices from prices.csv, use team.jpg on About". Files stay with the link, so later changes can use them again. Afterwards, check the result against your file; for long lists, ask for an admin page so you can correct entries yourself.
Attach up to 10 files per message; supported types include JPG, PNG, WebP, PDF, CSV, TXT, MP3 and ZIP. An attached PDF or document works as reference but is not published on the site: to offer a download, upload it from the admin page. Use JPG, PNG or WebP photos: iPhone HEIC photos cannot be shown on the site. If you attach no photo, the builder may use a stock picture, so check every image.
Use your own material. An image of another company's site invites a copy of its design: describe what you like instead, such as "large photos, a lot of white space, one strong accent color". And never paste passwords or API keys into the chat: they go under Integrations after the build. Wisy tells you the admin login in the last message of the build; keep it private and check that the admin page asks for it.
Mistakes that waste a build
On the free plan every build counts, and a follow-up change is a build too. Once one has started, you cannot start another or message Wisy until the 5-hour window ends. These mistakes cost the most:
- Sending the idea in scattered pieces. Write the brief once, in one message, with the core flow first and the extras marked as optional.
- Leaving out who can see what. "Clients can sign in," without "and see only their own files," is the most common gap in portals and member sites.
- Asking for what a web app does not do. App Store apps, AI-generated photos or video, free-text search over a long list and jobs that must run at an exact minute are not available. Ask for a web app, your own photos, filters and background jobs that run every 30 to 60 minutes instead.
- Using style words with nothing behind them. "Modern" means little without colors, a mood and a logo.
- Asking for invented social proof. Made-up reviews, client logos or "thousands of happy customers" mislead visitors. Use real quotes with permission, or leave the section out.
- Forgetting the site's language. Writing in Spanish does not make the site Spanish. Say "the site is in Spanish".
- Asking for everything at once. Start with the core flow, such as booking or checkout, and add features once it works.
Follow-up prompts: ask for changes precisely
A good change request has four parts: where, what, the change and the rule behind it. Compare:
- "Make it pop" becomes "On the home page, make the Book a class button larger and dark green, and show it without scrolling on a phone."
- "Fix the form" becomes "On the Contact page the form accepts an empty email. Make email required and show the error under the field."
- "Bookings are broken" becomes "I booked the 18:00 class on Tuesday and it still shows 10 of 10 places free. Booking should reduce the count by one."
For a bug, describe what you did, what happened and what should have happened. For several fixes, send one numbered list in a single message.
A full change of direction is also a valid follow-up: "Redesign the whole site in a darker, more restrained style; keep all pages and content." Saying what must stay is the important part. If you want to understand why this works, our essays on intent fidelity and context engineering go deeper.
Publishing: link life, your own domain and plans
- On the free Community plan, a link stays live for 30 days, and you get an email before it ends. If you do not keep it, it is marked for deletion for about a week and then deleted with its files and data.
- Starter ($7 a month) keeps your links live while you are subscribed and removes the "Made with WisyLink" badge.
- You can connect a domain you already own on every plan, Community included.
- A free link is still deleted after its 30 days and the week marked for deletion, also on your own domain.
- Free-plan pages on a wisylink.com address may be kept out of search results. On your own domain or a paid plan they can be indexed.
Details are on the plans and pricing page. For the full path from first message to your own domain, read how to build a website with AI. If you would rather start from your phone, see how to make a website on your phone. More walkthroughs by topic are in all guides.
Send your first message
Pick the template closest to your project, fill in the brackets, attach your files and send it. Before you do, check that the prompt states the goal, every type of user, the pages, what data is saved and who sees it, the rules, the integrations, the look, the language and your real facts.
Describe your site in one message and get a live link: start free on Community, no card required. If you need the link to stay live and the badge gone, Starter is $7 a month.
F.A.Q.