Automate monthly refreshes of data-driven articles with an agent that fetches, filters, rebuilds and drafts for human review
An Ahrefs marketer describes a monthly pipeline that pulls fresh keyword data, filters it with written rules and examples, rebuilds tables, updates WordPress drafts and notifies the editor, who approves every change before it goes live.
Evidence: The source shows its work: steps, screenshots, code or data you can inspect.
The business problem
Articles built on data (top searches, top questions and similar lists) go stale fast, and refreshing them by hand is slow, rule-heavy work that tends to slip from monthly to quarterly.
What was tried
1. Pick one repeatable, rule-based job that keeps getting delayed; here, refreshing data-led posts. 2. Write down every step, including unwritten rules and exceptions. The author suggests letting an agent interview you one question at a time and saving the result as a reusable skill file. 3. Connect trusted data sources (first-party data and APIs) rather than relying on the model's memory or open web search: the model processes the data but is not the source of it. 4. Give the system accepted and rejected examples with reasons, and keep a log of rejected items so rules can be checked. 5. Build one dataset end to end with a visible output at each stage: fetch, clean, classify, build, update the CMS draft, notify. 6. Compare the output side by side with the human version (numbers, rejections, formatting, tone, links), then schedule runs after the source data refreshes, with failure alerts. 7. Add datasets one at a time; widen the agent's permissions slowly (the author waited two to three months before allowing larger edits).
What was reported (positive)
The author says the hub now refreshes 12 datasets each month and shows screenshots of drafts waiting for review and of rejected-item lists (including real questions wrongly rejected). Teammates adopted similar workflows. No time saved, cost, or traffic change caused by the automation is reported.
Limitations
Vendor content: Ahrefs sells the data tools used and the agent platform featured, so the setup is easiest for its own customers. Run by a marketing team at a large company, not a solo founder. No before-and-after numbers. The author lists real failure modes: model updates changing how rules are read, source format changes, rule drift, CMS formatting breaks, and an access error caused by a colleague's workspace change. Human review stays mandatory.
What you need
A repeatable data-driven content job, an API or export for the data, a CMS with drafts, and an agent tool that can connect to them.
Start with a single dataset and keep the agent limited to drafts until its output matches yours for several runs.
A prompt to try
Interview me about how I currently update [article or report], one question at a time. Follow up on any vague answer. When done, write a step-by-step checklist that includes every rule and exception I mentioned.
Sources
- Ahrefs blog (Si Quan Ong) ↗ Vendor case study, published October 16, 2026
Source published: October 16, 2026. Last reviewed here: October 25, 2026. Spot a mistake? Tell us.
Tools in this workflow
- Slack: NotificationsTry Slack
- Claude Code: Named as an alternative agent toolTry Claude Code
- WordPress: CMS where drafts are updatedTry WordPress
- Ahrefs Keywords Explorer: Main data sourceTry Ahrefs Keywords Explorer
- TablePress: Table plugin for rebuilt tablesTry TablePress
Get new workflows like this by email
A short selection of the most useful new workflows, including the ones that did not work. Free, and you can unsubscribe at any time.
Related workflows
Build a five-email onboarding sequence with stop rules and a dry-run cron job, using a copy-paste prompt for your AI coding tool
A beginner guide for first-time SaaS builders: pick one first-win action, log signups and sends, map five plain emails over 14 days with stop rules, send them from a scheduled job after a dry run, and measure activation instead of opens.
Cut LLM costs in a small SaaS with flex-tier fallback, cache-friendly prompt order, side-by-side model migrations and backend circuit breakers
A bootstrapped founder's four habits for the AI calls inside his product: try the cheaper flex tier first and fall back on rate limits, order prompts so the long repeated part is cached, run old and new models side by side before switching, and cap spend in the backend.
Pressure-test a SaaS idea with a free Claude Code skill that scores evidence and returns a dated go or no-go verdict
An open-source Claude Code skill walks a solo founder from idea to one cheap demand test, then scores six dimensions with a script so the verdict comes from evidence, not enthusiasm. Free, MIT licensed, no results reported.
Turn client meeting notes into a branded A4 proposal PDF with a Claude Code skill and Puppeteer
An agency owner shares a Claude Code skill that parses meeting notes, fills a multi-page HTML proposal, checks page heights and renders a PDF with Puppeteer. Its repository supplies the template and rendering setup.