
How a PR agency scaled SEO and content with 30+ AI agents
A mid-size PR agency runs 30+ production AI agents — technical SEO, PR research, content at scale, and three niche directories — on a self-hosted runtime.
- AI agents in production
- 30+AI agents in production
- articles produced
- 1,000+articles produced
- niche directory sites
- 3niche directory sites
- to build, then ongoing
- 7 moto build, then ongoing
The agency had a problem every growing PR firm eventually hits: the work that wins clients — original research, technical SEO, and a steady stream of well-sourced content — is exactly the work that doesn't scale with headcount. This is how we turned that manual grind into a fleet of more than 30 production AI agents, running reliably enough to put in front of paying clients.
The client
A mid-size PR agency running content, SEO, and digital-PR programs for a roster of clients. Their differentiator was credibility: articles backed by real research, not filler — the kind of pieces that earn coverage and citations from major outlets like CNN and The Times. The problem was that this quality was entirely manual, and manual doesn't scale.
The challenge
Every deliverable competed for the same scarce analyst hours:
- Technical SEO across many client sites — audits, fixes, and monitoring — done by hand in spreadsheets.
- Research for every PR article, chasing primary sources and data to make each piece genuinely citable.
- Content production at a volume the team could never realistically staff for.
- Directory sites the agency wanted to launch in specific niches, each needing hundreds of quality listings.
- Competitor analysis that went stale the moment it was finished.
They didn't want a chatbot. They wanted the busywork to run itself — reliably, on-brand, and visible enough to trust with client work.
Our approach: a fleet, not a feature
Instead of one "AI writer," we built a fleet of specialised agents — more than 30 in production — each scoped to a single job and wired into the tools the agency already used. The design principle was boring on purpose: every agent does one thing, is observable, and hands its output to a human to approve rather than publishing blindly.
The whole fleet runs on the Stacx24 Runtime, self-hosted in the agency's environment, which gives every agent monitoring, cost control, memory, and governance out of the box.
Inside the fleet
Technical SEO agents
These pull live data from Google Search Console and Ahrefs, then surface and prioritise issues — crawl errors, thin or cannibalising pages, broken internal links, decaying rankings. They draft the fix — a rewritten title, a redirect, an internal-link plan — and route it to an editor. What used to be a monthly manual audit became a continuous, always-on process.
Research and content agents
The agency's edge is research-backed writing, so these agents lead with sources. Each grounds itself in authoritative references before drafting, so claims are backed rather than invented — the foundation for pieces that stand up to editorial scrutiny and earn citations from major publications. Editors review and approve; the agents handle the grind of sourcing, structuring, and drafting. Over the engagement the fleet has produced 1,000+ articles.
Directory-building agents
For three niche directory sites, agents research, structure, and populate listings at a volume that would be uneconomical by hand — turning a "someday" idea into three live properties.
Competitor-analysis agents
Instead of a one-off deck that's outdated on delivery, these agents monitor competitors continuously — content, keywords, backlinks, positioning — and keep a living picture the strategy team can actually act on.
The stack
The system is deliberately built on tools the team already trusted, with LLMs chosen per task:
- Claude and OpenAI models — stronger reasoning models for research and analysis, faster models for high-volume drafting.
- Google Search Console and Ahrefs for live SEO signals.
- The agency's headless CMS for publishing, Google Sheets as a familiar control surface, and Amazon S3 for assets and artifacts.
- The Stacx24 Runtime tying it together — the control plane that makes 30+ agents observable and affordable.
Keeping 30+ agents trustworthy
Running one agent is a demo. Running thirty in production is an operations problem — and it's where most "AI automation" quietly falls apart. Three things made it viable:
- Observability. Every agent run is traced end to end, so when something drifts it's visible, not a mystery.
- Cost control. The runtime meters spend per agent and per workflow, with budgets and alerts, so continuous operation stays economical.
- Human-in-the-loop and governance. Agents draft; people approve. Guardrails check tone, facts, and PII before anything ships.
That combination is the difference between a clever prototype and a system a PR agency will put in front of paying clients.
The results
Over roughly seven months — and continuing with ongoing support — the fleet has:
- Put 30+ agents into production across technical SEO, research, content, directories, and competitive intelligence.
- Produced 1,000+ articles, grounded in research rather than filler.
- Stood up three niche directory sites the agency couldn't have staffed manually.
- Turned technical SEO and competitor analysis from periodic projects into continuous, always-on processes.
Most importantly, it did this visibly: the agency can see what every agent did and what it cost — the trust that lets them scale AI into real client work instead of keeping it in a sandbox.
What's next
The engagement continues. New workflows get added to the fleet the same way the first ones did — scoped tightly, instrumented from day one, and expanded once they've earned it. If you're running a content, SEO, or digital-PR operation that's bottlenecked on manual work, that's exactly the kind of system we build.
“We went from a team drowning in manual research to a system that ships publish-ready work at a scale we could never have hired for — and we can see exactly what every agent did, and what it cost.”
Built with
- Claude
- OpenAI
- Stacx24 Runtime
- Google Search Console
- Ahrefs
- Headless CMS
- Google Sheets
- Amazon S3
Frequently asked questions
- Can AI agents actually run technical SEO reliably?
- Yes — when they're scoped and supervised. Our technical-SEO agents read live data from Google Search Console and Ahrefs, flag issues (crawl errors, thin pages, cannibalisation, broken internal links), and draft fixes. A human approves changes before they ship, and every run is traced, so the work is auditable rather than a black box.
- How do you stop 30+ agents from producing low-quality or off-brand content?
- Three layers: retrieval grounds each article in vetted, authoritative sources so claims are backed rather than invented; guardrails check tone, facts, and PII before anything is published; and an editor approves the final draft. The agency reviews, it doesn't assemble — so quality scales without the manual grind.
- Which LLMs power the agents?
- A mix of Claude and OpenAI models, chosen per task — stronger reasoning models for research and analysis, faster models for high-volume drafting. Because the agents run on the Stacx24 Runtime, models can be swapped per workflow without rebuilding the product.
- How is agent cost controlled at this scale?
- The Stacx24 Runtime meters every run: per-agent and per-workflow token spend, budgets, and alerts before costs surprise anyone. That's what makes running 30+ agents continuously viable — you can see and cap the spend, not just hope it stays reasonable.
- Can we run this in our own cloud?
- Yes. The Stacx24 Runtime is self-hosted — it deploys into your environment, so your data, prompts, and models never leave your infrastructure. Observability, cost control, and governance all run on your own systems.
- How long does it take to stand up an agent fleet like this?
- This one took about seven months to reach 30+ agents across technical SEO, research, content, and competitor analysis — but value landed far sooner. We ship the first useful workflow in weeks, then expand the fleet workflow by workflow, with ongoing support once it's running.
More case studies
- A real-estate directory that ranks itselfSearch, enrichment, and ranking across thousands of listings — built to stay fast and accurate as the catalogue grows.
- Sensor-to-dashboard for vertical farmingA production ingestion pipeline — Raspberry Pi over mTLS, FastAPI, Postgres — feeding live dashboards and an assistant.
- A RAG assistant teams actually trustGrounded answers with citations, evals to keep them honest, and observability so drift gets caught before users do.