Diners choose the restaurant before they taste a single bite.
The decision about where to eat tonight happens on a phone, in about a minute, and it turns on four questions: what is on the menu, what does it cost, are they open, and how do I book or order. We build restaurant websites that answer all four before the thumb gets tired, with the structure behind them that helps search engines and AI assistants recommend you.
The table gets decided on the couch.
Nobody wanders into a restaurant cold anymore. Whether the trigger is a date night, a visiting relative, or plain hunger at 6pm, the path is the same: somebody searches, somebody scrolls, and the group goes where the phone made the strongest case. The restaurant that shows tonight's actual menu, current hours, real photos of the food, and a working reservation button wins the table. The one whose site shows a blurry PDF from two owners ago does not get a second look, no matter how good the kitchen is.
Hours deserve special mention because they are where trust dies fastest. A diner who drives across town to a door that closed an hour ago does not blame Google, they blame you, and they say so in a review. Your website is the one source of hours you fully control, and when it is right, kept current, and marked up so machines can read it, the listings that copy from it tend to be right too. Holiday hours, a private event closure, a kitchen that stops seating at 9: all of it belongs on a page you can change the same day.
And the way people find restaurants is shifting under everyone's feet. A growing share of "where should we eat" questions now get asked to AI assistants, which answer from whatever structured information they can actually read. A menu trapped in a PDF is invisible to them. A menu published as real text, with restaurant schema behind it and reviews marked up properly, is quotable. Nobody can promise you the recommendation, and we never will, but you can be one of the few restaurants in your area that is even legible to the systems doing the recommending.
Your menu is a web page, not a download.
The single most common failure on restaurant websites is the menu as a PDF. It made sense once: the print file already existed, so somebody uploaded it. But on a phone it means pinching, squinting, and sideways scrolling, and to a search engine or an AI assistant it is close to a locked box. The dish names, the prices, and the words people actually search for, like the name of that one appetizer their friend keeps talking about, are all invisible.
We build the menu as a real page. Sections, dishes, descriptions, prices, and dietary notes are all live text, readable one-handed in a parking lot, indexable by search engines, and structured so machines know a price from a pepper. When a dish gets 86ed or a price moves, you send us the change and it goes live; on the Diamond plan those menu updates are included, not billed as extras. The reason PDF menus persist is that editing the website was always somebody's unpaid second job. On Diamond it is our job, and we like it.
What a restaurant site needs.
Open or closed right now, tonight's hours, the address with a working map link, and parking notes if you have them, all visible without scrolling. The most expensive mistake a restaurant site can make is hiding the two facts every visitor came for.
The site plugs into whatever you already use. OpenTable, Resy, Toast, Square, direct phone bookings, or the delivery platforms all get clear buttons where diners expect them. We do not replace your systems, we make them easy to reach, and swapping a provider later is a small change, included on Diamond.
Dedicated slots for your best shots of plates, the room, and the bar, compressed so pages stay fast on a phone in a car. Your photos, not stock, because a diner can spot a stranger's brisket instantly. If all you have is a phone camera, we will tell you which ten shots to take.
Restaurant schema, the menu as machine-readable text, marked-up hours and reviews, and one page per thing you want to be found for, from Sunday brunch to private dining. This is the groundwork that makes you eligible when search engines and AI assistants answer where to eat.
Read the menu on a live restaurant site we built.
A live restaurant site we built, with the menu as a real page. Yours gets your brand, your dishes, your photos, and your reservation links. There is a bakery build in the gallery too, if counter service is closer to your world.
Costs less than one slow Tuesday.
A custom build, hosting, security and backups, contact forms straight to your inbox, a visitor dashboard and an instant answers widget. One location, the menu built as a real page, live in days.
Everything in Gold with no build fee, plus every tool package, monitoring and updates with menu changes included, priority on requests, extra locations, and your numbers emailed monthly.
Run it against your covers. Gold costs less per month than most restaurants gross from two tables on a Friday, and it works every night, including the ones you are closed. The four tool packages bolt onto Gold one at a time: Get found at $35 a month for the restaurant schema and review markup that search and AI assistants read when someone asks where to eat, Capture the lead at $25 for tracked calls with the spam filtered before it interrupts a dinner rush, Follow up automatically at $25 for private event and catering inquiries that go quiet, and Look the part on paper at $25 for branded quotes and invoices on that same catering work. All four on Gold come to $190 a month plus the build fee, so at that point we will tell you to take Diamond at $215 instead. Every package also works on a restaurant site somebody else built.
No contracts. Cancel anytime, and the domain and files are yours. Full details on the pricing page.
Asked by owners in your business.
How much does a restaurant website cost?
On our Gold plan it is a $250 one time build fee and $80 a month, which covers the custom build, hosting, security, backups, contact forms, a visitor dashboard, and an instant answers widget. Diamond is $215 a month with no build fee and includes every tool package plus monitoring, content updates with menu changes included, priority on requests, and monthly reporting. All pricing is public on the pricing page, and there is no contract.
We already have a Google listing and an Instagram. Why do we need a website?
Because both of those send people somewhere, and right now that somewhere is a platform you do not control. The Google listing shows whatever photos and hours it wants in whatever order it wants, and Instagram buries your menu three taps deep. A website is the one place where the menu, the hours, the photos, and the reservation link are exactly what you decided, and it is what the listing and the bio link should point at.
Can you put our menu on the site without making it a PDF?
Yes, and that is the point of the build. The menu becomes a real page with sections, dishes, prices, and dietary notes as text, readable on a phone without pinching, indexable by search engines, and quotable by AI assistants. A PDF is a photograph of a menu; machines cannot read it well and neither can anyone on a phone in a parking lot.
We take reservations on OpenTable and orders through Toast. Does the site replace those?
No, it connects to them. Whatever you already use for reservations, ordering, or delivery keeps doing that job; the site gives each one a clear button in the places people look for it. You keep your existing systems and your existing accounts, and if you switch providers later, changing the links is a small update, included on Diamond, not a rebuild.
Will we show up when someone asks Google or ChatGPT where to eat?
Nobody can promise a placement in those answers, and we will not either. What we do is the groundwork those systems read: restaurant structured data, the menu as machine-readable text, accurate hours, and reviews marked up so they can be quoted. That makes you eligible to be the answer when someone nearby asks, and most restaurants have none of it in place.
Who updates the menu when prices or dishes change?
On the Diamond plan, we do, and it is included: send the change and it goes live, whether that is a price bump, an 86ed dish, a seasonal menu swap, or new holiday hours. The whole reason restaurants fall back to PDF menus is that editing the website was somebody's unpaid second job; Diamond makes it our job. On Gold, updates are quoted as you need them, which suits a menu that rarely changes.
How fast can the site be live?
Days, not months. You send your menu, your hours, your reservation and ordering links, and your best photos of the food and the room; we handle design, copy, and setup, and typical builds go live inside a week. On the Diamond plan, changes after launch are included and prioritized, so a new brunch menu or a private dining page is a same-week request.
The next "where should we eat" search should surface you.
Leave your details and we reply within one business day with a price and a plan for your restaurant. No sales call unless you ask for one.
Want the numbers first? Both plans are printed on the pricing page, or open the live demo.