You can build a complete restaurant website in an afternoon by describing each section in plain English to an AI page builder — including a menu people can actually read and an ordering button that points wherever you want it. Below is the full playbook: the seven sections a restaurant needs, the exact prompts that build each one (copy and paste them), how to take direct orders instead of routing every ticket through a delivery app, what it costs compared to hiring out, and the questions restaurant owners ask most.
Why most restaurants have a website that costs them money
I want you to do something. Pull out your phone, search your own restaurant, and try to order a pickup order from yourself.
Here is what usually happens. Google shows your name. Under it are three delivery apps, all bidding on you. Your own site is down the page, and when you finally tap it, the menu is a PDF that opens sideways and renders at about six-point type. So the hungry person pinches, gives up, backs out, and taps the app instead — and that order, the one that was already yours, now costs you a commission that commonly runs fifteen to thirty percent of the ticket.
Think about what that actually is. You did the marketing. You built the reputation. Somebody searched for you by name. And you still paid a finder's fee on a customer you already had. That's not marketing — that's a tax.
Here's the thing. Nobody is saying to rip up the apps. They bring you people who have never heard of you, and that's worth paying for. What is insane is paying that same rate on the regulars — the Friday-night family, the guy who gets the same bowl every Tuesday. Those orders should land on your own page, at your own prices, with the customer's name and email in your own hands.
And the thing standing between you and that is almost never technology. It's that the website became a someday project. The agency quoted $4,000 and wanted the menu in a spreadsheet. The nephew built something in 2019 and moved away. Meanwhile you're running a kitchen. So the PDF stayed up, the apps kept their cut, and the afternoon site — the one that would take an afternoon to build — never got built.
Can AI really build a restaurant website?
Yes — and the skill it needs is the one you use every time you walk a new server through the specials: saying plainly what a thing is. Designer Talk is an AI page builder that lets you build WordPress pages by describing them in plain English — no drag-and-drop, no design skills. You describe a section the way you'd describe it out loud — “a menu section with our dinner items, prices, and little tags for vegetarian and gluten-free” — and it appears in a live preview. Too fussy? Say so. Want the ordering button bigger? Say that. Each section is its own conversation, so you push it around until it looks like your dining room.
What you end up with is a real WordPress site on your own domain, with your menu as actual text, your hours, and an order button pointed at whatever system you choose — not a listing inside somebody else's marketplace.
Get started with Designer Talk today and build along as you read — every prompt below is copy-paste, and the whole build is an afternoon between services.
“When somebody searches your restaurant by name and still orders through an app, you just paid rent on a customer you already owned.”— Vincent Jordan
What does a restaurant website actually need?
Not twelve pages. Seven sections, in this order, each one doing a job the apps currently do for you:
| # | Section | Why it matters for a restaurant |
|---|---|---|
| 1 | Header with an Order Online button | The single most-tapped thing on a restaurant site. Keep it fixed on every scroll, next to a tap-to-call number, so a hungry person never has to hunt. |
| 2 | Hero naming the food and the neighborhood | “Wood-fired pizza and handmade pasta in Lawrenceville” beats “A Dining Experience.” Somebody three blocks away needs to know in two seconds what you cook and that you're close. |
| 3 | The menu as real text — not a PDF | This is the section that decides everything. Real text with prices is readable on a phone, searchable by Google, and editable by you in thirty seconds. A PDF is none of those things. |
| 4 | Ordering: pickup, delivery, and who takes the cut | Put your direct-order link first and the apps underneath. Same food, and people will happily tap the first button. That ordering of buttons is worth real money every week. |
| 5 | Hours, location, parking & reservations | “Are you open right now and where do I park?” is the second-most common question a restaurant site gets. Answer it plainly, with today's hours and the holiday exceptions. |
| 6 | Private events & catering | The highest-margin inquiry you will ever get, and most restaurant sites bury it. One section with capacity, a sample package, and a form turns a rehearsal dinner into an email instead of a missed call. |
| 7 | Real photos of your food and your room | People are deciding whether this is a nice place. Actual plates from your pass and an honest shot of the dining room outperform any stock photo of a generic burger. |
That's the whole site. One page, seven sections, and the ordering button belongs to you.
The exact prompts to type (copy and paste these)
These are real prompts, in build order, for a fictional restaurant — Copperline Kitchen, run by Renata Solis, in Pittsburgh, Pennsylvania, a neighborhood spot doing wood-fired pizza and pasta with pickup and delivery. Swap in your restaurant, your town, your dishes, and your prices, and type them into Designer Talk one at a time. Your site won't look like anyone else's — the AI designs each section fresh — but it'll match what you asked for.
Two things before you type the first one. First, open Brand Settings and set your colors and font once — every section after that comes out already matching, which is why none of these prompts mention colors. Second, photos never go in section prompts: the layout builds with placeholders. You can generate something to hold the hero while you wait on a photographer, but the plates on your menu need to be your actual plates — I'll show you both flows below.
create a header for Copperline Kitchen — links to Menu, Order, Hours, and Private Events, our phone number, and an Order Online button on the right that stays visible when you scroll.
create a hero section for Copperline Kitchen in Pittsburgh — headline Wood-Fired Pizza and Handmade Pasta in Lawrenceville, a line that we are open for dinner Tuesday through Sunday and do pickup and delivery, and two buttons, Order Online and See the Menu.
Now the hero photo. Two honest options: upload a wide shot of your dining room or your pass (+ → upload → Insert), or generate something to hold the spot until you get a real one. Hit the + button, choose Generate Image, and describe it:
A warm dim neighborhood restaurant dining room at night, wooden tables, low pendant lights, an open kitchen glowing at the back, no people, shot wide.
It saves straight to your Media Library. Click Insert and tell the section “use this as the hero background.” Then swap in a photo of your actual room the first slow Tuesday you get — the real one always outperforms the generated one.
create a menu section grouped into Starters, Pizza, Pasta, and Dessert — each item with a name, a short description, a price, and small tags for vegetarian and gluten free, laid out so it reads easily on a phone.
create an ordering section with a big Order Direct for Pickup button first, then smaller links for the delivery apps underneath, and a line saying ordering direct means the whole ticket stays with our kitchen.
create an hours and location section — our address in Lawrenceville, a map, dinner Tuesday to Sunday 4 to 10, closed Monday, our phone (412) 555-0193, a note that street parking is easiest on Butler, and a Reserve a Table button.
create a private events and catering section — our back room seats 30, we do rehearsal dinners and office parties, a sample family-style menu per person, and a short form asking for the date, headcount, and what they have in mind.
create a photo gallery section showing our food and the dining room, a few large images with short captions.
Then fill it with your own plates: + → upload → Insert into each slot. Shoot them at the pass in daylight if you can, from slightly above, before anyone eats. Never AI-generate a photo of “your” food — somebody is going to order that dish and compare, and a plate that doesn't match is the fastest way to a one-star review.
Seven short prompts. Read them back — there's nothing technical in a single one of them. And nothing is final: every section is a conversation, so when something isn't right, you just say so:
Make the Order Direct button bigger than the app links.
Move today's hours up into the hero.
Add a line that the kitchen closes at 9:30 on Sundays.
That's the entire “how,” and it's the part the delivery apps hope you never figure out.
Two tips from watching a lot of these builds: put the direct-order button above the app links, always — most people tap the first thing that works, and that single ordering decision compounds over a year. And keep the menu as text you can edit yourself, because the moment updating a price means emailing someone, your menu starts going stale, and a wrong price on the internet is an argument at the register.
What does a restaurant website cost in 2026?
| Option | Upfront cost | Ongoing cost | Time to launch | Who does the work |
|---|---|---|---|---|
| Web design agency | $3,000–$8,000 | $50–$200/mo maintenance | 4–8 weeks | Them — and every menu change is a ticket |
| Freelancer | $800–$3,000 | Varies | 2–4 weeks | Them — quality and availability vary |
| Wix / Squarespace | $0 | $192–$588/yr, forever | Days–weeks | You, with drag-and-drop, on their platform |
| Delivery-app listing only | $0 | Commission on every order, commonly 15–30% | Minutes | Their marketplace — and they keep the customer |
| AI page builder + WordPress hosting | A fraction of an agency build | Standard WordPress hosting | An afternoon | You, by describing what you want |
Run the last row against the fourth one for a second. A site you build once is a fixed cost. A commission is a percentage that grows precisely as you succeed — the better your month, the more you hand over. That's the difference between renting leads and owning your pipeline, and in this business it shows up on every single ticket.
Common questions
Do I need a website if I'm already on DoorDash and Uber Eats?
Yes, and for a specific reason: on those apps you are a listing among competitors, the commission applies to everyone including your regulars, and the customer belongs to the platform — you don't get their email, and you can't reach them when you launch a new menu. Keep the apps for discovery if they work for you. Own the repeat business.
Should my menu be a PDF?
No. A PDF opens at the wrong size on a phone, can't be read by search engines, forces a download on slow connections, and takes a design tool to update. Put the menu on the page as real text with real prices. It's the single highest-impact change most restaurant sites can make, and it takes one prompt.
Can people order directly from my site?
Yes. The simplest route is to point your Order Online button at whatever ordering or POS system you already use, so your tickets, printer, and reports keep working exactly as they do now. It's normal WordPress underneath, so if you'd rather run ordering on your own site later, an ordering plugin drops in via shortcode.
How do I update the menu when prices change?
You type the change. Open the menu section, say “change the margherita to $18 and take the special off,” and publish. That's the whole point of the menu living as text you control — when an update takes thirty seconds and no invoice, it actually happens, and your site stops lying about your prices.
Do I need online reservations?
Only if you take them. If you're walk-in and pickup, a reservation button is clutter that creates expectations you don't meet. If you do take them, point the button at the booking system you already use rather than trying to rebuild it — the goal is one obvious tap, not a second system to maintain.
What photos should I use?
Your own food and your own room. Shoot plates at the pass in daylight, from just above, before service gets loud. Get one honest wide shot of the dining room with the lights how they actually are at dinner. Never generate a picture of a dish you serve — someone will order it expecting that plate. Generated images are fine as a temporary background, not as your food.
Will it help me show up on Google?
It helps in a way a PDF never could, because your dish names and neighborhood are now real text on a real page. The builder includes an SEO optimization step that adds alt text, structures headings, and generates schema markup. Beyond that, claim your Google Business Profile and keep the hours accurate there — most “pizza near me” taps resolve in the map results before anyone reaches a website.
How long does this actually take?
Budget an afternoon between services: roughly an hour building and refining the seven sections, and the rest on the two things worth doing slowly — typing the menu accurately and shooting a few honest photos. Both are things only you can do, and both keep earning after the site is up.
Build it between lunch and dinner
The seven prompts above are the whole playbook. Copy them, swap in your restaurant and your dishes, put your own order button above the app links, and the site can be live before the weekend rush. The apps will still bring you strangers — fine, that's what they're good for. But the regulars, the ones who searched your name because they already love you? Stop paying rent on your own customers.
Seven prompts, a menu people can actually read, and an order button that keeps the whole ticket — on your own WordPress install.
Get Started Today