Daily lunch on your website and Google: a menu that is right every week (2026)

Lunch is decided in five seconds

An evening guest compares, reads reviews and books a table. A lunch guest has half an hour and a hungry group of colleagues behind them. They search for "lunch" and the town, open two tabs and pick the place where the answer shows immediately. What should show first on the lunch page is therefore not the week but the day:

• Today’s dish, at the top. The rest of the week below, for those who plan.
• Price and serving hours on the same line, not in the footer.
• What is included. Salad bar, bread, coffee. That is often what decides between two places at the same price.
• The vegetarian option and whether the lunch can be taken away.
• The line about allergies. That the guest can ask the staff, and the phone number. Why it is needed is in the guide on allergens on the menu.

Image and PDF: the lunch menu nobody can read

The most common way to publish lunch is a photo of the chalkboard on Facebook and a PDF on the website. Both work for those who already follow the place. For everyone else they are poor. A PDF has to be opened and zoomed on a phone, a photo in a feed cannot be searched, and Google, a screen reader and the AI services more and more people ask "where can I have lunch in Åhus?" read text far more reliably than text in an image. When Rökeriet in Åhus changed websites, the menus were PDFs. In the new one they are text directly on the page, and that is the single easiest improvement a restaurant can make. The same logic that makes a site show up in AI searches in the first place.

Write the week once, let the page switch day

The worst thing a lunch page can show is not an empty menu but last week’s. The guest comes for the fish that was served last Tuesday, and trust in the page is gone after a single time. It happens because someone has to remember to change the menu every Monday morning, in the middle of deliveries and prep.

In Rökeriet’s build the kitchen plans lunch weeks ahead and publishes them when they are ready. After that it is the calendar that decides which week applies, not a button. On Monday morning the page switches week by itself, and each day today’s dish shows first, without anyone needing to be awake. And if a week has passed without the next one being published, it is not carried on under a new week number with last week’s dishes. Better an honest blank than a confident mistake.

Exceptions belong to the day, not the week. In a midsummer week no lunch at all is served on the Friday, neither the dish of the day, the fish of the week nor the vegetarian one, and at the weekend there is no salad bar or coffee. The line "served Monday–Thursday" is therefore never written by hand. It is computed from which days are ticked, because a hand-written range is a range that becomes wrong the week someone ticks Friday again. The same calculation drives the lunch page, the printout for the counter and what the chat knows, so the three cannot say different things about the same week.

One text, four recipients

Lunch rarely goes only to the website. At Rökeriet it also went to the newspaper’s lunch guide and to a company in the village that orders lunch for its staff, and each recipient wanted it their way. So the week is written once, and the rest are extracts of the same text:

• The newspaper’s lunch guide. Kristianstadsbladet has a portal where the lunch is entered. The panel produces a ready text block in the same order the guide is printed, with prices and serving hours, and a button that copies it.
• The company that eats lunch. An email with the week’s dishes without prices, since they pay another way, and a line under each dish with what it contains, such as pork and lactose, which they asked for.
• The weekly newsletter. Lunch is what changes every week and therefore the best reason for a newsletter that actually gets sent, with the consent rules that apply there.
• The sheet by the counter. A printout of the same week, so the staff and the page say the same thing.

Google: the profile, the hours and the menu link

What the lunch guest sees first is often not the website but the Google Business Profile in the map. Three things there make a difference. Add the lunch hours as separate hours under "more hours" if your category has that option; which types exist depends, according to Google, on category and country, and they show only once the regular opening hours are filled in. Point the menu link to the lunch page, not to a PDF. And keep the hours the same on the profile, the site and the sign, because three different answers to "when do you serve lunch?" are worse than one. The rest of local visibility is in the guide on local SEO.

The free route: five things by next Monday

1. The lunch as text on the website, not an image or PDF. Even a simple page in the publishing tool you already have is enough.
2. The week number in the heading. "Lunch week 42" makes an old menu obvious, to the guest and to you.
3. A fixed time for the switch, for example Friday afternoon, so that Monday morning never depends on anyone.
4. The lunch hours in the Google profile and the menu link to the lunch page.
5. The same hours everywhere: profile, site, sign and the newspaper’s lunch guide.

When I build a restaurant site, the lunch is entered once in the panel from a phone, the page switches day and week by itself, and the same text becomes the newspaper block, the company email, the newsletter and the printout. What it costs is listed openly under services, and you can read who builds it under about me.