Images, Schema, and Agent Ready

Audit your restaurant media, add JSON-LD structured data, and run the Agent Ready scanner — so search engines, answer engines, and AI agents understand your site.

Use this when

You want search engines and AI tools to understand your restaurant site better. This playbook covers three connected tasks: making your images more useful, adding structured data (schema), and checking how ready your site is for AI agents.

Part 1: Audit and improve your images

Real photos of your food, venue, and team are one of the strongest signals a restaurant site can have. But photos only help if they have good filenames, useful alt text, and proper captions.

Copy this prompt

Use dineway-seo-images to audit media on this restaurant site. Check filenames, alt text, captions, hero images, and OG images. Replace only placeholders, never real restaurant photos. Apply changes as drafts and flag anything that needs my review.

What the agent should inspect first

  • All images in the Dineway media library.
  • Images used on the homepage, menu, gallery, and blog posts.
  • OG (social sharing) images — what does the site look like when shared on Instagram or WhatsApp?
  • Hero images — are they real photos or generic placeholders?
  • Filenames — IMG_4832.jpg tells search engines nothing.

How you review image changes

Ask the agent for a summary table:

  • Old filename → new filename.
  • Updated alt text and captions.
  • Which images were flagged as placeholders or AI-generated.
  • Which pages use each image.

Check that alt text is honest and specific. “Handmade pappardelle with wild boar ragù” is good. “Delicious Italian food” is not.

Part 2: Add structured data (JSON-LD schema)

Structured data helps Google, Bing, and answer engines display rich information about your restaurant directly in search results — things like your hours, address, menu, rating, and price range.

Copy this prompt

Use dineway-seo-schema and the Agent Ready scanner to audit this restaurant site. Compare schema to visible page facts, list missing facts, and propose safe draft changes. Do not invent ratings, reviews, hours, coordinates, prices, images, or availability.

What schema is useful for restaurants

Not every schema type matters. For most restaurant sites, focus on:

  • Restaurant or LocalBusiness — your name, address, hours, phone, price range.
  • WebSite and WebPage — helps search engines understand your site structure.
  • BreadcrumbList — makes your search results show the navigation path.
  • Menu — only when your menu facts are verified and current.
  • ImageObject — for real photos with proper metadata.
  • Article — for blog and news posts.

How you review schema changes

Ask the agent for:

  • What schema was added or changed and on which pages.
  • Whether every fact in the schema matches what visitors can actually see on the page.
  • Whether any required fields are filled with guesses instead of facts.

The golden rule: if a visitor cannot see the fact on the page, it should not be in the schema.

Part 3: Run an Agent Ready check

The Agent Ready scanner checks whether your restaurant site is easy for AI agents to work with. It looks at things like robots.txt, sitemap, schemamap, link headers, content signals, and protocol support.

Copy this prompt

Run an Agent Ready scan on this restaurant site. Show me the results, explain any failures in plain language, and suggest fixes I can apply as drafts. Do not add protocols or features we do not actually support.

How you review Agent Ready results

The scanner groups checks into categories. For each failed check, ask:

  • Is this something we should fix now, or is it fine for later?
  • Does fixing it require a code change, a config change, or just adding a file?
  • Will it break anything?

Do not let the agent invent

This applies to all three parts:

  • Do not use AI-generated images as if they were real food, room, or staff photos.
  • Structured data must match visible facts. No fake review ratings, fake hours, made-up prices, or invented coordinates.
  • Do not claim Agent Ready protocols you do not actually implement.