Organize Pages and Navigation

Ask your AI agent to restructure your restaurant site around what customers actually need — finding the menu, reserving a table, and getting directions.

Use this when

Your site has content, but customers cannot quickly find what they came for. Maybe the menu is buried, the reservation link is hard to spot, or there are pages that nobody visits. This playbook helps you reorganize around real customer tasks.

Copy this prompt

Reorganize this Dineway restaurant site around what customers need most. Look at the pages, posts, navigation menus, location content, and calls to action. Propose a simpler structure first, then make only safe draft changes after explaining what will move or change.

What the agent should inspect first

  • All your pages and their current URLs.
  • Blog and news posts — should any be grouped differently or retired?
  • Primary and footer navigation menus.
  • Location pages and city-specific content.
  • Repeated or orphaned content that nobody sees.
  • Reservation, ordering, contact, and map links — do they all work?

What most restaurant sites need

Think about it from your customer’s perspective. They visit your site because they want to:

  • See the menu — this should be one tap from anywhere.
  • Reserve a table or order — the call to action should be obvious.
  • Find your location and hours — address, map, parking, transit.
  • Check out events or private dining — if you offer these.
  • Browse the gallery — photos of food, the space, your team.
  • Read reviews or press — social proof.
  • Catch up on news — seasonal menus, closures, special events.
  • Contact you — phone, email, or a form.

If any of these take more than two clicks, your navigation needs work.

What Dineway tools it may use

The agent may inspect collections, list content, read menus, and suggest navigation changes:

npx dineway content list pages
npx dineway content list posts --limit 50
npx dineway menu get primary

If a command changes content, the agent should tell you whether it reads or writes before running it.

How you review the result

Put yourself in a customer’s shoes and click through the site:

  • Can you find the food menu in one tap?
  • Can you reserve, order, or call without hunting?
  • Are location pages useful — or just thin filler?
  • Did the agent preserve important URLs, or recommend redirects where needed?
  • Does the mobile navigation make sense?

Do not let the agent invent

Do not create doorway pages for neighborhoods you do not actually serve, fake services you do not offer, or navigation links to pages that do not exist yet.