Local SEO and Content Planning

Strengthen individual pages for local search and plan groups of related pages — without creating thin doorway content or fake neighborhoods.

Use this when

You want your restaurant to show up when someone nearby searches for what you serve, like “best Italian restaurant Toronto” or “private dining Brooklyn.” This playbook covers two connected tasks: making individual pages stronger for local search, and planning groups of related pages that reinforce each other.

Copy this prompt

Use dineway-seo-content-brief to audit and improve SEO for this restaurant page. Compare with competitive local search results, use only verified facts about this restaurant, and apply changes as drafts. Do not fabricate food items, awards, reviews, neighborhoods served, or dietary claims.

What the agent should inspect first

  • The page you want to improve — its title, description, headings, and body content.
  • Competitive pages ranking for similar terms in your city.
  • Dineway site context and brand voice if recorded.
  • SEO metadata fields and structured data.
  • Any review themes or verified facts from the Google Business Profile.

What Dineway tools it may use

npx dineway seo content-brief "private dining toronto" --url /private-dining --json
npx dineway seo dataforseo serp "italian restaurant toronto" --limit 10 --json

The agent may also use browser QA to compare your page against top-ranking competitors.

How you review the result

Ask for the brief itself, not just the changes. A good brief includes:

  • Primary and secondary target phrases.
  • Recommended title tag and description.
  • Missing or weak content sections.
  • Competitor comparison — what are they covering that you are not?
  • Questions the agent could not answer without your input.

Sometimes one page is not enough. If your restaurant does private dining, catering, and events, those might each need their own page — and those pages should link to each other. This is called a topic cluster: a hub page linked to several spoke pages that share a theme.

Copy this prompt

Use the dineway-seo-cluster skill to plan a local topic cluster for this restaurant. Identify realistic hub and spoke pages, group by real search intent, and avoid thin or duplicate pages. Use keyword data if available.

What the agent should inspect first

  • Your existing pages and blog posts — are some already covering related topics?
  • Keyword research data from Dineway SEO tools.
  • Local search intent — what are people actually searching for in your city?
  • Competitor site structures — do the top restaurants in your area have similar content groups?

What Dineway tools it may use

npx dineway seo dataforseo keywords "private dining brooklyn" --limit 25 --json
npx dineway seo firecrawl search "best [cuisine] [city]" --limit 10 --json

How you review the result

Ask for a visual overview of the cluster — a simple list is fine:

  • Hub page: what is it, does it already exist?
  • Spoke pages: what topics do they cover, how many are realistic?
  • Internal links: which pages link to which?
  • Are there pages that overlap or compete with each other?
  • Is each page genuinely useful, or just filling a keyword gap?

A smaller useful cluster is much better than a large thin one.

Do not let the agent invent

This is critical for local SEO. Do not allow:

  • Doorway pages for neighborhoods you do not serve.
  • Fake service pages for things you do not offer.
  • Blog posts with no distinct value — just targeting a keyword.
  • Claims about awards, press, or accolades that are not verified.

If a fact is not in Dineway, your source material, or a public record, it should not become visible copy.