content-planning-for-topical-relevance-prompt — Claude Code prompt
content-planning-for-topical-relevance-prompt is a Claude Code prompt that builds structured SEO content briefs using the FLOW model. Delivers a prioritized action plan with strict fact validation.
MIT ★ 159 updated 2026-11-09
.claude/commands/content-planning-for-topical-relevance-prompt.mdWhat content-planning-for-topical-relevance-prompt does
This prompt directs the model to act as a senior SEO strategist following the FLOW framework. It analyzes searcher intent, existing proof, and conversion friction points without fabricating numbers or reusing private examples. Every assumption gets labeled explicitly, while unverified claims are placed in a separate review list.
The generated deliverable contains an executive summary, a priority table, copy recommendations, required evidence, and a measurement plan. You supply the business name, target URL or query set, target audience, and existing analytics or reviews. The prompt targets long-context reasoning models; smaller models need narrower inputs processed one section at a time.
What it helps with
- build an execution-ready SEO rewrite brief around search intent
- separate verified page facts from assumptions before publishing
- prioritize structural and copy updates based on search evidence
- establish a verification checklist for disputed factual claims
Example prompts for the agent
- Create a topical relevance brief for our local service landing page using these search queries and analytics
- Run the FLOW model prompt on our product page notes to identify evidence gaps and rewrite priorities
How to install content-planning-for-topical-relevance-prompt
Manually: put the files in place
.claude/commands/content-planning-for-topical-relevance-prompt.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about content-planning-for-topical-relevance-prompt
How to install content-planning-for-topical-relevance-prompt in Claude Code?
Add the prompt file to .claude/commands/content-planning-for-topical-relevance-prompt.md inside your project directory.
What does content-planning-for-topical-relevance-prompt do?
It generates a prioritized SEO audit document containing copy recommendations, evidence gaps, verification checklists, and conversion tracking milestones.
What models work with content-planning-for-topical-relevance-prompt?
Long-context reasoning models run it best. Smaller models require narrower inputs and generating one deliverable section at a time.
Source text
content-planning-for-topical-relevance-prompt.md · MIT
<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Content planning for Topical Relevance Prompt" description: "Content planning for Topical Relevance Prompt" updated: 2026-04-25 tags: - prompts - find --- # Content planning for Topical Relevance Prompt ## Use This When Use this prompt when you need a structured find deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification. ## AI Compatibility Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time. ## Inputs - Business or website name. - Target page, profile, query set, or campaign. - Audience and geography where relevant. - Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes. - Constraints, exclusions, and required sources. ## Prompt ```text Act as a senior SEO strategist using the FLOW model. Task: create a find deliverable for: [BUSINESS OR ASSET]. Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around: 1. Searcher or buyer intent. 2. Evidence available now. 3. Gaps that block trust, extraction, or conversion. 4. Recommended changes in priority order. 5. Measurement events and review cadence. 6. Claims that require source verification before publication. Return a concise working document the team can execute. ``` ## Output - Executive summary. - Priority table. - Recommended copy, structure, or audit findings. - Evidence needed. - Measurement plan. - Verification checklist. ## Example Input: a local service page with weak proof and inconsistent profile details. Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure. ## See Also - [Prompt Library](../README.md) - [FLOW Framework](../../flow-framework.md) - [Bibliography](../../bibliography.md) ## Source Note Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.
© zhtyyx · MIT · zhtyyx/codex-seo