High Priority
Deploy `/restaurant-menu.txt` Protocol
Establish a machine-readable summary of your entire site hierarchy, focusing on menu items, specials, and location details, specifically for AI agents serving diners.
Create a text file at `/restaurant-menu.txt` with a brief intro to your restaurant (cuisine type, ambiance, key selling points).
Include markdown-style links to your most important pages: full menu, online ordering, reservations, location/hours, and catering services.
Add a 'Specials' or 'Daily Offerings' section in the file to answer common AI queries about current promotions directly.
Configure your Restaurants crawler protocols effortlessly.
Join 2,000+ teams scaling with AI.
High Priority
GPTBot Selective Menu Indexing
Fine-tune which sections of your restaurant's website should be ingested by AI crawlers like GPTBot to prioritize accurate menu and booking information.
User-agent: GPTBot Allow: /menu/ Allow: /reservations/ Allow: /specials/ Disallow: /careers/ Disallow: /private-events/
Verify your crawler permissions using an AI bot tester tool (e.g., OpenAI's tool) to ensure correct indexing of dining-related content.
Monitor crawl frequency in your server logs to ensure GPTBot is hitting your menu, booking, and location pages efficiently.
Medium Priority
Semantic HTML for Menu Structure
Use HTML5 landmarks and semantic tags to help LLM scrapers understand the hierarchy and details of your menu items, ingredients, and pricing.
Wrap individual menu items within `<article>` tags to signal their distinct nature.
Use `<section>` with descriptive `aria-label` attributes for different menu categories (e.g., 'Appetizers', 'Entrees', 'Desserts', 'Beverages').
Ensure all menu item details (description, ingredients, price) are clearly tagged using appropriate elements like `<p>`, `<span>`, and `<strong>`, with prices specifically marked for easy extraction.
High Priority
RAG-Friendly Dish Descriptions
Structure your menu item descriptions and specials so they can be easily 'Chucked' and retrieved by RAG (Retrieval-Augmented Generation) pipelines for AI-powered recommendations.
Keep related dish concepts and key ingredients within concise descriptions (ideally under 150 words per item).
Avoid ambiguous culinary terms; clearly state primary ingredients and preparation methods.
Eliminate vague adjectives; use specific flavor profiles (e.g., 'zesty lemon aioli' instead of 'creamy sauce') and dietary information (e.g., 'vegan', 'gluten-free').
