How AirOps Playbooks Work: Defining a Scout
Your content refresh pipeline is only as strong as the decisions that feed it, and picking the right pages to update can feel like guesswork without a clear framework. In this lesson, Aaron shows you how to build a Playbook that pinpoints declining pages and prioritizes them by real data, keeping your refresh queue sharp on autopilot.
What You'll Learn
A content refresh system in AirOps breaks into two roles: the Scout and the Action Playbook. The Scout decides which pages need attention. The Action Playbook carries out the update.
The Scout Playbook's single job is selection. It identifies pages that are losing AI visibility and ranks them by impact so you know where to focus first.
Aaron walks through the full anatomy of a Scout Playbook in this lesson, from objective setting to output formatting to scheduling triggers.
Setting the objective
Every Scout Playbook starts with a clear objective: surface pages losing visibility, ranked by impact, with each recommendation including the URL and primary keyword.
You also define guardrails up front. For example, the Scout excludes any page that already appeared in your approved or rejected Grids within the last 60 days. This prevents duplicate recommendations from clogging your workflow.
A target page folder input lets you scope the scan. The default is your blog folder, but you can adjust it to any section of your site.
Defining "losing visibility"
The Scout uses AirOps Insights metrics to determine which pages are declining. These include citation rate (how often AI engines cite your page) and mention rate (how often your brand appears in AI answers). The Scout also factors in signals from AI search and Google search.
Aaron explains four ranking criteria the Scout applies to prioritize recommendations:
- Opportunity size: Search volume tied to the page's primary keyword. Higher volume means a bigger potential payoff.
- Decline signal severity: How steep the drop in visibility metrics has been. Steeper declines get flagged first.
- Page importance and topical authority: Whether the page is central to a topic cluster your brand owns or is building toward.
- Competitive pressure: Whether named competitors are gaining ground on the same queries.
The Scout's output
The Scout produces an executive brief called the "Refresh Scout Report," formatted in Markdown.
This report ranks your pages by priority and gives you the context you need to decide which ones move forward.
Human review step
After the Scout generates its report, a human review step pauses the Playbook. You review each recommendation and mark an X next to any pages you want to discard.
This keeps you in control. The Scout does the analysis, but you make the final call on what gets refreshed.
Saving recommendations to Grids
The Playbook's second section saves your decisions to two Grids: one for approved refresh pages and one for rejected pages.
Each Grid row captures the URL, page title, primary keyword, and date recommended.
Rejected pages feed back into the guardrails. The next time the Scout runs, it skips those pages automatically. Approved pages move into your Action Playbook queue.
Publishing and triggers
Once your Scout Playbook is ready, you can publish it and attach a trigger so it runs without manual kicks. Aaron covers four trigger types:
- Schedule: Run on a recurring cadence, such as every Monday morning.
- Webhook: Fire the scout from an external system like your CMS or data platform.
- Monitor: Scan the web on a set interval (for example, every 12 hours) and trigger the scout when competitor activity changes.
- AEO Insight trigger: React to specific metric shifts in AirOps Insights. For example, trigger the scout when citation rate drops by 10% over a rolling seven-day window, scoped to specific topics, platforms, or regions.
These triggers keep your Scout running continuously, feeding your content refresh pipeline with high-priority recommendations on an ongoing basis.
Key takeaways
- Rejected pages are guardrails, not dead endsEvery page you reject gets recorded in a Grid and excluded from future scout runs for 60 days. Your "no" today saves you from seeing the same recommendation next week.
- You can edit recommendations right inside the chatDuring the human review step, you don't need a separate tool to discard pages. Change the checkmark to an X directly in the artifact, and the Playbook reads your decision on the spot.
- The default scan targets your blog folderWhen you set up a scout, the target page folder input defaults to your blog. If you want the scout to cover landing pages, product pages, or another section, you need to update that input before publishing.
- AEO Insight triggers let you scope by topic, platform, or regionYou're not limited to a single, site-wide alert. An AEO Insight trigger can fire your scout only when citation rate drops for a specific prompt topic, on a specific AI platform, or in a specific geographic region.
- You design the report format yourselfThe Refresh Scout Report isn't a fixed template. You sketch the exact Markdown structure you want in the Playbook's output section, so every run produces a brief that fits your team's review workflow without post-processing.
FAQs
A Scout Playbook is an automated system that monitors your content library and identifies pages losing AI visibility. It evaluates every page against ranking criteria, filters out pages that were recently reviewed, and delivers a prioritized shortlist of refresh candidates. You approve or reject each recommendation before any action is taken.