Industry Guide
Restaurant
Restaurant visibility depends on menu clarity, hours, cuisine, reviews, reservations, and delivery or order actions.
Restaurant prompts are often local, time-sensitive, and attribute-rich. Assistants need to know cuisine, hours, menu, price, dietary options, atmosphere, location, and whether the user can reserve or order.
High-value prompts
- "Italian restaurant near me open late"
- "best brunch with patio in Capitol Hill"
- "vegan dinner near Golden Gate Park"
- "restaurant for six tonight with reservations"
- "does [restaurant name] have gluten-free options"
Priority facts to publish
| Fact | Why it matters |
|---|---|
| Cuisine and menu | Primary category and dietary matching. |
| Hours and special hours | "Open now" and holiday prompts are high-risk. |
| Reservation/order links | Converts answer into action. |
| Amenities | Patio, private dining, wheelchair access, parking, kid-friendly. |
| Reviews and press | High-impact authority support. |
Recommended schema
Use Restaurant, Menu, MenuItem, OpeningHoursSpecification, AggregateRating only where policy-compliant, ReserveAction, and OrderAction where accurate.
Fast fixes
- Publish a crawlable HTML menu, not only a PDF or third-party iframe.
- Add dietary, atmosphere, and amenity facts in visible text.
- Keep reservation, order, and delivery links location-specific.
- Sync Google, Apple, Bing, Yelp, TripAdvisor, OpenTable, Resy, DoorDash, Uber Eats, and Toast data where relevant.
- Run holiday-hours and open-now freshness checks before major holidays.
Check restaurant intent prompts
Test cuisine, dietary, open-now, reservation, delivery, and atmosphere prompts.
Run scan