Frequently asked questions

A fully managed, custom-coded website for your restaurant: menu pages set as structured content rather than a PDF, a reservation and enquiry flow that connects to whatever you already use, 90+ PageSpeed, managed hosting, a free domain, and 2 researched articles a week on The Folio and The Broadside, 3 on The Standing Order. Nobody on your team edits the website directly; you send us changes and we make them.

7 days on The Folio, 10 on The Broadside while the AI Engine is trained on your menu and policies, and 15 on The Standing Order while the Content Engine's editorial calendar is built. The clock starts at the onboarding call, not at purchase, so the sooner the onboarding form is in, the sooner you are live.

No. The words on your menu are yours, since nobody outside your kitchen can describe a dish the way it was actually built. We handle the structure, the typesetting and the speed of the page the menu sits on, and researched blog articles are written separately from the menu itself.

Each of those is the right answer for some restaurants, and we have written ten comparison pages that say so, including the cases where the other option wins. The short version: a builder is a tool somebody has to operate, a freelancer is a project rather than a relationship, an agency sells attention rather than the asset attention arrives at, and we sell the asset with the work attached.

A revision is any change request you send, and there is no limit on how much goes into one. Swapping the entire seasonal menu, adding a new wine list, or updating hours for a holiday closure: each is one revision, not one per item changed. 5 are included every month. After the fifth, each additional revision is a flat $20, with no cap on how many you can buy and no hourly billing anywhere. Every revision is completed within 2 to 5 working days, whatever the size.

Raise it in your client portal. You describe the change, attach the new menu or prices, and it lands with the team as a tracked request so you can see where it is. You can also email us or reply to any thread with our team, and we log it for you. Unused revisions do not roll over to the next month.

Yes, as long as it is submitted as one request. "Replace the current tasting menu with these six new courses and this new wine pairing list" is one revision regardless of how many individual dishes and prices it touches, which is exactly how a real seasonal changeover works for a chef-led kitchen.

Both mobile and desktop, on every plan, on the pages we build. Pages are custom coded, ship almost no unnecessary code and are served from a global edge network, so the speed is there on launch day rather than after an audit a year later. If a page drops below it after a change on our side, fixing it is our job and it does not use one of your revisions.

It can help, and we will not promise a figure. Google documents Quality Score as being calculated from three components, one of which is landing page experience, described as how relevant and useful your landing page is to people who click your ad, and it lists the quality of your ads and landing page as a factor in Ad Rank. Google also calls Quality Score a diagnostic tool rather than an input to the auction. The mechanism is real; a specific reduction in cost per click is not something anybody can honestly guarantee.

Because a guest deciding where to eat is comparing three tabs on a phone, often on poor signal, and the slowest tab loses. A menu page is also usually the heaviest page on a restaurant site, since it is the one people load photographs onto, which makes it the page most worth building carefully.

It answers common guest questions, such as dietary accommodations, dress code or private dining capacity, using information trained on your real menu, hours and policies, so a guest gets an answer without waiting for a phone call to be returned. It is included from The Broadside up.

No. It answers questions and can point a guest to your existing reservation platform or contact form, but the reservation itself is completed through the booking system you already use, so nothing about how you actually manage seating changes.

A privacy policy, terms of use, a cookie policy with consent that genuinely gates the scripts it names, and an accessibility statement. They are written as a starting point for a restaurant website rather than as legal advice, and if your situation is unusual you should have a lawyer in your state read them before launch.

It is built with WCAG 2.1 Level AA in mind: real contrast, keyboard operation, visible focus, tap targets a thumb can hit and motion that respects a reduced-motion setting. We say built with it in mind rather than compliant, because accessibility is an ongoing property of a site rather than a certificate, and your own content affects it too.

No, and we will not. Menu pages present your own wording about dietary accommodations and allergens exactly as you supply it. We are not a food safety, health or licensing authority, and nothing on your site will imply that we are.

No. One domain is included free for as long as your plan is active, registered in your name, so you own it outright. If you already have a domain we point it at the new site instead and nothing changes for guests who know your current address. If you ever leave, tell us where to send the domain and we transfer it at no charge.

Yes. A restaurant inside a hotel or boutique property can have its own domain or subdomain, registered in your name as part of the plan, so the site can be built to rank for the restaurant's own name rather than living buried inside the property's main site.

You pay the monthly fee for the tier you choose up front: $117, $247 plus AI usage, or $597 a month. The $647 one-time build fee is invoiced only after your site is live and you are satisfied with it. Domain and hosting are inside the monthly figure.

Email us and say you want to cancel. Your message must reach us at least 2 business days before your next invoice date, during business hours, which are 9:00 to 17:00 Central Time, Monday to Friday. A message sent outside those hours counts from the start of the next business day, so a weekend email does not give 2 business days of notice for an invoice due Monday or Tuesday. With valid notice, no further invoice is raised and your site runs to the end of the month you have paid for. With late notice, the next invoice is charged as normal and the cancellation takes effect at the end of that month.

No. All sales are final, and that includes monthly fees, the build fee, extra revisions and any cost we pass through at what our providers charge us. We do not refund for a change of mind or for a month you did not use. The one exception is a duplicate or incorrect charge made by our billing: tell us within 30 days and we correct it within 10 working days. The build fee is charged only after you have approved your site, which is exactly why it is not refundable afterwards.