Skip to content
Create & optimiseContent refreshUpdated 12 November 2026

Update old blog posts to rank better

Finds posts losing clicks in Search Console, or takes your URL, and rewrites it in place with missing subtopics, fresh facts and a direct intro. Free plan.

Start this playbook free

Free to start · No card needed · 20 free credits. The question waits in the chat until you press send.

At a glance

Search Console
Search Console: helps

Works without it. Connected, the agent adds your own clicks, impressions and positions to the answer.

Plan
Every plan, free included
Smallest charge
3 credits. See pricing

A free account starts with 20 credits and is topped up to 3 each day. A request that takes several steps costs more than the smallest charge. Typical ranges are on the pricing page.

Ask it like this

What this playbook does

Content refresh rewrites an article that is slipping, or one that was always thin, while keeping its URL and the parts Google already rewards. The agent updates the facts and dates, adds what today's top results cover and your post does not, and rewrites the opening so it answers the search straight away.

Most sites have a few posts that brought steady traffic for a year and then began to fade. Rewriting one can be less work than a new post, because the page already has searches it shows up for and links pointing at it.

How the agent works through it

  1. Finds the posts worth refreshing. With Search Console, it compares clicks per page over the last 28 days with the 28 before and looks for pages whose clicks fell while impressions held steady: Google still shows them, but fewer people choose them. Or it takes the URL you give.
  2. Reads the searches that post currently gets, so the sections that already rank are kept rather than rewritten away.
  3. Reads the post itself, then checks what the current Google results cover for its topic, along with the other ways people phrase the search. On an India-market site that includes Hindi and Hinglish phrasings when the English results show demand for them.
  4. Rewrites on the same URL: adds the missing subtopics, replaces old facts, prices and years, and rewrites the introduction to answer the search in its first lines.
  5. Saves the rewrite as a document and explains in the chat what changed and why.

What you get back

A refreshed article saved in Documents, plus a short explanation in the chat of what changed and why.

An example of the shape of the answer, for a made-up site (not real data):

PostWhat happenedKeptAdded or changed
/blog/best-time-to-visit-goaClicks down, impressions about the sameMonsoon section (ranks for "goa in july")Festival dates moved from 2023 to 2026; new section on shoulder-season prices; first two lines now answer "October to March"
/blog/goa-homestay-vs-hotelThin, 400 wordsComparison tableQuestions on family stays and parking, answered under their own headings

How to pick what to refresh

A fall in clicks with steady impressions usually means the snippet or the content lost out to something fresher, which a rewrite can fix. A fall in impressions as well points to a ranking or demand problem; the performance analysis playbook is the better first step there, because it separates seasonal dips from real losses. A post that never got traffic at all may need a new angle rather than an update.

What it needs

  • Your site in Qelvra, with the posts on it publicly readable.
  • Search Console, ideally. It lets the agent find decaying posts for you and see which searches each post ranks for, so it knows what to protect. Without it, give the agent the URL of the post you want refreshed; it can still rewrite it against the current results, but it is guessing at which sections earn the traffic.
  • WordPress or Shopify connected, only if you want the rewrite put on the live post from the chat.

Where it stops

  • The rewrite is saved as a separate document. Your live post is untouched until you paste it in, or ask the agent to update the WordPress post or Shopify blog article, which needs your approval when the post is live.
  • It keeps the URL. If you want to merge two posts or move one, plan the redirect yourself; the agent can tell you which to keep but does not set redirects as part of this playbook.
  • Search Console only shows the searches Google reported for the period read. Very small posts may have too little data to tell a decline from noise.
  • A refresh cannot add first-hand detail it does not know: new photos, your own numbers, a quote from a customer. Add those before you publish.

Frequently asked questions

Should I change the date on a refreshed post?

Change the "updated" date when the content really changed, as it will after a refresh. Leave the original publish date alone. Google asks for dates that reflect real changes (publication dates, read 13 November 2026).

Will a refresh lose the rankings the post has now?

The main risk in a rewrite is cutting the sections that earned the traffic. With Search Console connected, the agent reads the searches the post already appears for and keeps those sections. Keep the URL and title close to the old ones unless the answer says why to change them.

How many posts should I refresh at once?

Start with the two or three with the biggest drop. Refresh them, wait a few weeks, and compare their clicks with the same period before, so you know the work helped before you do more.

Can it tell me which posts are decaying without a URL from me?

Yes, if Search Console is connected. It compares the last 28 days with the previous 28 page by page and lists the pages where clicks fell but Google still shows them.

Related playbooks

Read more on the blog

Run it on your site.

Free to start · No card needed · 20 free credits. The question waits in the chat until you press send.