Keeping Data-Driven Content Fresh Was a Monthly Slog. So We Taught an Agent to Do It.

At Ahrefs, we publish many data-driven posts.

Four Ahrefs blog post previews titled "The 50 Most-Cited Websites in Grok, Copilot, Perplexity, and Gemini (June 2026)", each with an author byline and date

Publishing them is fun. Easy. And they get a ton of search traffic too.

Ahrefs organic traffic performance chart showing an upward trend in monthly organic traffic from 2015 to 2023

But such posts, like “Top Google Searches” or “Most Asked Questions on Google”, are only worth reading if the numbers are current.

Google knows that too, which explains the spike in search traffic every time we update the posts.

The same Ahrefs organic traffic chart with orange arrows pointing to repeated traffic spikes that line up with each content update

So someone has to keep them fresh.

Ideally, every month, someone (usually the author) had to pull fresh data from Ahrefs (or the API), clear out the junk and format the tables. The posts with custom charts were worse: spec the new chart, hand it to design, wait, review it, send it back for tweaks. Only then paste everything into WordPress without breaking the layout, update the dates, and republish.

One post is fine. Bearable tedium. But 14 posts? 20? The more you publish, the more it becomes a slog. I could lose a whole afternoon and have nothing to show for it except a post that said the same thing as last month with slightly different numbers.

It’s one of the most tedious jobs on the content team.

So, we made a compromise. We refreshed them every quarter. (And to be honest, there are some posts we never even got to.)

Fast forward to today. We don’t do that anymore. Letaido does it for us. It’s been running quietly for two months now. Altogether, it’s saving us at least 20 hours per month. Not only can we now update them every month, we can publish more of such posts, and update them regularly too.

It’s a genuine win/win: far less drudgery for us, and fresher, more accurate numbers for the reader.

Drop me some of that fire emoji, yes please.

Automating content marketing like this is apparently unfashionable to admit in 2026, with Gartner saying more than 40% of agentic AI projects will be scrapped by the end of 2027.

MarTech article headline reading "Gartner: 40% of agentic AI projects will fail, making humans indispensable"

With the amount of LinkedIn bragging and much of “AI agent” demos being merely performative, I can understand the disillusionment. Fortunately, this one works.

But it works precisely because it’s boring. It doesn’t write our articles. It simply does the tedious part, which is a big part of content marketing.

Brand Radar — cleans each one by its own rules, and saves the results so I can see exactly what it kept and what it threw out. Then it builds a WordPress draft with the new tables in place and emails me to say it’s ready.

An email titled "Data Refresh Hub — June 2026" listing seven WordPress drafts ready to review, each linking to an updated data post

I want to be honest about how unglamorous the building was.

Getting the data alone meant three completely separate paths. I could get the US keyword tables easily via Letaido as it has all Ahrefs data. But the global ones weren’t available as it was custom-made by our data scientists previously for these posts. So I had to connect it to a separate internal service. Then I had to grab the AI citation tables from Brand Radar, one platform at a time.

A "Data Sources (all via Ahrefs API)" table mapping each post to its API method, sort order, country, and special handling rules

And then there are what seem to be silly problems. One build kept throwing a 500 error over a tiny capitalization mismatch: our code sent the field as Cpc, and the API insisted on CPC, all caps. I lost a genuinely embarrassing amount of time to that one.

A debugging explanation showing that the SDK serialized the sort value as "Cpc" causing a 500 error, while the API expected "CPC" in all caps

Despite all of these, I want to say it was genuinely magic. After all, I didn’t hand-code any of this. I built it conversationally in Letaido. Letaido did all the work. Even the “time lost” was Letaido figuring out how to fix it, not me.

His reaction, near enough word for word: “This was my dream for AI: actual automation, genuinely saving us hours of drudgery. And it is finally here. SORCERY!!!”

A LinkedIn post from Ryan Law, Director of Content Marketing at Ahrefs, describing how his team now automatically pulls data, generates charts and tables, updates WordPress drafts, and emails him, ending with "SORCERY!!!"

His version now runs on a schedule: pulls fresh data, regenerates the charts and tables, builds the WordPress drafts, makes the small date and sample-size edits, and emails him when the article’s ready to look at.

An email titled "CTR benchmarks refresh ready for review — May 2026" telling Ryan the monthly refresh is ready as a WordPress draft, with edit and preview links and a note that nothing has been published

Nobody was told to do any of this. It spread because it worked, and the fact that it spread on its own (without anyone assigned to make it happen), is a clear sign that it’s real and not just a demo. Useful things just get copied, without anyone needing to call a meeting.

There are three of us running a version of this now.

How to find a job like this in your own work and automate it

I can almost guarantee that you have a job like this hiding in your own work. Most content teams do.

Here’s how I’d go looking for it.

Start with a question. Go through the work you do on repeat and ask two things of each task: does it run on a schedule, and could you write down the rules for what “done right” looks like?

If both answers are yes, it’s a candidate. “Pull the same numbers from the same place every month and reformat them the same way” passes easily. “Write the article” fails the second test, and that’s the part you might want to keep doing yourself anyway.

If what you’re running is marketing work, just go to Letaido and tell it what you need. It’ll do most of the hard, tedious work for you. (If you’re an Ahrefs customer, you get a free month.)

Then, if I had to boil down what actually made ours work:

  • Automate the plumbing, not the thinking. Fetching, cleaning, formatting, pasting. These are all mechanical work and it’s exactly what you want to hand off. Keep the thinking part for yourself.
  • Make the cleaning visible. Don’t let the agent just hand you a finished list. Get it to show you what it removed, and why, right next to what it kept.
  • Keep a human at the gate. Drafts only. Let a person publish. This buys you most of the safety.
  • Lock the things the model shouldn’t touch. Headline stats, verified figures, the opening line. You’d want to pin them down so the agent can’t quietly reword a number into something that isn’t true anymore.

That’s really all it is. It isn’t exciting, and sort of the point. The boring, well-defined jobs are the ones AI handles well today, and they’re sitting in plain sight in pretty much every content workflow.

Final thoughts

This is one of the best parts of AI automation right now. It can help with all the work you quietly dread every single week or month.

Get an agent to do it, but be the editor that says it works and pushes live.

If there’s a lesson in here, it isn’t a very flashy one. Hand the boring, repetitive stuff to the machine, and keep the parts that actually need you.

We’re all managers now.

Similar Posts