Content refresh automation

Content refresh automation that rewrites old posts on autopilot

Last updated: July 2026

Content refresh automation is Leafpad's system for finding blog posts that are losing search traffic and rewriting them automatically. It connects to Google Search Console, flags any page that lost more than 20 percent of clicks in 90 days, and updates weak sections while keeping the same URL, backlinks, and indexing intact.

Google Search Console decay view inside Leafpad, showing which posts lost traffic over the last 90 days.

Most of your traffic is leaking from posts you forgot about

Every blog has decay. The post that ranked fourth in 2024 is on page two now. The one that brought 800 clicks a month in January is bringing 200. You did not write a bad post. The internet just moved on, and you did not move with it.

Refreshing old content is the highest-ROI thing most teams ignore. It is faster than writing new posts and the page already has authority. The problem is no one has time to do it manually across 60 or 200 articles.

Ranked fourth in 2024

On page two now.

800 clicks in January

200 clicks now.

Highest-ROI motion

Refreshing old content is faster than writing new posts because the page already has authority.

Manual work does not scale

No one has time to refresh 60 or 200 articles by hand.

How it works

How the refresh layer works

StepTriggerAction
Watch GSCPull click and impression data on every indexed post and spot 90-day decay.Flag any page that lost more than 20 percent of clicks over the last 90 days.
Rank recovery potentialPrioritize pages that used to drive meaningful traffic and are close to winning again.Move page-two opportunities and larger traffic recoveries to the top of the queue.
Rewrite the pageKeep the original URL, backlinks, and indexing in place while updating what fell behind.Refresh stale statistics, weak openings, missing FAQs, and missing internal links.

Signals that decide what moves first

90-day decay window

Refresh

Leafpad watches for the slow drop in clicks that signals a page is losing ground.

20 percent threshold

Refresh

Any page that loses more than 20 percent of clicks in 90 days gets flagged.

Recovery potential first

Refresh

A page that fell from 1,000 clicks to 400 matters more than one that slipped from 12 to 9.

Page two wins

Refresh

Posts sitting on page two move up first because they are usually the easiest traffic wins.

URL stays intact

Refresh

Leafpad keeps the URL, backlinks, and indexing so the page keeps its existing authority.

What gets repaired

Refresh

Stale stats, outdated examples, weak openings, missing FAQs, and missing internal links.

We watch your Google Search Console

Once you connect GSC, Leafpad pulls click and impression data on every indexed post and looks for decay (the slow drop in clicks that means a page is losing ground). The system flags any page that lost more than 20 percent of clicks over the last 90 days.

We pick the refreshes worth doing

Not every decaying page is worth fixing. Leafpad ranks the list by recovery potential. A page that used to bring 1,000 clicks and now brings 400 is high priority. A page that brought 12 clicks and now brings 9 is not. Pages sitting on page two of Google move up first, because they are the easiest wins.

We rewrite the page, not the URL

Leafpad keeps the URL, the backlinks, and the indexing. We update what is broken: stale statistics, outdated examples, weak answers in the first 150 words (the part AI engines extract first), missing FAQs, missing internal links. The post comes out modern without losing what was already working.

You set the rules

Leafpad lets you decide how the refresh layer behaves so automation stays inside the boundaries your team actually wants.

How often Leafpad sweeps for decay (weekly is default)

How big the drop has to be before a refresh fires

Whether you approve refreshes before they go live

Which sections to never touch

All settings are configurable from your dashboard at any time.

AI search

Why refresh matters for AI search

AI engines cite fresh content first. The Aggarwal et al. GEO paper (arXiv:2311.09735, KDD 2024) found that the combined effect of adding citations, quotations from credible sources, and statistics improved AI citation visibility by over 40 percent across diverse queries. Old posts get skipped not because they are wrong, but because they look stale. Refreshing them puts you back in the AI quote pool.

This is part of the same EEAT system (expertise, experience, authoritativeness, trustworthiness, the four things Google uses to decide if a source is credible) that Leafpad builds across every post with named author entities and Person schema.

What gets fixed in a refresh

Stale statistics

Replace outdated numbers before AI engines skip the page as old news.

Outdated examples

Swap examples that made sense a year ago for ones that match the live SERP now.

Weak first 150 words

Tighten the top of the article where AI engines extract answers first.

Missing FAQs and links

Add the FAQs and internal links that modern pages need to stay competitive.

FAQ

Questions teams ask before turning this on

Recover your old traffic with Leafpad