Build a Keyword Map You Can Actually Action

You are an SEO strategist helping an Australian small business decide what to write and optimise for.

<context>
Business and main services: [BUSINESS: e.g. Marloo Mobile Dog Grooming]
Area served: [AREA: e.g. inner-north Brisbane suburbs]
How customers describe what they want, in their words: [SEEDS: e.g. 'dog wash near me', 'nervous dog groomer', 'puppy first groom']
Pages the site already has: [PAGES: e.g. home, about, contact — no service pages]
A competitor or two, if known: [RIVALS: e.g. two local grooming salons — or 'none']
</context>

Before clustering, sort the seeds by what the searcher actually wants — ready to book, comparing options, or just learning — because that split decides which page answers each one. Note the intents you see, and flag any seed that's really two different searches bundled into one.

<task>
1. Expand my seeds into a broader candidate list, grouped by the language real customers use — include Australian phrasing and spelling, and 'near me' or suburb variants where they fit.
2. Cluster the candidates into topics, and within each topic tag the intent (ready to buy, comparing, learning).
3. Map each cluster to a page: an existing page to optimise, or a new page to create — and name the page.
4. Check that no two pages are chasing the same cluster — if they are, say which page should own it, so my own pages don't compete against each other in search.
5. Put the clusters in a suggested order of attack, based on how close they sit to a booking and how much new content each needs — not on traffic figures.
6. State plainly that you cannot see real search volumes or keyword difficulty from here, and tell me which tool to check them in (Google Keyword Planner, or a tool like Ubersuggest) before I commit.
</task>

<output_format>
Sections: INTENTS I SEE, KEYWORD CLUSTERS (each with its intent tag and member terms), PAGE MAP, ORDER OF ATTACK, VERIFY BEFORE YOU COMMIT. No invented search volumes, difficulty scores or rankings — those come from a tool, not from you. Plain text, no tables. Australian English spelling.
</output_format>

Copy the block above straight into Claude — anything in [BRACKETS] is yours to fill in.