Review and Improve

Review your first Dineway restaurant site like an operator, then use prompt-driven iteration to make it genuinely useful for customers.

Use this when

Your first site exists — the agent built it, it runs locally, and you can see the pages. Now you need to check whether it is accurate, well-organized, and ready for real customers. After the review, you will want to improve the weak spots.

This page covers both steps because they naturally flow together: review first, then improve.

Part 1: Review the first version

Copy this prompt

Review this Dineway restaurant site as an owner. Check accuracy, navigation, mobile layout, content structure, SEO metadata, media, and missing facts. Do not guess at fixes. Return a prioritized list with three categories: safe draft changes you can make now, changes that need my approval, and questions only I can answer.

What the agent should inspect

  • Homepage, menu, reservations, location, contact, gallery, reviews, blog/news, and legal pages.
  • Primary and footer navigation — can a customer get where they need in one or two taps?
  • CMS collections and whether content is draft or published.
  • Media quality, alt text, and captions.
  • SEO metadata and structured data — are the facts actually true?
  • Mobile rendering — does anything overflow or look broken on a phone?
  • Agent Ready scan results if you have run one.

What to fix first

Go in this order — the top items can lose you customers if they are wrong:

  1. Wrong phone number, address, hours, reservation link, or delivery details.
  2. Invented claims — dishes that do not exist, fake awards, made-up reviews.
  3. Confusing navigation — customers cannot find the menu or how to reserve.
  4. Weak homepage — it sounds generic instead of sounding like your restaurant.
  5. Missing local SEO — page titles do not mention your restaurant or city.
  6. Missing image alt text — hurts accessibility and search.
  7. Content that should be draft but is published.

Part 2: Improve the site

Once the review is done, you will have a list of improvements. Some are quick fixes; others need a focused session.

Copy this prompt

Improve this Dineway restaurant site for real customers. Start from the review findings. Apply safe changes as drafts, explain anything that needs my approval, and do not invent menu items, prices, awards, ratings, hours, or reviews.

What the agent should inspect first

  • The review findings from Part 1.
  • The homepage and most important customer paths.
  • Calls to action — do they point to the right reservation, ordering, or contact page?
  • Media quality — are there placeholder images that should be replaced with real photos?
  • SEO metadata — anything the review flagged as missing or inaccurate.

What Dineway tools it may use

  • Restaurant-site and frontend-design skills for layout and copy improvements.
  • CLI commands to list content, menus, and media.
  • Browser QA to check layout and interactions.
  • MCP if connected, for draft content updates.

How you review the result

Ask the agent for:

  • A before/after summary of what changed.
  • The actual files or content items it modified.
  • Screenshots of key pages (desktop and mobile).
  • Validation output — did it run lint, typecheck, or build checks?
  • A list of anything it left untouched because it needs your approval.

Do not let the agent invent

This is the most important rule for restaurant sites. Do not allow:

  • Invented dishes, specials, or tasting menus.
  • Made-up chef bios or staff descriptions.
  • Fake press quotes or customer reviews.
  • Claims about delivery, private dining capacity, or dietary options that you have not confirmed.
  • Prices, awards, or ratings that are not verified.

If a fact is missing, it should become a question for you — not filler copy on the site.