This audit is for an owner or marketing lead responsible for one restaurant or a group of locations. Its job is to produce a one-location evidence worksheet and find the first broken or unclear handoff in the local discovery path. The restaurant growth page explains Pandorium's commercial approach; the menu audit goes deeper on menu formats; and the direction requests guide explains one measurement boundary. This page is the operator's triage method that connects those jobs without assuming more pages, more schema or more profile activity is always the answer.
Start with one location and one guest action
Choose a real location and the decision you want a nearby guest to make: view the menu, call, get directions, reserve or order. Then run the audit as a new visitor. For a multi-location group, repeat it for each location instead of assuming the brand-level result applies everywhere.
- Find the location through a search that reflects the cuisine, neighbourhood or dining need.
- Check whether the result identifies the correct location and presents current decision facts.
- Open the owned website page and confirm that the location context survives the handoff.
- Follow the intended menu, directions, reservation, order or call route without completing a real transaction.
- Record the first point where the location, offer or next action becomes unclear.
Create the one-location evidence worksheet
Use pass only when the current public evidence is clear, fail when a verified mismatch or broken path exists, and unknown when the source cannot establish the answer. Unknown is a research task, not a failed score and not permission to fill the gap with an assumption.
Swipe sideways or focus the worksheet and use the arrow keys to see every column.
| Check | State | Proof to record | Owner and next fix |
|---|---|---|---|
| Local result facts | Pass / fail / unknown | Dated result or profile URL plus the visible name, category, address and hours. | Person who controls the source; correct a verified mismatch before other optimization. |
| Location-page handoff | Pass / fail / unknown | Exact landing URL and the location cues visible without opening another page. | Website owner; give the real location a useful destination or repair the incoming link. |
| Menu path | Pass / fail / unknown | Menu URL, format, location label, mobile reading result and last verified date. | Menu owner; correct the specific readability, version or context gap. |
| Primary guest action | Pass / fail / unknown | Action label, destination URL, retained location and safe no-send test result. | Journey owner; fix a wrong or broken destination before adding another CTA. |
| Outcome definition | Pass / fail / unknown | Named source, metric, date range, timezone and what the metric does not prove. | Reporting owner; separate visibility, interaction and business-outcome evidence. |
Use stop, fix, plan and hold decisions
- Stop: a result sends guests to the wrong location, publishes a materially wrong core fact or reaches an unsafe destination. Preserve evidence and correct that route before expanding the work.
- Fix now: the intended location is clear but a current link, mobile menu or primary action is broken or loses context.
- Plan: the path works, but the location page lacks useful decision facts, crawlable internal links or accurate structured data. Scope the content and owner before implementation.
- Hold: evidence is unknown, the restaurant cannot maintain the proposed detail, or the business outcome cannot yet be read. Name the missing proof instead of treating the gap as a failed ranking.
Only move to another location after the first worksheet has an owner and next action. A repeated issue can become a shared standard; a one-location issue should not automatically trigger sitewide page production.
Walk through one illustrative location
Suppose a guest searches for dinner near a neighbourhood and finds the correct restaurant, but the result links to a brand homepage. The homepage lists two locations, the menu button opens a generic provider page and the reservation link does not state which restaurant it serves. A brand-level route can be valid when the location choice stays clear, so the extra step is observed friction rather than an automatic failure. This is an example of the method, not a client result.
- Mark the visible profile facts pass only where they match a current authoritative source. Leave uncertain service options unknown.
- Mark the location-page handoff unknown until the full path is tested. Mark it fail only if the chosen location is lost, the route reaches the wrong restaurant or the intended task cannot be completed clearly.
- Mark the menu and reservation routes unknown until their destination context can be verified without completing a transaction.
- If the handoff fails, choose one first fix: route the result or location selector to the correct owned location page, then keep that location in the menu and action labels. If the path passes, retain it and record the extra step as a lower-priority usability observation.
- Define separate checks: public route correctness, landing-page sessions and any reservation or order record from its actual system. Do not combine them into one conversion claim.
The worksheet now contains a reproducible problem, the proof behind it, an owner and a bounded next fix. “Improve local SEO” does not.
Check the facts guests see first
Google says local results are mainly based on relevance, distance and prominence. Complete and accurate Business Profile information can help Google understand the business and match it to relevant searches, while distance depends on the searcher and cannot be edited into a guaranteed ranking. Review Google's local ranking guidance.
For the chosen location, compare the visible name, category, address, phone, hours, service options, menu link and next action with the facts on the owned location page. Treat a mismatch as a publishing problem to resolve at the correct source. Do not invent a location, service or availability detail to make a page look more complete.
Give each real location a useful owned page
A location page should answer the questions that change the guest's decision at that restaurant. Useful details can include the address and access notes, service periods, dining or pickup options, location-specific menu context, contact route and the next action. A repeated city-name template does not become useful merely because it has a unique URL.
Link the page through normal crawlable navigation or contextual links. Make the anchor text describe the destination. Google recommends links that use an <a> element with an href and gives people and search systems context through the surrounding words. See Google's crawlable-link guidance.
Keep the menu and action attached to the location
The location page does not need to duplicate the complete menu, but it should make the correct menu route obvious and preserve the guest's context. The menu-specific audit covers HTML, PDF, image and provider formats. Then test the next action separately: a clear click proves that the route is usable, not that a reservation, order or visit happened.
Use structured data to describe visible facts
Google's local business documentation recommends the most specific applicable subtype, such as Restaurant, and says each business location should be defined as its own local business. The markup should describe facts that are visible and true for the page. Structured data can help Google understand the page and support eligibility for search features; it does not guarantee a rich result or ranking. Review Google's LocalBusiness structured data guidance.
Audit the location name, address, URL, telephone, hours, menu URL, cuisine and other applicable fields against the visible page. Remove unsupported values rather than using schema as a second, conflicting database.
Make the page useful in search and AI experiences
Google's guidance for generative AI features keeps the same SEO foundation: a clear technical structure and unique, useful, people-first content. It says a special AI file, special markup or a particular page length is not required for Google Search. For a restaurant location, the useful work is to publish accurate facts, answer real guest questions and connect them to an actionable page. See Google's generative AI optimization guide.
This can make a page easier to retrieve and use, but it does not promise indexing, a ranking, an AI citation or a guest action.
Separate discovery signals from business outcomes
Use one measurement line for each stage instead of turning all activity into “customers.” A practical review can label:
- Search visibility: query, page, impression and click evidence from the named search property and date range.
- Profile actions: the exact action reported by the profile or campaign, such as a direction request or call click.
- Owned-page use: landing sessions and meaningful page interactions on the correct hostname and location path.
- Business outcomes: reservations, orders, visits or revenue from the system that actually records them.
The direction-requests measurement guide shows why the definitions matter. A change in one stage is a signal to investigate the next stage, not automatic proof that the whole path produced revenue.
Turn the audit into a small implementation brief
- Name the location and the one guest action being improved.
- Capture the exact mismatch or friction with its source URL.
- Choose the smallest useful change: correct a fact, improve the location page, repair a link or clarify the action.
- Name the owner of each fact and the event that should trigger a review.
- Define the technical check and the business metric separately.
- After implementation, verify the public page and destination before interpreting performance.
For a restaurant group, shared standards help, but each real location still needs its own evidence. Audit one location first, learn from the fix, then repeat the method where the same gap is actually present.