When a menu URL changes, keep the old address useful by sending visitors to the closest relevant new page. Start with a list of old addresses, map each one to a destination, and ask whoever controls the website or server to set up permanent redirects. Then test the old links and update links you control.
The goal is simple: a guest who opens an old lunch-menu link should reach the current lunch menu, not a generic homepage or an error. A redirect can also help search engines understand that a page has moved, but it does not guarantee a particular ranking.
Find the menu links people may still use
Start with the menu pages that are changing, including addresses for individual menus, ordering categories, downloadable menus, and seasonal pages. Copy the full address for each one. Keep the version with and without a trailing slash, or with different capitalization, if those addresses have been used separately.
Check the current restaurant website navigation, footer, homepage buttons, and ordering links. Search your email campaigns, social profiles, local listings, printed QR codes, and any saved promotional materials for links that point directly to a menu. A link on a printed table card may be harder to replace than a link in your own website footer, so note where each address appears.
Backlinks are links from other websites. You may find some in a search performance tool or website analytics account, or by asking your web provider for a report. You do not need a complete backlink inventory to start. Record useful links you can find and prioritize pages that guests are likely to reach from them.
Different people may hold different pieces of the list. The owner or marketing manager can supply campaign links and printed materials. The website provider can identify current addresses and explain where redirects are managed. A staff member who updates menus can confirm which new pages will actually exist. Assign one person to combine the answers and approve the map.
Also check who controls the domain and the current hosting or website account. Domain ownership alone does not necessarily give you access to redirect settings. If an ordering page lives on a separate domain, ask that provider how its old links can be handled. The domain ownership guide is useful when those responsibilities are unclear.
Map each old address to the closest useful page
Make one row per old URL. Include the full old address, its intended destination, the reason for the choice, and the person responsible for setup and verification. The destination should be a working final page, not another old address that needs a second redirect.
Hypothetical example: A restaurant is replacing several menu pages with a smaller set of current pages. The addresses below are examples, not live links. The table shows how its owner could make and explain each decision.
| Old URL | New destination | Decision | Owner and check |
|---|---|---|---|
| example.com/lunch-menu | example.com/menu/lunch | Same meal and current menu | Web provider sets redirect; manager checks lunch items |
| example.com/drinks | example.com/menu/drinks | Closest matching category | Web provider sets redirect; manager checks mobile page |
| example.com/summer-menu | example.com/menu | Seasonal page retired; current menu is the nearest useful page | Manager approves; web provider tests destination |
| example.com/order/pickup | Current pickup ordering page | Preserve pickup intent; confirm the final address with the ordering provider | Ordering provider confirms destination and setup |
The seasonal row is a compromise. A current menu may help a guest more than a dead page, but it should not pretend that last summer's dishes are still available. If there is no reasonably related destination, discuss whether the old address should return a clear not-found or gone response instead. Sending every retired page to the homepage can leave guests confused.
For permanent moves, ask for a permanent redirect, commonly an HTTP 301. A temporary redirect may be appropriate when the original page is expected to return. Ask the provider which response it will use and how you can verify it. Avoid redirect chains where an old lunch page points to an intermediate page before reaching the current menu; they add another point of failure.
Pay particular attention to ordering intent. A guest following a pickup link should not land on a page that only describes the restaurant. Confirm that the destination opens the right ordering flow and shows the current menu. If your online ordering uses a different provider or domain, clarify which company controls the old address before promising that a redirect can be installed.
Test redirects and update links you control
Before release, agree on who will install the redirects and who will check them. Ask whether the provider offers a staging area or another safe way to preview the rules. A preview may not behave exactly like the live domain, so plan a separate check after release.
For each row, open the old address and confirm that it lands on the intended final page. Check the page itself, not just the address bar: Is it the right meal or ordering category? Is the menu readable on a phone? Does a guest have an obvious next step? Check a sample on both a mobile device and a desktop browser, and test every high-priority old URL.
Use a redirect checker or your browser's developer tools to inspect the response when possible. Confirm the expected permanent or temporary status and look for extra hops or loops. If you cannot inspect the response yourself, ask the provider for the result. A page that appears to load is useful evidence, but it does not by itself show which redirect response was sent.
For an ordering destination, run a simulated check only: open the old link, reach the intended menu, and stop before any action that could submit an order, charge a card, notify a guest, or dispatch a courier. Ask the provider how to use a safe test environment if you need to check later steps. A live service pilot is different and should be planned separately with the people operating it.
Redirects are a fallback, not a reason to leave old links everywhere. Change your own navigation, footer, ordering buttons, social profiles, and editable campaign links to the final URLs. Replace printed QR codes when practical; until then, test that the old QR destination still works. For links on other sites, request an update when you can, but keep the redirect in place for visitors using older materials.
Monitor errors and maintain the map
After release, repeat the checks on the live addresses. Record the date, result, and any fix next to each row in your working copy of the map. If a link fails, identify whether the problem is the redirect rule, the destination page, or a link that was copied incorrectly. Give the responsible provider the exact old URL and the result you saw.
Watch available website analytics, search performance reports, and server or provider error logs for requests to missing menu pages. Ask staff to pass along reports from guests who cannot open a menu. A report may show only part of the picture, so use several sources where available rather than assuming a quiet dashboard means every link works.
Prioritize an old ordering link or a QR code still in circulation over an obscure address with no known use. When you find a missed URL, add a row, select the closest useful destination, assign an owner, and test the fix. Revisit the map when a seasonal menu returns or an ordering provider changes its page structure.
Keep useful permanent redirects in place rather than removing them immediately after launch. Ask your provider about any limits on the number or duration of rules and who maintains them if your website service changes. Redirects reduce friction, but they cannot prevent every broken link, especially when another provider controls the old address.
Use the table as a checklist for your current menu setup. Then ask Fleksa about its restaurant website, including redirect responsibilities and verified US availability for your setup.
Frequently asked questions
Should every old menu URL redirect to the homepage?
No. Send each address to the closest relevant current page when one exists. If there is no useful match, discuss a clear not-found or gone response with your provider.
Do I still need to update a link if it redirects?
Yes, when you control it. A direct link to the final page avoids an unnecessary hop. Keep the redirect for old bookmarks, printed codes, and links you cannot update.
Can a redirect preserve my search ranking?
A permanent redirect helps indicate that a page has moved, but rankings are not guaranteed. Check that the destination is relevant and monitor available search reports after the change.
