This audit is for a restaurant operator responsible for the owned website path. A menu can be current inside the restaurant and still create friction online. The useful question is not whether one file format is always best. It is whether a diner can reach the right menu, understand what is available at that location and take the next step without losing context.
Start with a five-minute menu path test
- Open the restaurant or location page as a new visitor.
- Find the menu through a descriptive link that works without a scripted click handler.
- Check the menu on a phone at normal zoom. Look for readable item names, descriptions, prices or price context, and dietary or availability notes that matter to the decision.
- Confirm the page identifies the right location and gives the relevant hours or service periods.
- Follow the next action: order, reserve, call or get directions. The destination should retain the restaurant and location context.
Google recommends crawlable links built with an <a> element and an href, plus descriptive anchor text that gives people and Google context. See Google's crawlable-link guidance.
Choose the format by the job it must do
| Format | When it can work | What to audit |
|---|---|---|
| HTML menu page | The menu is an important discovery and decision page that the team can keep current. | Visible item text, headings, location context, internal links, mobile reading and the next action. |
| PDF menu | A designed print-style menu is already part of the operating workflow. | Descriptive links to the file, readable text, mobile usability, version control and a clear path back to the location and next action. |
| Image menu | Photography supports the food and brand presentation. | Do not make the image the only useful source of menu information. Provide accessible, selectable text for the facts diners need. |
| Ordering or menu provider | A provider handles live availability, ordering or reservations. | Keep an owned page that explains the location, menu context and next step, then link clearly to the provider with a usable fallback. |
Google lists both HTML and PDF among the file types it can index, along with common image formats. That does not make any format automatically indexed or higher ranking. HTML is often the more practical editorial choice when a restaurant needs frequent updates, contextual internal links and a mobile reading experience under its own control. A PDF can remain useful when its text, version and phone experience are managed well. An indexable image still does not replace accessible, selectable menu text for diners. See Google's indexable file types.
Keep website and Business Profile controls separate
Your website menu and your Google Business Profile menu are separate surfaces. Google documents controls for a menu URL and for uploading menu photos or a PDF in an eligible Business Profile. It also says menu data from a business website may be transcribed into the profile. Treat that as a possible source, not a promised automatic sync.
Choose one owner for the website menu and one owner for Business Profile checks, even if the same person handles both. After a menu change, verify each surface separately. This guide does not require opening or changing a Business Profile. See Google's menu editor guidance.
Use a compact upkeep checklist
- Location: confirm which restaurant, dining format and service period the menu covers.
- Items and price context: update the details a diner uses to decide, without promising availability that changes faster than the page can be maintained.
- Dietary and service notes: state useful facts clearly and route sensitive questions to a person when needed.
- Next action: test order, reservation, call and direction links for the correct location.
- Fallback: give the guest a usable route when a provider is unavailable or an item is not listed.
- Owner and trigger: name who updates the page and which menu, price, hours, location or provider changes trigger a review.
Make the menu page useful to search systems
Google says pages shown in its AI search features must be indexed and eligible to appear with a snippet, and that the same foundational SEO practices apply. Its guidance calls for crawlable internal links, important content in text and structured data that matches visible text. It does not require a special AI file or special schema, and it does not promise indexing, an AI citation or traffic.
For a restaurant menu page, the practical work is familiar: publish useful visible information, link to it from the relevant location or restaurant page, keep it accessible to crawling, and make the next guest action clear. Review Google's AI features and website guidance.
Write the smallest useful fix brief
- Record the exact restaurant or location and the menu URL a diner should reach.
- Name the current format and the specific friction found in the five-minute test.
- Choose whether to improve the current format, add an HTML summary or rebuild the owned menu page.
- List the facts that must stay current and the person responsible for them.
- Define the next action and its fallback.
- After implementation, verify the public page, internal link, mobile state and destination separately.
A menu-page improvement is a publishing and guest-path decision. It does not prove that a search impression, menu view, reservation or order was caused by the change.