Friday, half past six. Someone searches for a table, finds your site, and taps the menu link. It opens a PDF from last winter, with a dish you stopped serving in the spring and none of the new ones. They ring, ask about the dish, and the person on the phone sighs. That sigh is the cost of a website nobody has looked at since the last menu change.
Restaurant website maintenance is mostly about this sort of thing: a small, busy business with fast-changing facts and almost no time to edit them. This article is for owners and managers in the US, UK, Australia and elsewhere, including those who hand the website to a team in another country. It covers what changes weekly, what breaks without telling you, and how to share the job so that it does not rest on one tired person.
What the site is actually for
Most people who visit a restaurant website want one of five things, and they want them quickly, on a phone, usually while deciding where to go:
- What is on the menu, and is there something I can eat?
- Are you open now, or when?
- Where exactly are you, and how do I get there?
- Can I book, or order, without ringing?
- Is it worth the trip? (Photos, atmosphere, reviews.)
Each of those is a thing that can go wrong in its own way. A neat way to plan the upkeep is to take them one at a time, which is what the next sections do. Notice that none of them is “design”. The site can look dated and still do the job well, as long as these five answers are right.
Behind those answers sits ordinary technical upkeep, and it is the same for every WordPress site: updates, backups, security checks, uptime alerts. The page about what a web maintenance agency in India covers for overseas clients is a plain list of that monthly work, which makes it a handy yardstick for any quote you receive.
The menu: text beats a PDF
A menu uploaded as a PDF is easy to produce, and awkward to use. On a phone it often means pinching and zooming. Search engines may read it poorly. Screen readers can struggle with it. And because it is a file, it is easy to forget it exists when the printed menu changes.
Where you can, put the menu on the page as real text, with section headings for starters, mains, desserts and drinks. It loads faster, reads well on small screens and can be edited in a minute. If you keep a PDF for people who want to print it, label it with its date, and make sure the old file is actually replaced rather than a new one uploaded next to it, so the link you share never points at last season’s version. Make sure it is a properly built PDF with real text, not a scanned photo of the menu, so people using screen readers can still read it.
Allergen and dietary information
If your menu carries allergen or dietary labels, treat them as information that must be right, not decoration. The rules about what must be provided differ by country and sometimes by local authority, so check with your local food-standards body. The maintenance habit is simple: whenever a dish changes, the website, the printed menu and the staff briefing change on the same day, and one named person confirms it.
Hours, holidays and special days
This is where the Friday-night sigh most often begins. Put your regular hours on the site in plain text, then keep a second list in your head or on the kitchen wall: the exceptions. Christmas, the local festival, the private function, the week the chef is away.
Three habits help.
- Update the exceptions in one go. At the start of each quarter, list the closures and unusual hours you know about, and put them on the site together.
- Match your Google listing. Customers often see your hours on Google before they see your site. If the two disagree, someone is wrong, and it will be the one that annoys a customer. Our post on Google Business Profile services, products and posts shows where a listing can carry extra detail.
- Use a notice banner sparingly. A bar at the top for “closed Monday for a private event” is useful. A bar that has said “New summer menu!” since last year teaches visitors to ignore it.
Booking and ordering: the part that costs real money when it fails
Most restaurants do not take bookings or orders on their own site. They use an outside system, and the website holds a button or an embedded form. That arrangement is sensible, and it has a particular weakness: the website and the booking system are run by different companies, and neither tells the other when something changes.
In restaurant website maintenance, this is the check that pays for itself. So check these by hand, as a customer, on a phone, at least once a month and always after any change to the booking account:
- Does the “Book a table” button open the right page for the right restaurant?
- Can you complete a test booking from start to finish and get a confirmation?
- If you use online ordering, do the dishes, prices and delivery areas on that system match the menu on the site?
- Does the confirmation email actually arrive, and not in spam?
If the site takes orders directly, the technical risk grows. Payment plugins and ordering plugins need updating, and updating them without a recent backup is how a Saturday service goes wrong. A careful team applies updates outside your busy hours and checks that an order still goes through afterwards. Ask any provider how they do this before the first update, not after.
A phone number that is tappable also earns its place here. Plenty of people would rather ring than fill in a form, and a number that is plain text on mobile means they have to copy and paste it. Tap-to-call buttons are worth adding if yours is still static.
Photos and speed on a phone
Restaurants rely on pictures, and food photographers often hand over files that are enormous. If each one is uploaded as it came, a gallery page can take a long time to load on a mobile connection, and a hungry visitor does not wait. A good routine is to resize and compress every photo before it goes up. If you update the gallery regularly, ask whoever maintains the site to try a few main pages on an ordinary phone from time to time, not just on the office computer.
The same goes for a full-width background video of the kitchen. It looks lovely on the owner’s fast laptop, and can make a phone struggle. The test is simple: open the home page on your own phone, away from the restaurant wifi, and time how long the first screen takes. Keep the home page light, and put the heavy images further down, on their own page.
Also, add short descriptions to photos. They help people who cannot see the image, and they help search engines understand what the picture shows.
Updates, backups and what it means for a busy kitchen
Behind the front of the site sits the machinery every WordPress site shares: core software, themes and plugins that need regular updates, a backup that is stored somewhere other than the web server, a security scan and an uptime check that alerts someone when the site goes down. A restaurant needs the same as anyone else, and the difference is timing. You want the updates run when the dining room is quiet, and a backup you know you can restore, taken before the changes.
Compare whatever an agency or freelancer proposes with that yardstick. If the reports you get are only two lines long, ask for more detail on what was updated and what the security check found.
When there is more than one site, or one season
Two situations change the job considerably.
First, seasonal trade. A beach cafe that closes in winter, a ski-lodge restaurant, a place that triples its bookings in December. The site needs a plan for each peak and each quiet period: when to switch on the holiday menu, when to put up a “closed until spring” notice without taking the whole site down, when to run extra checks before bookings surge. A fuller plan for those swings is in our guide to a year-round maintenance calendar for seasonal trade.
Second, several locations. Each branch has its own address, hours, phone number, menu variations and, often, its own booking link. One shared template is easy to look after, but only if the branch details are kept in one place. A single page that lists every site with a short checklist beats a group of near-identical pages where one branch is always out of date. The upkeep side of that setup is covered in multi-location website maintenance.
Who changes what: a simple handover
Restaurants run on the people in them, and people leave. A manager who edited the website quietly for three years moves on, and nobody has the login. To avoid that, write a one-page handover and keep it in a shared drive, not in someone’s head:
- Who may change the menu and hours, and how fast it must happen after a decision is made.
- Who gets the booking and enquiry emails, and who covers when that person is away.
- Where the logins live, and whose name the domain, hosting and booking accounts are registered in. They should be in the business’s name.
- What the maintenance team does without asking (updates, backups, security checks) and what always needs the owner’s approval (changing prices, removing pages, installing something new).
If a team in India looks after the technical side, a time difference can work in your favour for planned jobs, because updates can be scheduled for when your kitchen is shut, if you agree that up front. The cost is that urgent requests need a clear route, so agree in advance how to reach them (WhatsApp or email) and what counts as urgent.
A restaurant website maintenance routine to keep
- Each time the menu changes: update the site, print menu and Google listing together.
- Weekly: test the booking button and the contact form from your own phone.
- Monthly: read the maintenance report; check that a backup exists and updates were applied.
- Quarterly: enter the next three months of closures and special hours; look at the site as a stranger would.
- Yearly: check domain, hosting and certificate renewal, and review who holds a login.
None of this requires technical skill. Good restaurant website upkeep needs only someone who is given the job and told it matters, and one honest look at the site each week. To get an outside view of how your own restaurant site is doing, the quick health check is a fair first step.
Next in this series: Real Estate Website Maintenance: Listings to Leads
