If your public menu page is missing from search, start with the exact page address, not a general search for your restaurant. Check whether the page opens for a new visitor, inspect its indexing status, and then check the signals and links that help search engines find it. Each result points to a different next step.
A page that opens in your browser can still be blocked from search engines. A page that is indexed may simply not appear for the search you tried. Treat those as separate problems before paying for a redesign or changing the menu URL.
1. Confirm the menu page is public and reachable
Write down the exact menu URL you want guests to find. Copy it from the browser address bar after opening the menu, including the path after your domain. If your site has separate pages for dine-in, takeout and catering, decide which one you are checking first.
Open that address in a private browser window while signed out. Try it on a phone, too. You are looking for a useful menu that loads without a staff login, a broken-page message or a redirect to an unrelated page. Check that guests can read the items and prices, not just see a loading screen.
Then follow the menu link from your home page. Does it lead to the same address? A direct link you saved months ago may point to an old version, while the current navigation points somewhere else. Record the starting address and the final address after any redirect.
A private-window check tells you what a typical visitor sees; it does not prove a search engine can access the same content. If the page fails for you, ask the person who manages the website or hosting to check the page, redirect and server response. Give them the URL, the time of the attempt, the device and a screenshot of the error.
If you do not know who controls the domain or website, locate those contacts before changing settings. The guide to restaurant domain ownership can help you identify the right person to ask. Your website provider may also control access to search tools, even if you own the domain.
2. Inspect indexing and canonical signals
Search for the exact URL as a quick clue, but do not treat a missing result as proof that the page is not indexed. Search results vary, and a search for your restaurant name or a dish may show a different page. For a more useful diagnosis, ask whoever manages Google Search Console to inspect the exact menu URL.
The URL inspection report can show whether Google has indexed the address and may explain why it has not. It can also show the canonical URL: the address Google treats as the preferred version among similar pages. The declared canonical is the version your site indicates; Google may choose a different one. A live test checks the page as it is available now, while the indexed report reflects Google's recorded information. The two can differ after a recent change.
Use this decision tree to choose the next check. The evidence column is what you should save or pass to your website provider, rather than a list of changes to make all at once.
| What you find | Likely next check | Evidence to collect |
|---|---|---|
| Page does not open publicly | Check the URL, redirect and server response with the provider. | Starting and final URLs, error screenshot and time. |
| Page opens, but inspection reports a block or exclusion | Ask about robots rules, a noindex directive or the reported access issue. | Inspection status, live-test result and any reported directive. |
| A different canonical is selected | Compare both pages and decide which address should be the main menu. | Inspected URL, declared canonical and Google-selected canonical. |
| Page is indexed but missing for a particular search | Check the query and whether another useful page appears; review menu content and links. | Search terms, location, date and the page shown, if any. |
A noindex directive asks search engines not to index a page. A robots rule can prevent crawling. These are different controls, so ask the provider to identify the actual issue before changing either one. Removing a restriction from a page that was intentionally private can create a new problem.
A different canonical is not automatically a mistake. If two addresses show essentially the same menu, one preferred address can reduce duplication. The question is whether that preferred page is public, current and useful to guests. If Google selected an old menu or an unrelated page, give both addresses to the provider for review.
3. Check internal links and sitemap inclusion
Search engines need a way to discover pages. Look for a normal, visible menu link in your site's navigation or on a relevant page. Follow it rather than assuming the button is connected correctly. If you offer online ordering, also check whether the ordering link and the menu link lead to the experiences you intend; they may be different pages.
Ask your website provider where the site's XML sitemap is located and whether it includes the preferred menu URL. A sitemap is a list that can help search engines discover URLs; inclusion does not guarantee indexing. Likewise, a page can be discovered through links without appearing in a sitemap. The useful question is whether your links, sitemap and preferred URL point consistently to the page you want found.
Hypothetical example: A restaurant's home page links to /menu, but that address redirects to /order. The sitemap still lists /menu, and the owner wants guests to find a readable menu before they start an order. First, the owner opens both addresses in a private window and notes the final destination. Then the provider can confirm whether a separate public menu page exists and which URL should be linked and listed.
If the ordering page is the intended menu, the owner can check that its content is useful without a login. If a separate menu is intended, the provider can review the navigation, redirect and sitemap together. Neither choice guarantees a search result. The point is to stop sending mixed directions before requesting another inspection.
Also check what the page actually displays on a phone. A menu that depends on an image or a downloadable file may be usable for some guests, but ask your provider how the important menu text is presented to search engines and whether visitors can read it comfortably. Do not delete an existing PDF solely because the HTML page is missing from search; guests may still use it.
4. Request specialist review when the cause is unclear
If the page is public, the inspection report is unclear and the links appear consistent, give your website provider a compact evidence packet. Include the preferred URL, any old or redirected URL, screenshots, the inspection status, canonical details, the sitemap location and the search terms you tried. Note when you last changed the page. This gives a specialist a starting point without requiring them to reconstruct the problem from a vague report that the menu is missing.
Ask these questions in writing:
- Can a search engine access the preferred URL and see the current menu content?
- Is any noindex directive, robots rule, redirect or canonical setting affecting it?
- Do navigation links and the sitemap point to the intended version?
- What change do you recommend, who will make it, and how will we check the result?
After a correction, use the live inspection test to check the current page and request indexing if the tool offers that option. A request is not a promise of inclusion or placement. Record the date, leave the intended URL stable where practical, and revisit the indexed report rather than repeatedly changing several settings at once.
If the page is indexed but does not appear for a particular search, the problem is no longer just access. Check whether the page clearly identifies the restaurant and contains the current menu guests need. A search engine can choose another page or omit yours for a given query even when the page is indexed. Avoid anyone who promises a specific position as the outcome of this checklist.
If your current provider cannot explain who controls these settings, make that a buying question before moving platforms. The restaurant website builder comparison can help frame the wider decision, but keep the missing page and its evidence separate from a general site redesign.
Use the checklist on your current menu URL, then ask Fleksa about a restaurant website and verified US availability if you are considering a change. Bring the evidence packet and ask who would control the domain, menu edits and search-related settings.
Frequently asked questions
Does a missing search result mean my menu is not indexed?
No. A page can be indexed without appearing for a particular query. Inspect the exact URL in Google Search Console and compare that report with the search terms you used.
Should I request indexing before fixing the page?
First address a confirmed access problem, unwanted noindex directive or incorrect redirect. Then use the live test and request indexing if available. A request does not guarantee that the page will be indexed or shown.
Can my ordering page be my searchable menu?
It can be the page you choose to promote, but check that it is public, displays useful menu content and is the address your links and sitemap intend to identify. Ask your provider how search engines access that content.
