Pull up your website on your phone right now and look at the menu. Is it what you are serving tonight?
For most restaurants and breweries I talk to, the honest answer is “mostly.” A beer that kicked last month. A dish that came off in the spring. Prices from before the last supplier increase.
“Mostly” feels harmless from the inside, because you know what you are actually serving. From the outside it is the whole picture. The person on their couch deciding between you and the place down the road only has your menu to go on. If it is wrong, one of three things happens, and none of them is good.
What a stale menu actually costs
The customer who never shows up. They wanted the hazy IPA they saw on your site. They drove over. It has been gone for three weeks. They order something else, maybe, and they do not make the drive next time based on your menu, because they have learned it lies. You will never hear about this. It does not show up in any review. It just quietly lowers the number of people who trust your website enough to plan around it.
The customer who shows up annoyed. The dish they came for is off the menu. The price is eight dollars higher than the site said. Your staff absorbs the conversation. This one you do hear about, usually from the server.
The customer who never found you at all. This is the invisible one, and it is the biggest.
For some of your customers, the menu is a safety document
There is a group of people for whom an out-of-date menu is not an annoyance. It is the reason they cannot come at all.
Someone with a peanut allergy, a shellfish allergy, celiac disease, or a kid with a dairy allergy does not pick a restaurant the way everyone else does. They read the menu online first, carefully, looking for what they can eat and what they need to avoid. Most of them will not call to ask. If they cannot tell from your website, they choose the place where they can. And they rarely decide alone: one person in a party of six who cannot eat safely at your place moves all six somewhere else.
This is where “mostly current” gets dangerous. Recipes drift. The house sauce now has fish sauce in it. The burger moved to a brioche bun with egg. The fries now share a fryer with the breaded chicken. The seasonal salad got walnuts. Every one of those changes happened in the kitchen weeks ago, and the website still describes the old version. Someone reads it, trusts it, orders, and reacts. That is a night your staff never forgets, and it started with a web page nobody updated.
Breweries are not exempt. A person with celiac disease looks for the gluten-free beer, the cider, or the seltzer on your tap list before they agree to meet friends at your place. If the site shows a gluten-free option that kicked in July, they arrive with nothing safe to drink. If the site shows nothing, they never arrive.
What this asks of your online menu:
- Ingredients that matter are listed. Not the whole recipe, but the nuts, dairy, egg, gluten, shellfish, and soy that someone would need to know about, at the item level.
- A clear note on shared equipment if the kitchen cannot guarantee separation. “Fried items share a fryer” is honest and takes one line.
- It is current. An allergen note from the old recipe is worse than no note, because it invites trust it does not deserve.
- It is text, not a picture. Screen readers cannot read a photo of a chalkboard, and neither can the person zooming in on a blurry PDF at a bus stop.
The people who need this are quiet about it and loyal when they find a place that gets it right. A menu that tells them what is actually in the food is one of the cheapest ways a restaurant can earn a regular.
Why your menu affects whether people find you
Google wants to send people to businesses that are open, current, and accurate. It measures that in ways most owners never see.
A menu that lives as real text on your website, with dish names, beer styles, and descriptions, is something Google can read and index. When someone nearby searches “hazy IPA near me” or “wood-fired pizza Derry NH,” a current, readable menu is one of the strongest signals you have that you are the answer. A PDF from the spring, a photo of a chalkboard, or an image of the menu gives Google nothing to work with.
Freshness matters too. A page that changes regularly tells search engines the business is alive and maintained. A page that has not changed since 2024 tells them the opposite, and it is not just your menu page that pays for it. Your whole site is judged partly on whether anything on it is ever updated.
Then there is your Google Business Profile, the box that shows up on the map. Google pulls menu information into it, and increasingly answers “does this place have X” directly in search results, drawn from what it can read on your site. If your online menu is wrong, Google is now confidently telling strangers wrong things about you, with your name on it.
Why menus go stale in the first place
It is never because the owner does not care. It is because updating the menu is a chore that belongs to nobody.
The web menu was built by a designer or an agency, and changing it means emailing them and waiting. Or it was built in a site builder that only one person knows how to use. Or the menu is a PDF, which means opening a layout file, editing it, exporting, uploading, and hoping the link on the site points at the new one. Or the point-of-sale system has the real menu, the website has a copy, and nobody has time to reconcile them.
Every one of these is a two-source problem. The menu exists in the kitchen or the POS, and it exists again on the website, and every change has to be made twice. Two sources drift. It is not a willpower problem. It is a design problem.
The fix: one source, and it is the one you already update
The only online menu that stays current is one that updates itself from something your staff already maintains.
For a brewery, that is almost always Untappd. The taproom keeps it current because the tap board depends on it. A website that reads from the same feed stays current for free. Republic Brewing Company’s site works this way: Peter edits Untappd, and the website, the TV board, and the printable menu all follow within the hour. He has not “updated the website menu” in over a year, because there is nothing to update.
For a restaurant, the equivalent is the point-of-sale system. If you run Toast, Square, or something like them, the real menu already lives there, with current items and current prices, because that is what the register charges. A website that pulls its menu from the POS cannot disagree with the kitchen. Change a price on the register, and the website changes with it. I am building exactly this for a wood-fired pizzeria right now: a web menu and a print menu both driven from their Toast menu, so the owner maintains one thing.
If neither of those fits, the fallback is a menu that the owner or manager can edit in a plain form on their phone, in under a minute, with no designer in the loop. Not a page builder. Not a PDF. A list of items with names, prices, and descriptions, and a Publish button.
Whichever one you use, allergen notes belong in that same source, tied to the item. When the recipe changes, the note changes in one place and follows the dish to the website, the print menu, and anywhere else it shows up. Allergen information kept in a separate document is the first thing to fall out of date.
Any of the three works. What does not work is “email John when something changes.”
Hours belong in the same conversation
Everything above applies to hours, and hours are worse, because a wrong menu costs you an order and wrong hours cost you a visit. The number of restaurant websites showing pre-pandemic hours, holiday hours from last December, or “kitchen open until 9” when it closes at 8 on weeknights is remarkable.
Hours should be maintained in one place, and that place should feed the website, the Google Business Profile, and the structured data search engines read, all at once. If you are changing hours on Google and separately on your website, one of them is wrong right now.
A quick audit you can do tonight
- Open your site on your phone. Find the menu. Time how long it takes. If it is a PDF, note whether it opened in something readable or downloaded to who-knows-where.
- Compare it, line by line, to tonight’s actual menu and tonight’s prices.
- Read it as someone with a nut allergy or celiac disease would. Can they tell what is safe? Is what it says still true in the kitchen?
- Search your business name on Google. Look at the menu and hours in the map box. Compare them to reality.
- Ask yourself who would update all of it if a beer kicked tomorrow, and how long it would take them.
If the answer to step five is “me, eventually,” the menu is not going to stay current, and the fix is not trying harder. The fix is a site that reads from the source you already keep.
That is most of what I build for breweries and restaurants, and it is the reason their menus are right at 9pm on a Saturday without anyone thinking about it. See how it works for breweries or get in touch.
