Queries such as “family-dinner restaurants in Xinyi” or “cafes near Guishan” used to return a column of blue links. ChatGPT, Perplexity, and Google AI Overview now often answer directly and name about three to five places.
Landing on that short list means AI is sending guests who already intend to visit. In conversations with operators around Taoyuan and Zhongli, many have not yet noticed the shift, which still leaves an opening for restaurants that move first. The notes below explain, from an advisory view, how a dining site can be read and cited by AI.
Restaurant Schema sample
Six required tasks
1. Complete the Google Business Profile
This single asset has the largest effect, and operators skip it most often. The profile is usually where AI starts reading local facts:
- Fill in the name, address, phone, and hours completely
- Upload 10 to 20 clear photos of the exterior, seating, signature dishes, and menu
- Choose accurate categories, such as restaurant, Taiwanese cuisine, or family dining
- Post each week with offers or new dishes
- Reply to reviews, especially critical ones
Many owners assume the profile does nothing. One small Guishan restaurant raised completeness from about 60 percent to full and kept posting once or twice a week; map visibility rose clearly within about three months. The fuller the profile, the more likely AI is to mention the restaurant first.
2. Finish the Restaurant Schema
Use the sample above as the pattern. For how the markup is applied, see a practical guide to structured data. Check these fields first:
servesCuisine: an array of several labels, such as Taiwanese, seafood, and family diningpriceRange: standardized as$,$$,$$$, or$$$$openingHoursSpecification: weekdays and weekends written separatelyacceptsReservations: set totruewhen booking is available
3. Mark up the menu
Describe each dish as a MenuItem:
name: dish namedescription: a short note of about 30 to 50 charactersimage: URL of the dish photooffers.price: pricesuitableForDiet: vegetarian, gluten-free, low-fat, or similar
Whether the menu is published as a web page directly affects how precisely AI can recommend the restaurant.
4. Publish bilingual pages
Restaurants that regularly host international guests should treat this as required:
Translate the menu, introduction, address, and hours in full. After the English pages go live, AI visibility on English queries usually rises sharply.
5. Optimize every photo
Each image should at least have:
- WebP or AVIF format
- A specific alt text, such as “signature soy-braised short rib with seasonal vegetables”
- Modest location metadata (EXIF GPS)
- An ImageObject Schema entry for extra context:
6. Connect reservations
After linking OpenTable, SevenRooms, or inline, add the Schema. For the booking flow, see how to plan a reservation site:
"potentialAction": { "@type": "ReserveAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://example.com/reserve", "actionPlatform": ["http://schema.org/DesktopWebPlatform"] }, "result": { "@type": "FoodEstablishmentReservation", "name": "City Family Table reservation" }}When recommending places, AI tends to prefer restaurants that can be booked online.
A restaurant rollout snapshot
A mid-to-high-priced Taiwanese restaurant in Xinyi rebuilt its site so AI could read it more easily:
Work finished within two months:
- Restaurant Schema and Menu Schema fully in place
- Business profile completed, with weekly posts
- Chinese and English versions launched together
- More than 100 dishes published as web pages, with photos, prices, and descriptions
- OpenTable booking connected
Change after about six months:
| Metric | Before | After |
|---|---|---|
| AI mentions for “Xinyi family dinner” | Not listed | About 12 times per month |
| Organic visits | 1,200 per month | 5,800 per month |
| Online bookings | 18 per month | 95 per month |
| Share of international guests | 8% | 24% |
This is one case only. District, cuisine, and positioning differ, so the same result should not be assumed for every restaurant.
Five mistakes to avoid
- ❌ Menu available only as a PDF: AI cannot see individual dishes
- ❌ Blurry photos: both AI and visitors get a weaker first impression
- ❌ Profile and website facts disagree: AI treats the information as unreliable
- ❌ Google reviews left unanswered: this weakens profile ranking weight
- ❌ Outdated menu prices: once AI quotes them, a mismatch on site badly damages trust
Closing: local search is now decided by AI
Put plainly, “nearby XX” queries are moving from map browsing to direct AI shortlists. Restaurants that prepare early build an advantage, and those that wait are more likely to fade out of the recommended set. For how layout can support AI-readable structure, see page layout in the AI Overviews era.
For a dining site, completing Restaurant Schema and the business profile together is usually the thirty-day effort with the clearest return. Accurate, complete data is what later makes citation by answer engines more likely.