When an old menu or location link no longer works, show a page that says the requested page is unavailable and gives guests a few reliable ways forward. Start with the current menu, locations and contact information. If you accept direct orders, include an ordering link too.
A useful 404 page is a fallback for paths you do not recognize or cannot serve. It does not replace redirects: when you know an old address has moved to a specific new page, send visitors to that relevant page instead. The goal in both cases is to help a guest finish the task that brought them to your site.
Tell guests what happened and give them a next step
A 404 page appears when the requested page cannot be found. The message does not need to explain servers or blame the visitor for typing the address incorrectly. An old link on a search result, social post or printed flyer may be the reason they arrived.
Use a short heading such as “We couldn’t find that page,” followed by a sentence that offers help: “The page may have moved or is no longer available. Choose an option below to find what you need.” Keep the restaurant name visible so visitors know they have not landed on an unrelated site.
Put the most useful choices immediately below the message. A guest following an outdated menu link probably wants food information; someone following a former location link may need an address or phone number. A homepage link is useful as a backup, but it should not be the only escape route.
The owner or manager should decide which guest tasks matter most and confirm the current destinations. The person who maintains the site should implement the page and check how the server responds to missing addresses. Staff who answer calls can flag recurring questions, such as guests asking for a menu that has moved. One person should own the final link list and keep it current.
Also ask the site provider whether a genuinely missing address returns an HTTP 404 status. A page can display an error message while returning a successful status, which makes missing-page reports harder to interpret. The guest-facing message and the technical response both need attention.
Choose links that solve the likely problem
Keep the link set small enough to scan on a phone. Use descriptive labels rather than several buttons that all say “Learn more.” The right destinations depend on how your restaurant operates.
- View the menu: Send guests to the current menu page, not an outdated file or a page that only says a menu is coming soon.
- Find a location: Use a current location list if you have several restaurants. For one location, link to its address, hours and other practical details.
- Contact us: Link to the page with the best current way to reach the restaurant. If a phone number is shown on the 404 page, keep it current too.
- Order online: Include this only if guests can actually start an order at the destination. Make the label clear so someone looking for a menu is not surprised by an ordering flow.
- Go to the homepage: Offer this as a general fallback, after the more specific choices.
The following is a hypothetical example. A two-location restaurant has replaced an old lunch menu and closed one of its locations. Its 404 page could use this link set:
| Link label | Destination | Guest task |
|---|---|---|
| View our current menu | Current menu page | Find food and prices |
| Find our open location | Current location page | Check address and hours |
| Contact the restaurant | Current contact page | Ask a question |
| Start an order | Current ordering entry page | Begin a pickup or delivery order if offered |
This table describes destinations, not suggested URLs. The manager should supply the actual addresses and confirm that each page reflects current operations. If ordering is paused, remove or update the ordering choice rather than sending guests to a dead end.
The old lunch-menu address deserves a separate decision. If there is a current menu that reasonably replaces it, set up a redirect to that menu. For the closed location, redirect to a relevant closure or current-location page only if it accurately explains the change. An unknown address should still receive the useful 404 page. Avoid sending every missing path to the homepage; that hides the problem and can make guests think they found what they requested.
If you are changing platforms, decide who can edit these destinations and redirects before launch. A restaurant website builder comparison can help frame the wider platform decision; the immediate question is whether your team can keep this small set of links accurate.
Make the page easy to use on a phone
Many guests will reach a broken link while deciding where to eat or trying to find your door. Put the explanation and primary links near the top, without a large decorative image pushing them down the screen. Use readable text, clear contrast and enough space between links to tap one without hitting another.
Check the page at a narrow mobile width and on a phone if one is available. Read it without zooming, then enlarge the text and see whether the message and links remain usable. Try keyboard navigation as well: the focus indicator should be visible, and the link order should make sense. Link text should identify the destination even when read on its own.
For a practical simulation, enter a made-up path on the restaurant’s domain that you have confirmed is not a real page. Check that the 404 message appears, then follow the menu, location and contact links. If there is an ordering link, stop after confirming it reaches the intended ordering entry page. Do not place an order, make a payment, send a guest message or dispatch a courier as part of this practice check.
Repeat the check for a known old menu URL that should redirect. It should lead to the intended replacement, not the general 404 page. Then check an unknown path separately. A successful simulation shows what happened for those addresses and devices at that time; it does not prove every old link or phone will behave the same way.
If you use online ordering, confirm who can update the entry link when the ordering setup changes. A working link that leads to the wrong location or an unavailable ordering flow is not much help to a guest.
Review recurring errors and keep a short checklist
Ask whoever maintains your site what missing-page information is available. Depending on the setup, it may come from server logs, a website tool or another reporting system. Agree on a regular review and a way to record the path, where visitors appeared to come from when available, the likely task and the action taken. Avoid collecting more personal information than you need for troubleshooting.
Look for patterns rather than reacting to every unusual address. Repeated visits to a former catering menu may justify a redirect to its current replacement. A broken link from your own homepage should be corrected at its source. A one-off unknown path with no clear replacement can continue to use the 404 page. If you are unsure what a path once contained, investigate before redirecting it somewhere unrelated.
Use this checklist when setting up the page and during each review:
- Message: Does the page clearly say the requested page is unavailable and identify the restaurant?
- Destinations: Do the menu, location, contact and any ordering links lead to current, useful pages?
- Mobile and access: Can a guest read and select each link on a small screen and navigate with a keyboard?
- Response: Does an unknown path show the custom page and return a 404 status?
- Known moves: Do old addresses with relevant replacements redirect to those replacements?
- Ownership: Who updates the link set, reviews recurring errors and confirms fixes?
Keep a small record of changes so the next person knows why an old address redirects. Domain access matters here: confirm who controls it and who can make website changes. The domain ownership guide covers questions to ask before a handoff.
Use the checklist on your current setup, then ask Fleksa about a restaurant website, including whether the features and setup you need are available in the US.
Frequently asked questions
Should every broken URL redirect to the homepage?
No. Redirect a known old URL to a relevant replacement when one exists. For an unknown or genuinely missing path, show a useful 404 page with clear choices.
What if the restaurant has several locations?
Link to a current location list so guests can choose the right restaurant. Check that each location’s address, hours and contact details are maintained.
How often should we check the 404 page?
Choose a regular review that fits your team, and check it after menu, location, domain or website changes. Also review recurring missing paths and fix broken links you control.
