> ## Documentation Index > Fetch the complete documentation index at: https://promptwatch.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Content Agent use cases > Three scenario-driven playbooks for the Content Agent: closing a content gap cluster, keeping a comparison page competitive, and scaling a content program on autonomy settings. The Content Agent is one pipeline with many operating points: fully manual, fully automated, and everything between. These three scenarios show how the same features combine at different levels of trust. Each assumes setup is done ([overview](/docs/academy/content-agent-overview)). ### Use case 1: close a content gap cluster Scenario: you sell accounting software, and your [content gap](/docs/academy/content-gap) page shows a cluster of "how to" prompts scoring under 30% coverage: "how to file quarterly taxes as a freelancer", "how to reconcile bank statements", and six more. Competitors get cited on all of them; you're absent. 1. **Let the planner do the sequencing.** Turn the Content Agent on in **Review first** mode. The planner pulls those gap recommendations into the [schedule](/docs/academy/content-schedule) ranked by expected impact, so the cluster becomes a queue ordered by value instead of a to-do list ordered by guilt. 2. **Feed it your substance first.** Before the first drafts generate, add your real material to the [Knowledge Base](/docs/academy/knowledge-base): your tax-deadline cheat sheet, support macros, product screenshots' claims. Eight grounded articles beat eight generic ones, and this is the cheapest moment to guarantee that. 3. **Review with the gap in view.** Each draft's sheet shows why it was prioritized. Accept what's right, use **Open in editor** for fixes, and decline with a reason when the planner misread your positioning; the reasons teach you what to correct in the Brand Book. 4. **Verify the cluster closes.** Once a piece is live, Promptwatch adds its URL to the [Page Tracker](/docs/academy/page-tracker); CMS drafts aren't tracked until they go live. The gap scores update after re-analysis, and citations on those prompts are your real finish line. See [Publishing and tracking](/docs/academy/publishing-and-tracking). ### Use case 2: keep a comparison page competitive Scenario: your "YourBrand vs. BigCompetitor" page earned citations for months, then the competitor shipped a redesign and your citations on "yourbrand vs bigcompetitor" prompts dried up. 1. **Confirm the drop where it happened.** Check the page in the [Page Tracker](/docs/academy/page-tracker): citations falling while crawls stay steady means models still read the page but prefer other sources. That's a content problem, not a discovery problem. 2. **Rewrite against the pages that beat you.** Open [Optimize Content](/docs/academy/optimize-content), pick the comparison prompt and your page, and select the competitor pages currently cited for it (up to 5). Choose the **Balanced** level to keep your structure, or **Full Rewrite** if the page was thin to begin with. 3. **Review, publish, and watch the same tracker row.** The optimized draft lands in your Optimize Content list; review it in the editor and publish through your normal path. Because the URL is unchanged, the same Page Tracker row shows whether citations recover. 4. **Make it a habit, not a rescue.** Comparison prompts are high-intent, so re-run this loop whenever the tracker shows decay, not just after a competitor launch. ### Use case 3: scale a program on autonomy settings Scenario: an agency runs Promptwatch for a client with a 200-prompt setup and a thin content team. The backlog is deep, review capacity is one person, and the client wants steady output without surprises. 1. **Start gated, measure your own accept rate.** Run **Review first** for the first cycles. If you're accepting nearly every draft untouched, the settings are dialed in; if not, fix tone, defaults, and Knowledge Base before adding autonomy. 2. **Move to Auto-publish with the CMS draft safety net.** Switch autonomy to **Auto-publish** but keep **publish state** on CMS draft: the agent plans, writes, and pushes without you, while the client's CMS remains the final human checkpoint. Full autonomy plus live publishing is the last step, not the first. 3. **Shape the cadence with guardrails.** Set publish windows to business hours in the client's timezone, cap **max per day** at 1 or 2, and set the **budget share** to leave room for the manual pieces you still write yourself. See [Settings](/docs/academy/content-agent-settings). 4. **Audit through Activity, not by re-reviewing.** The Activity tab records each planning run's reasoning, and auto-approved pieces are labeled in their detail sheets. That's your monthly audit trail: what the agent chose, why, and what it published, without reinstating the bottleneck you removed. The Promptwatch Content Agent Activity tab showing the planning timeline with run groups and rationale.