Topic Coverage Audit
Find out whether your page covers the topic deeply enough to be useful to an AI-generated answer
What This Prompt Does
AI systems prefer pages that cover a topic thoroughly. This prompt breaks the topic into subtopics, identifies which ones your page covers and which it doesn't, and prioritizes the top five additions — so you know exactly what to write next.
When to Use It
- •Building out a cornerstone page over multiple drafts
- •AI answers mention related topics but not yours — suggesting coverage is too thin
- •Planning an editorial calendar to expand a topic cluster
- •Validating a content brief before a writer starts
The Prompt Template
Act as a content strategist for AI visibility. Your goal is to determine whether this page covers the topic well enough to be useful in AI-generated answers. Context: - Topic: [TOPIC] - Page text: [PASTE PAGE CONTENT] - Target audience: [TARGET AUDIENCE] Task: Identify: 1. the key subtopics the page already covers 2. the key subtopics it is missing 3. the likely questions the page can answer now 4. the likely questions it cannot answer well 5. the top 5 additions that would improve topic coverage Process: 1. Identify the main topic. 2. Break the topic into likely subtopics. 3. Compare the page to those subtopics. 4. Recommend the most important additions. Constraints: - Use simple language. - Focus on the biggest gaps. - Do not recommend adding filler. - Keep the answer under 450 words. - Favor clearer facts, direct answers, and useful specifics over polished marketing language. Output format: Use these headings: - Covered Subtopics - Missing Subtopics - Questions the Page Can Answer - Questions the Page Cannot Answer Well - Top 5 Additions
How the Prompt Is Structured
"Break the Topic Into Subtopics"
The Process step forces the AI to generate a full subtopic tree before comparing. Without it, the model only flags obvious gaps and misses deeper ones.
Covered vs Missing
A two-column view makes the gap immediately visible. You scan Covered to confirm the strengths and Missing to know what to add.
Question-Level Translation
Translating subtopics into "questions the page can/cannot answer" connects topic coverage to real user queries — the currency AI systems trade in.
"Do Not Recommend Filler"
Adding subtopics just to hit a word count hurts AI visibility. The constraint keeps every addition load-bearing.
Example Output
Covered Subtopics
Service description, primary service area, phone number, basic emergency services list.
Missing Subtopics
Pricing, response time, service guarantee, what to do before arrival, licensing and insurance details, reviews.
Questions the Page Can Answer
- • Do you serve my area?
- • What kinds of emergencies do you handle?
Questions the Page Cannot Answer Well
- • How much does emergency service typically cost?
- • How fast will you arrive?
- • Are you licensed?
- • Do you guarantee your work?
- • What should I do while I wait?
Top 5 Additions
- Add a short pricing section with at least a minimum call-out fee.
- Add an explicit response-time promise with a concrete number.
- Add licensing, insurance, and business-established details.
- Add a "What to Do Before We Arrive" checklist.
- Add 3 customer reviews on-page with names and neighborhoods.
Tips for Better Results
Name the Topic Precisely
"Plumbing" is too broad. "Emergency residential plumbing in Bozeman, MT" produces a subtopic list tailored to what you actually need.
Ship Additions in Sections
Don't rewrite the whole page. Add one missing subtopic per sprint as a new section, and re-run the audit after.
Some Gaps Deserve Their Own Page
If a missing subtopic is large (e.g., "emergency pricing"), a dedicated pricing page often beats stuffing it onto the service page.
Treat "Missing" as a Content Calendar
Every missing subtopic can become a blog post, FAQ section, or new landing page. The audit doubles as a roadmap.
Cover the Questions AI Is Being Asked
We turn topic coverage audits into shipped content that wins citations — one subtopic at a time.