How to keep your website's menu, prices and opening hours up to date without high costs or bugs

Why website content goes out of date

It's rarely because nobody cares. It's because updating the website is a job of its own. Someone has to remember the login for a website builder they use twice a year, find the right page, and edit it without breaking the layout. Or they email whoever built the site, wait a few days and pay for twenty minutes of work.

So people take the shortcut. They upload a PDF of the menu, or a photo of the printed one, and move on. Six months later the website shows dishes that are gone, prices that have gone up, and opening hours that were right last summer. Sometimes the menu link has stopped working altogether.

What stale content costs you

• Wasted trips and awkward conversations. Customers who turn up when you're closed, or ask for the dish they saw online, or query a price at the till.
• Lost bookings on phones. Most people check a menu on their phone. A PDF or a photo of a printed menu means pinching and zooming, and plenty of people give up and look elsewhere.
• Invisible to Google. Search engines read text on web pages far better than text inside PDFs or photos. A menu that is a picture mostly can't help you show up for searches like the dishes you serve.
• Allergen risk. If a recipe changes and the allergen information online doesn't, that is a real safety problem, not just an out-of-date page.

The fix: keep the content separate from the design

The most useful change is also the simplest. Instead of the menu being part of a designed page, keep it as plain data: a list of dishes, each with a name, description, price and allergens, plus your opening hours and this week's specials. A template then turns that data into the finished web page.

Changing a price then means editing one line, not editing a page. You can't accidentally break the layout, because you never touch it. Every update looks as polished as the first version, and the same data can produce the web page, a printable menu and the hidden information Google reads, so they never disagree.

Where the data can live

• A spreadsheet. A shared Google Sheet with one row per dish is something anyone can edit from a phone. The website rebuilds from it when you publish.
• A simple form. For things that change often, such as specials or holiday hours, a short form is quicker still.
• A message to someone who does it for you. If you would rather not touch anything, a managed service can take changes by email or message and publish them the same day.

Cheap, reliable hosting for this kind of site

A menu, a price list and opening hours don't need a database or a heavy content management system. The page can be built once each time the content changes, and then served as plain, pre-built HTML. This is called a static site, and for a small business it has three big advantages.

• It costs very little. Static hosting on a content delivery network is free or costs a few pounds a month at the traffic a restaurant or shop gets.
• There is little to go wrong. There are no plugins to update and no database to be hacked, which removes the most common causes of small business websites breaking or being compromised.
• It is fast and secure. Pages load quickly on a phone signal, and https (the padlock) comes as standard, so browsers don't warn visitors that the site is not secure.

You don't have to replace your whole website to get this. A menu or price list can live at its own address, such as menu.yourrestaurant.co.uk, with the menu button on your existing site pointing to it.

Stopping mistakes before they go live

Because the content is data, it can be checked automatically before anything is published. A good setup refuses to publish, and says why, if something looks wrong.

1. Check the data. Every price is a sensible number, every dish has its allergens filled in, and nothing is left blank.
2. Check the page. Links work, images exist, and the page builds without errors.
3. Preview and approve. Changes appear on a private preview first. Anything touching allergens is approved by the owner or chef before it goes live.
4. Keep every version. If a mistake does get through, the previous version can be restored in a minute.

Make the content easy for Google to find

Once your menu or price list is real text on a web page, you can also add structured data: information in the page's code, invisible to visitors, that tells search engines exactly what is on it. For a restaurant this covers the menu, dishes and prices, opening hours and address. It helps search engines understand and present your business accurately.

Keep your Google Business Profile consistent with your website too, especially opening hours. It is often the first thing people see, and a mismatch between the two is confusing.

Doing it yourself or having it managed

If your website builder has a good built-in menu or price list tool and you will genuinely use it, that may be all you need. If updates keep slipping, a managed service is usually a small setup fee followed by a monthly fee that covers hosting and keeping the content current. Whichever you choose, ask these questions first.

• Who owns the content and the domain? You should. Your menu, your words and your web address should never be held by a supplier.
• How quickly are updates made? Same day for specials and holiday hours is a reasonable expectation.
• What happens if I leave? You should be able to take your content with you in a usable format.
• Who checks allergens? The answer should always be you, with a clear approval step before anything is published.