Most blogs are a pile of posts written once and never opened again. Often a few of them bring in most of the search traffic, and some of those are slowly losing it to a broken link, an old product name or a title nobody would click.
Refreshing the ones that already get found is a smaller job than writing new ones, and AI can do most of it if you keep the edits small and approve each one.
The loop here comes from BlogEO, a tool an intern built at her company and Alex Lieberman wrote up. Its reported results: Search impressions went up 5.8 times and page-one queries 9.8 times, and the blog's average position moved from page two to page one. Worth knowing before you quote it: the headline said traffic went up six times, but the numbers it reports are impressions and queries (In the margin: read the numbers.).
Export two periods from Search Console
In Google Search Console, open the Pages report, filter to your blog, and compare the last 28 days with the previous 28. Export it. For the posts you'll audit later, also note the top queries each one shows up for.
Look at how uneven the list is. In the blog behind BlogEO, an AI content tool an intern built and Alex Lieberman wrote up, about 70% of traffic came from 14 posts and about 50% from just five. Nobody had joined the data, because it lived in about five places.
Checkpoint
One export, two periods, blog pages only.
Rank the posts by clicks you are losing
the step that pays off
Paste the export into the prompt below. The scoring is BlogEO's: the unit of opportunity is clicks, and a real drop in clicks jumps the queue ahead of any estimate. CTR gap and rank upside come next.
Take only the top of the list forward. BlogEO gives every post a cheap score and spends the expensive fact-check and SEO pass only on the top 15 or so. For a smaller blog, five to ten is plenty.
Rank the posts by the clicks they are leaving behind
Checkpoint
A short list of posts, each with the number that put it there.
Audit each post for small edits
Run each post on the short list through the audit prompt. It does the hygiene check first, the way BlogEO does: broken links, positioning drift, products you no longer offer. Then it proposes at most three edits.
The edits stay small on purpose. BlogEO's rule: most posts were handwritten, so don't paste AI voice over human voice. The changes the write-up singles out are small ones: the SEO title, the meta description, a swapped link.
Audit one post and propose small edits
Pro tip
Click every link the audit lists. The model can't tell you whether a page still exists.
Checkpoint
Up to three before-and-after edits for each post.
Approve each edit by hand
Read each proposed edit, then approve it, change it, or skip it. Publish the ones you keep yourself, and write down the date next to the post.
This is the guardrail in BlogEO's design: the agent has no write path to live content until a human clicks. Every change has a name next to it.
Checkpoint
A log of which posts changed, what changed, and on what date.
Leave each post alone for 28 days
Don't touch a changed post again for 28 days. BlogEO builds in that cooldown so Search Console has time to catch up, and so the same post isn't edited over and over before anyone knows what worked.
After 28 days, export again and compare the changed posts with their numbers before the edit. Then run the loop again from step one.
Checkpoint
A before and after for every edited post, 28 days apart.
The takeaway
You end up with a short list of the posts that matter, a few small edits on each that you approved yourself, and a dated log so you know in 28 days which ones worked.
The limit: this refreshes posts that already have some search presence. It won't rescue a post nobody searches for, and it can't check its own links. Search results move for reasons outside your blog too, so judge the changed posts against their own before and after.
Variations
Find the missing posts. BlogEO also looks at near-miss queries: searches your blog shows up for without a page aimed at them. Those feed new post ideas. Treat "skip" as a real answer when a query isn't worth owning.
Let the tiny fixes through. In BlogEO, broken-link fixes and missing SEO fields publish without a person, and everything else waits for a click. Only do this once you trust the link check.
Make it weekly. BlogEO runs on a weekly cadence in Slack, with content ideas on Monday and the audit on Tuesday, plus an "audit this page now" on demand. A calendar reminder does the same job for a smaller blog.
Don't rewrite whole posts. A full AI rewrite of a handwritten post is the opposite of this loop. It changes the voice and gives you no way to tell which change helped.