Article refresh
How Content Autopilot decides an article needs updating, what a refresh changes, and how you review the difference before it replaces the live article.
An article starts going out of date the day it is published. Refresh finds the ones that need attention, rewrites what has changed, and shows you the difference before anything goes live.
How an article gets flagged
With Search Console connected, from what Google reports for the page:
- Clicks have fallen compared with the period before.
- Its average position has dropped.
- It sits at a good position and gets few clicks, which usually means the title or description is not earning them.
- It appears for searches it does not answer.
Without Search Console, from the article itself:
- The title carries a year that has passed.
- It has not been updated in a long time.
Each reason is shown next to the article, so you can see why it was picked and ignore the ones you disagree with.
What a refresh does
It researches the topic again with live search, updates facts and figures that have moved, adds what is missing for the searches the page shows up for, and keeps the address the same. The claims and sources list is rebuilt for the new version.
Reviewing it
The new version is held next to the old one with the changes marked. You approve it or discard it. Nothing replaces the live article until you approve, unless you have turned review off for the site.
Where it goes
To the same place the original went. On WordPress the existing post is updated; on GitHub the same file is committed again; a webhook receives an update_article event. The hosted blog copy is updated too.
From an AI assistant
Over MCP, list_refresh_candidates returns the flagged articles with their reasons, and refresh_article starts one.