Skip to content
Copy

Refresh old blog posts for search with an AI audit loop

Rank your existing posts by the clicks they're losing, audit the top few for broken links and stale claims, make small edits you approve one by one, then leave each post alone for 28 days.

contentstarter

Job cardDo it yourself

Time
an afternoon, then 28 days before you judge it
Works in
Claude or ChatGPT
Steps
5
Level
starter
Or we set it up for you

How it runs, start to finish.

Drawn from the steps below

  1. 01Export two periods from Search Console
  2. 02Rank the posts by clicks you are losing
  3. 03Audit each post for small edits
  4. 04Approve each edit by hand
  5. 05Leave each post alone for 28 days

Illustrative · the tools you use may differ

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.).


  1. 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.


  2. 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

    Below is a Google Search Console export of our blog pages, comparing
    the last 28 days with the 28 days before. Rank the posts by
    opportunity, measured in clicks.
    Score each post on three things, in this order of priority:
    1. Click loss: clicks in the last 28 days minus clicks in the 28 days
    before. A real loss ranks above any estimate.
    2. CTR gap: compare the post's click-through rate with the median
    click-through rate of our own posts at a similar average position.
    Multiply the gap by the post's impressions to estimate clicks missed.
    3. Rank upside: posts with an average position between 11 and 30,
    which sit on page two or three.
    Rules:
    - Use only the numbers in the export. Do not use outside benchmarks
    for click-through rates.
    - Ignore posts with so few impressions that the numbers mean nothing,
    and say which ones you ignored.
    - Return the top {{HOW_MANY}} as a table: page, the score that put it
    there, the numbers behind it, and one line on why.
    Export:
    """
    {{SEARCH_CONSOLE_EXPORT}}
    """

    Checkpoint

    A short list of posts, each with the number that put it there.


  3. 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

    Audit the blog post below and propose small edits. A person wrote this
    post. Do not rewrite it and do not change its voice.
    Check, and list every problem you find:
    - Links: list every link with its anchor text, so I can check each one
    still works and still points to the right thing. Flag any that name a
    product, plan or page that is not in our current offer below.
    - Stale claims: anything that mentions a product, price, feature or
    date that our current offer below contradicts or does not include.
    - Positioning: any sentence that describes us in a way our current
    one-line description below does not match.
    Then propose at most three edits, most valuable first. Each edit shows
    the exact current text and the exact replacement. Prefer, in order:
    a new SEO title (under 60 characters), a new meta description (under
    155 characters), a link swap, one corrected sentence. Do not propose
    new sections.
    If you are not sure a claim is out of date, write [CHECK: the claim]
    instead of editing it.
    Our current one-line description:
    """
    {{WHAT_YOU_DO_IN_ONE_LINE}}
    """
    Our current offer (products, services, prices):
    """
    {{CURRENT_OFFER}}
    """
    Search queries this post already shows up for:
    """
    {{TOP_QUERIES_FOR_THIS_PAGE}}
    """
    The post:
    """
    {{POST_TEXT}}
    """

    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.


  4. 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.


  5. 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.

← All use cases

Work order · from this page

Want this running in your business?

We set it up, you keep it. Talk to us.

  • Set up with you, in accounts you own
  • Your team trained on it as it goes live
  • Starts with a 30-minute call

30-minute callA written roadmapNo commitment

We reply within 2 business days.

We set it up