Key takeaways
- A content team running AirOps at full tilt (25-30 pieces a month) was producing content that technically shipped but rarely got cited by ChatGPT, Perplexity, or Google AI Overviews.
- Cutting monthly output by roughly 60%, from ~28 articles to ~11, and routing every piece through a real editorial review process more than doubled citation rate per published page within two quarters.
- The mechanism isn't magic: ChatGPT cites an average of only about 5 sources per response, so thin, broadly-similar pages compete for a tiny number of slots, and editorial depth is what wins those slots.
- AirOps and tools like it are genuinely useful for research, drafting, and repurposing. The failure mode is treating them as a publish button instead of a first-draft engine sitting in front of a human editor.
- If you want to know whether the switch is actually working, you need visibility data, not vibes. Tools like Promptwatch can show you which pages get cited, by which model, and why.
The setup: what "scaling content with AI" actually looked like
The team in question, a B2B SaaS marketing group of four people, adopted AirOps in early 2025 the way a lot of teams did: with a mandate to 10x output without adding headcount. AirOps is built for exactly that. It's a content engineering platform, not a chatbot wrapper, that combines brand knowledge, a workflow builder (AirOps calls them Grids and Playbooks), and human review checkpoints so marketing teams can run content as a repeatable pipeline instead of a series of one-off projects.
On paper this worked. The team went from shipping 6-8 articles a month to 25-30. Tasks ran through Solo and then Pro-tier plans, research was pulled in automatically, drafts came out in brand voice (mostly), and a human did a pass before publishing. Reddit threads from teams using AirOps describe a similar shape: "Use AirOps if you're doing 10+ pieces of content a month and need brand-accurate, SEO-optimized output," as one long-term user put it after a four-week trial. That's a fair description of what the tool is good at.
The problem showed up about five months in, not in the AirOps dashboard, but in the numbers that actually matter: organic rankings on competitive terms flattened, then dipped after a core update, and citations in AI answers stayed near zero despite a growing archive of published pages. The team had scaled a pipeline. They hadn't scaled relevance.
Where the pipeline actually broke
It wasn't the AI. It was what happens when "human review" becomes a rubber stamp because there are 30 drafts a month and one editor.
Task-based billing quietly encouraged volume
AirOps' pricing is task-based, and there's a well-documented gap between its Solo tier ($199-200/month, 20,000 tasks) and its Pro tier ($1,999-2,000/month, 75,000 tasks), with no mid-tier in between. Independent reviews call this the "$200-to-$2,000 cliff." Each article eats roughly 500-800 tasks across research, drafting, review, and publishing steps, so a 30-article month runs 15,000-24,000 tasks, right at or past the Solo ceiling. The pricing structure itself nudges teams toward publishing more to amortize the plan cost, which is precisely the wrong incentive when the actual bottleneck is editorial attention, not task volume.
E-E-A-T gaps piled up invisibly
A 16-month study tracking 4,200 articles across 140 domains found that AI-only content, generated and lightly copyedited, ranked 23% lower on average than human-written content on matched keywords, and the gap widened to 41% on competitive commercial queries. The same study found AI-only pages lacked a verifiable byline in 89% of cases, had original data or research in only 4%, and included no expert quotes in 94%. Content that is AI-assisted but substantially rewritten, with at least 30% original editing plus named expert attribution, closed almost the entire gap, landing within 4% of fully human-written content. The team's AirOps output sat on the wrong side of that line for most of the run: fast, brand-voice-consistent, and almost entirely missing the signals that separate "content that exists" from "content worth citing."
The review step wasn't actually a review
Even AirOps' own users treat human review as a baseline necessity, not an optional extra, per discussion in the r/AI_SearchOptimization community. But a five-minute skim of an AI draft, checking tone and grammar, isn't the same as a developmental edit that interrogates the thesis, verifies claims, and decides whether the piece should exist at all. Glean's research on AI content governance found that 42% of companies abandoned most of their generative AI content initiatives within a year (up from 17% in 2024), largely because quality and governance gaps outpaced the tooling. The team was headed toward that statistic before they changed course.
The pivot: building an actual editorial process
The fix wasn't abandoning AI tools. It was inserting the parts of an editorial process that had been skipped, borrowing heavily from how established editorial teams operate. Every.to, which publishes its full internal AI workflow, is a useful reference point: writers there use AI for research and first drafts, but every piece goes through a developmental edit (does the thesis hold up, is the structure right), then a line edit, then a top editor's final pass that specifically screens for "AI tells": vague pronoun openers, unsourced claims, hedging language, and formulaic transitions. No piece goes from AI draft to published without a human substantively rewriting it.
The team adapted a version of Glean's seven-step framework:
- Turn the brand voice guide into an actual review checklist, not a vibe.
- Classify each piece by risk before drafting starts, a comparison page aimed at a competitive term gets a different review bar than an internal FAQ.
- Ground every draft in the company's own documentation and product data, not general model knowledge.
- Assign a named owner to each review stage, not "the team."
- Edit against a fixed checklist, the same one every time, rather than editor intuition.
- Let automation handle the checks machines are actually good at: fact-linking, style consistency, broken citations.
- Feed performance data back into the checklist every quarter.
The practical result was fewer pieces getting greenlit. Ideas that didn't have a clear angle, a data point nobody else had, or a subject-matter expert willing to be quoted got cut before drafting even started. Output dropped from roughly 28 pieces a month to around 11.
Why fewer, deeper pieces doubled citations
This is where the data actually explains the result instead of just describing it. ChatGPT cites an average of about 5 sources per web-search answer, according to Promptwatch's data on average sources per response. Perplexity and Google AI Overviews are more generous, citing roughly 10 sources each, but ChatGPT's inventory is small and brutally contested. When you're competing for one of five slots, a page that partially covers a topic loses to a page that fully answers the specific question someone asked. Ten mediocre pages don't beat one page written by someone who actually knows the subject.
Promptwatch's tracking of ChatGPT citation types over August 2026 backs this up from the content-format side: informational, single-answer formats, how-to guides and documentation specifically, more than doubled their citation share over the month (how-tos went from 4.3% to 9.1%, documentation from 3.3% to 8.2%), while thin landing pages fell from 20% to under 12% over the same period. Social posts collapsed even harder, dropping from 4.4% to under 1% after August 14, the same day Reddit's share of ChatGPT citations cratered from roughly 4% to 0.5%, per Promptwatch's report on Reddit citations dropping in ChatGPT. Anything built on the assumption that scaled, UGC-style volume gets you cited is fighting the current trend, not riding it.
There's also a domain-authority angle worth knowing if you're a mid-market team and not a legacy media brand. Promptwatch's citation-share-by-domain-rank data shows domains in the DR 46-90 range capturing nearly 65% of all ChatGPT citations in August, while top-tier DR 91-100 sites shrank from about 7% of citations in week one down to roughly 3% by mid-month. You don't need Forbes-level authority to get cited. You need a page that actually answers the question better than the five other pages competing for the slot.
What changed in the actual workflow
Here's the honest before-and-after, not a feature list, just what moved:
| Dimension | Old AirOps-only pipeline | New editorial process |
|---|---|---|
| Monthly output | ~28 articles | ~11 articles |
| Human review depth | Single skim pass for tone/grammar | Developmental edit + line edit + checklist-based top edit |
| Sourcing | Model-generated citations, lightly checked | Named SME quotes, original data points, verified links |
| Greenlight criteria | Keyword had search volume | Unique angle, data, or expert access required |
| Task/billing pressure | Task quota nudged toward volume | Budget reallocated toward editor time, not task count |
| AI's role | Draft-to-near-final | Research assist + first draft only |
| Citation rate (per published page) | Baseline | 2.1x baseline over two quarters |
None of this required firing AirOps. It required treating it the way Every.to treats AI: as a research and drafting layer that feeds a human process, not a replacement for one. AirOps itself supports this; its brand kit and knowledge-base features exist specifically to ground drafts, the team just hadn't been using the review gates the platform makes possible.
Measuring whether it actually worked
The part most teams skip: after you slow down, you need a way to prove the slower pace is paying off, or you'll get pressure to go back to 30-a-month within a quarter. Rankings alone won't tell you if AI models are citing you. You need visibility into which pages get pulled into ChatGPT, Perplexity, and AI Overview answers, and ideally why.
This is the gap tools like Promptwatch are built to close. Beyond tracking whether a brand gets mentioned, it shows citation trends per page, crawler logs from ChatGPTBot, ClaudeBot, PerplexityBot and 400+ other bots, and a content gap analysis that flags exactly where a competitor's page is winning a citation slot that yours isn't. For a team that just cut output by more than half, that kind of page-level feedback is the difference between "we think this is working" and knowing which of the 11 monthly pieces is actually earning citations and which ones to stop writing.
If you're evaluating options beyond Promptwatch, the GEO software directory at bestgeosoftware.com is a reasonable place to compare platforms side by side before committing budget.
A practical checklist if you're running a similar pipeline
- Audit your last 20 published AI-assisted pieces against the E-E-A-T basics: named byline, at least one original data point or SME quote, a clear point of view. If most fail, that's your citation problem before it's a tooling problem.
- Cut anything greenlit purely because a keyword tool showed volume. Volume without an angle is what got the team into trouble in the first place.
- Reallocate the budget you'd spend on extra task credits toward editor time instead. Glean's research found structured review governance cuts revision rounds from 5-7 down to 2-3, which pays for itself.
- Track citations at the page level, not just brand mentions, so you know which formats (how-tos, documentation, comparisons) are actually winning slots in your category.
- Re-test quarterly. ChatGPT's citation behavior shifted meaningfully within a single month in 2026; what worked in June may not work in September.
The uncomfortable bottom line
Cutting output by 60% felt, at the time, like admitting defeat. The team had promised leadership a 10x content machine and delivered a smaller archive instead. But a smaller archive that gets cited beats a large one that doesn't, and the AI search engines are actively rewarding that trade-off right now: fewer slots per answer, more weight on depth and expertise, less patience for anything that reads like it was assembled rather than written. If your content program is optimized for task counts instead of citation counts, that's the metric worth changing first.
For teams figuring out how AI visibility fits into a broader SEO and content strategy, 1001 SEO Media works with content and marketing teams on exactly this kind of shift, from technical SEO audits to the editorial processes that actually earn citations in ChatGPT, Gemini, and AI Overviews.