Everything included in a MenuWebStudio website

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.

Topics your future guests are searching for: dining guides for your area, context on your seasonal menu, and questions specific to your cuisine and neighborhood, each 2,500 to 3,200 words. They are researched and written around your actual restaurant rather than a generic template reused across clients.

2 a week on The Folio and The Broadside, and 3 a week on The Standing Order, at roughly four weeks a month, published to your site's blog automatically.

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.

Four separate jobs. The technical side is set at launch and kept correct: clean addresses, correct headings, sitemaps, redirects and internal links. The on-page side is your menu, wine list, story and service pages written as real indexable text rather than uploaded as a file. We build location and service-area pages for the areas you genuinely serve. And we publish researched articles every week, because a site with nothing new on it has nothing new to rank.

Answer engine optimization means writing the answer first and explaining afterwards, so a search engine or an assistant can lift a clean answer out of the page. Every significant page on your site opens by answering its own heading in the first sentence and carries its own visible questions and answers marked up as structured data.

Nobody can guarantee that, and anyone who does is selling you something they cannot deliver. What we do is the work that makes it more likely: a machine-readable summary of the site, clean semantic markup that reads correctly without styling, facts stated plainly enough to be quoted, and consistent naming so your restaurant reads as one entity everywhere.

It is a block of machine-readable information that tells a search engine what a page is rather than making it guess. We add the right type to the right page: organization and local business details, the services you offer, your questions and answers, the breadcrumb trail and article markup on everything published to your blog.

Our stated expectation is 3 to 5 months, and that window only starts when the publishing does. We will not put a number on where a page lands, because search positions are not something any studio controls.

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.