Build a keyword map with one page per query
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and build a keyword map with one page per query.
LLMPrompt
Prompt
Copied 0
Build a keyword map for [https://example.com]. Product: [one sentence on what it does and who buys it]. Competitors: [3 to 8 names, or "find them"]. 1. Write the questions a buyer asks at each stage: unaware of the problem, aware of the problem, comparing kinds of solution, comparing products, and ready to buy. Write them the way a person types them into Google or an AI assistant. Give 5 per stage. 2. Add the search terms for the category, competitor names, "alternative to" and "vs" queries, integrations and use cases. 3. Add my real queries from [Search Console MCP / data/gsc-queries.csv] for the last [3] months. 4. Group the queries by intent. Give each group one main query. 5. Match each group to one existing page. If two pages target one group, flag it and say which page should win. If no page fits, mark it as a gap. 6. Output [seo/keyword-map.csv] with these columns: query, intent, stage, monthly volume, difficulty, target URL, status (live, planned, gap), current position. 7. Leave volume and difficulty empty unless they come from [keyword tool or export]. Never estimate them. 8. List the gaps as a backlog sorted by how close each one is to a buying decision. Wait for my review before you plan any content.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/keyword-map-one-page-per-query - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "keyword-map-one-page-per-query",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}