The restaurant's menu was available as readable HTML, and the homepage referenced two Google Analytics measurement IDs. Those observations suggest specific checks, but neither establishes that the menu is invisible to search or that visits are counted twice.
For a restaurant owner, the practical questions are whether guests can find current information, complete a reservation or order, and whether the available reports describe those actions accurately.
Keep the menu readable and current
The reviewed menu listed dishes and descriptions as text rather than an image or PDF. That is the right foundation: people can read it, and systems that retrieve the HTML can access the words.
We did not detect JSON-LD structured data in the pages inspected. Appropriate markup can make business details more explicit, but its absence does not make the menu unreadable. Search systems can interpret ordinary page content. Google describes structured data as a way to provide information about a page and classify its content; eligible features have their own requirements. Google's structured-data guidance
A review should check that hours, menu links, cuisine information, and the business identity are accurate and consistent. Add supported markup where it describes the actual page. Menu vocabulary alone does not promise a special search display or an AI citation.
Verify what the two measurement IDs do
Two IDs identify two data streams. They do not tell an outside reader whether those streams belong to separate properties, whether both tags fire, or whether the arrangement is intentional.
The next step is to inspect the configuration with the person responsible for the accounts. Confirm the intended destinations, events, access, and consent behavior. A browser debugging session shows which requests occur; account access is needed to understand the receiving setup. Google's explanation of data streams
Do not delete an ID solely because there are two. If both are needed, document why. If one is obsolete, remove it through a controlled change and verify the remaining collection.
Check the route to a reservation or order
The site handed online ordering to an external platform. That is a common integration pattern, not evidence that the restaurant has lost ownership of its customer information.
Before changing providers, review the actual agreement and export options. Ask which records can be exported, who controls the domain, what happens when service ends, and whether completed orders or reservations can be connected to website reporting.
For the website itself, test the menu, phone link, reservation link, and ordering handoff on a phone. Report a completed reservation only if the booking system makes that completion available; a click to another site is a different measure.
Review headings and summaries in context
The homepage used multiple top-level headings and lacked a meta description that described the page. One heading hierarchy, top to bottom, helps readers navigate, including people using assistive technology. The heading count alone does not establish a ranking problem.
A descriptive summary gives search systems another source for a snippet, but Google may select different page text. Write it for the page's purpose rather than expecting verbatim use. Google's snippet guidance
Method and limits
This was a public-file and page review of an anonymized restaurant, not a client engagement. We did not access analytics accounts, contracts, booking records, or internal systems. The observations describe the inspection at that time, not the site's current configuration or financial results.
Use the Tracking Health Check to identify references on your own site, then verify their behavior. For a review of the setup, see analytics and lead tracking.