Blog refresh finder
By Toolspoke
Finds blog posts losing Google clicks each week and posts a ranked list of what to update in each, from Search Console data.
Needs a Toolspoke account. You choose which project it installs into.
- WordPress + Google Search Console + Slack
- Required integrations
- Runs on a schedule
- Mondays at 10am by default
- Post one message
- What its last step does
- Some actions can delete
- 5 of 31 actions in its tools
On this page
The short version
- What it is
- A ready-made Toolspoke agent that finds blog posts losing Google clicks and tells you what to update in each.
- What it reads
- Search Console clicks by page and query for the last 28 days, the 28 before and the same period last year, and the matching WordPress posts.
- Where it posts
- One Slack channel, chosen when you set it up.
- What it suggests
- The queries each post lost, out-of-date years or claims, missing sections and internal links to add.
- How often
- Mondays at 10am once you switch it on.
- What it never does
- Edit, publish or comment on a post, or submit or delete a sitemap.
- What you need
- A Toolspoke account, a verified Search Console property, a WordPress site and a Slack workspace.
What Blog refresh finder does
Blog refresh finder is an AI agent that reads Google Search Console every Monday, finds the blog posts losing clicks, and posts a ranked list to Slack of what to update in each.
Blog posts decay. A post that brought steady traffic for two years slowly slips as competitors publish newer pages, the year in its title goes stale and the questions people search for change. Nobody notices until the traffic is gone.
Search Console has the data to spot it early, but comparing every post across two periods, then working out which queries it lost, is a job most teams never get round to.
Blog refresh finder compares each post's clicks over the last 28 days with the 28 before, and with the same period last year where there is data. For each post losing a fifth or more, it finds the queries that fell, reads the post in WordPress, and says what looks out of date or missing.
In practice, every Monday you get one message:
- The ten posts losing the most clicks, with before and after figures
- The searches each one lost, with position then and now
- Out-of-date years, missing sections and internal links to add
- A note where the fall looks seasonal
How it works
Blog refresh finder works in four steps each Monday: it compares clicks by page, finds what each decaying post lost, reads the post in WordPress and posts one ranked list. All of it comes from the agent's written instructions, which you can read and edit after you install it.
Step 1: Compare clicks
Clicks per blog page, this 28 days against the 28 before and last year.
Step 2: Find lost queries
For each decaying post, the searches that fell most.
Step 3: Read the post
Its title, dates and headings, matched by slug.
Step 4: Post the list
The top ten by clicks lost, each with what to update.
It allows for Google's reporting lag
Search Console data is usually complete only to about two days ago, so the current window ends there. The post states all three windows it compared.
It separates decay from seasons
A post about tax returns falls every summer. When a post's clicks are level with or above the same window last year, the agent says the fall is probably seasonal and ranks it lower.
It only suggests what the data supports
Lost queries the post does not answer, a year in the title older than this one, a post not modified in over a year, questions no heading covers, and related posts it does not link to. It reads the post with get_post and never guesses at content it has not read.
It does not touch the site
The WordPress connection can create and update posts and the Search Console connection can submit sitemaps. The agent is told never to use any of them. The limits are listed under what it will never do.
What a Monday message looks like
A message from Blog refresh finder is a single Slack post. It states the windows, then lists the posts losing the most clicks, each with the searches lost and what to update.
Taskhive
Channels
- # content
- # marketing
- # seo
- # general
# content
28 days to 19 Oct against the 28 before, and the same 28 days last year. 214 posts checked, 9 losing 20% or more.
1. Best project management tools for 2024
- Clicks 1,840 to 990 (down 46%). Lost: best project management tools 2025 (position 4 to 11), project management software comparison (6 to 14).
- Update: the title and headings say 2024. Last modified 14 months ago. Add a comparison table, which the lost queries ask for. Link from Gantt charts explained.
2. How to write a project brief
- Clicks 720 to 495 (down 31%). Lost: project brief template (position 3 to 8), project brief example (5 to 9).
- Update: no section offers a template or a worked example. Add both.
Probably seasonal
Year-end planning checklist: down 38% on last month, but up 5% on the same window last year.
- Biggest losses
Posts ranked by clicks lost, with the queries behind the fall and the concrete updates that match them.
- What to update
Only what the data shows: lost queries, stale years, missing sections and internal links.
- Seasonal
Posts whose fall matches last year's pattern. Listed so nobody rewrites a post that will recover on its own.
Why some weeks are short
If no post lost a fifth or more of its clicks, the agent posts one line saying so, with the number of posts it checked. A healthy blog gives short messages.
If Search Console cannot be read, it posts that once and stops. If WordPress cannot be read, it posts the losing pages and their lost queries without the post checks, and says why.
Who uses Blog refresh finder
Blog refresh finder suits any team with a WordPress blog that has been publishing long enough for older posts to decay. The examples use made-up names.
A content manager with a big archive
Ingrid Larsen looks after 400 posts and used to guess which to refresh. Now the Monday list tells her which are losing traffic and why.
An SEO lead proving refreshes work
Rahul Menon tracks whether last month's refreshes recovered. The lost queries and positions give him a before and after for each post.
A writer picking the next update
Amara Osei writes two refreshes a week. The suggested updates mean she starts with the missing sections, not with research.
A founder with a seasonal product
Gareth Price sells planning software that peaks in January. The seasonal note stops his team rewriting posts that recover every winter.
What Blog refresh finder connects to
Blog refresh finder connects to three tools: it reads Search Console and WordPress and posts to Slack. You connect each one yourself, and Toolspoke stores the connection encrypted, so the agent never sees the credential.
WordPress
RequiredRead and write a WordPress site through its REST API - posts, pages, taxonomy, media, people and comments.
Authentication: Application password
Google Search Console
RequiredQuery search traffic, inspect how Google indexed a URL, and manage sitemaps.
Authentication: Sign in with Google
Slack
RequiredSearch conversations and send messages to your workspace.
Authentication: Bot token
| Tool | What Blog refresh finder does | What it cannot do |
|---|---|---|
| Google Search Console | Reads clicks, impressions and positions by page and by query (query_search_analytics). | Read properties the connected Google account has no access to. It can submit and delete sitemaps, and this agent's instructions forbid both. |
| WordPress | Finds and reads published posts (list_posts, get_post). | Read posts it is not allowed to see. It can create and update posts and create comments, and this agent's instructions forbid all three. |
| Slack | Posts one message with send_message, to a channel. | Delete messages: the connector has no delete action. It can also edit, schedule and react, and the agent is told to do none of them. |
That the agent does not edit your blog or your sitemaps is an instruction, not a lock. If you want a lock, switch off WordPress's create_post, update_post and create_comment and Search Console's submit_sitemap and delete_sitemap in your project. The access control guide explains how.
For WordPress you can also connect an account with a role that cannot publish, such as Contributor, so the site itself refuses an edit to a published post.
What Blog refresh finder will never do
Blog refresh finder is told never to create, update or publish a post, never to comment, and never to submit or delete a sitemap. It suggests, and a writer makes the change.
- Create, update or publish a post or page, or create or reply to a comment.
- Submit or delete a sitemap, or ask Google to reindex anything.
- Read a password-protected or draft post, or quote one.
- Promise that a refresh will bring the clicks back.
Why it does not edit posts
A refresh is writing: it needs your voice, your product knowledge and a judgement about what to cut. An automated edit to a published post goes straight to readers and to Google. The agent lists what to update, and a writer does it in WordPress.
Why it leaves sitemaps alone
Submitting or deleting a sitemap changes what Google crawls. That belongs to whoever owns the site's technical SEO, not to a weekly report.
Why it never promises a recovery
A refreshed post may or may not win its clicks back. The agent says what could help and why.
If something goes wrong
If Search Console cannot be read, post that once and stop. If WordPress cannot be read, post the decaying pages and their lost queries without the post checks, and say why. If no post lost 20% or more, post one line saying so, with the number of posts checked.
These are written into Blog refresh finder's instructions. They guide the agent, but they are not a permission. What it is allowed to touch is set by the access you grant.
Blog refresh finder reads Search Console and WordPress and reports what it finds. Every edit to your blog stays with a person.
When Blog refresh finder runs
Blog refresh finder runs on Mondays at 10am, but only after you switch its schedule on. It arrives switched off, so nothing runs and nothing is charged until you decide.
- Each run compares the last 28 days with the 28 before and with last year.
- It lists the ten posts losing the most clicks.
- If no post lost a fifth or more, it posts one line.
- If Search Console cannot be read, it posts that once.
Each run uses model credit from your workspace balance, so it makes one run a week. A large blog with many decaying posts costs more, because there is more to read. The Search Console, WordPress and Slack calls themselves are free.
Your copy is an ordinary agent in your project. You can pause its schedule there, run it once on demand, change the day and time and edit its instructions. The agent's page lists recent runs and their cost.
How to set up Blog refresh finder
To find posts worth refreshing, add Blog refresh finder to a Toolspoke project, connect Search Console, WordPress and Slack, set your blog path and switch on the schedule. It takes a few minutes, and nothing runs until the last step.
Step 1: Create a Toolspoke account or sign in
Choose Use this agent. If you are new, you will be asked to sign up first, and you come straight back to this agent afterwards.
Step 2: Add it to a project
Pick the project it should live in. You get your own editable copy, and you can see the three tools it brings before anything connects.
Step 3: Connect Google Search Console
Sign in with a Google account that has access to your property. The agent reads the property you name.
Step 4: Connect WordPress
Connect your site with an application password. An account that cannot publish, such as a Contributor, is enough to read posts.
Step 5: Connect Slack and set the details
Sign in with Slack, then name the channel, your blog path such as
/blog/, and if you like the minimum clicks a post needs to count.Step 6: Switch on the schedule
The schedule arrives switched off. Run it once to see a message, then switch it on.
Make Blog refresh finder fit your blog
Blog refresh finder's instructions are plain English and you can edit them after you install it. Installing copies the agent, so your edits stay with your copy. Open the agent in Toolspoke and tell the builder what to change, and it rewrites the instructions.
Paste any sentence below into the builder chat, or say the same thing in your own words.
List posts that lost 10% or more of their clicks.
Look at pages under/guides/instead of/blog/.
Run on the first Monday of each month.
This changes when the agent wakes up, so the builder edits its schedule, not the instructions.
List the top 20 posts instead of 10.
Only count clicks from the United Kingdom.
None of these edits needs more access or touches the Never rules. They change what Blog refresh finder is told, not what the connections allow.
How it compares to other options
Blog refresh finder beats the alternatives when you want a weekly list of decaying posts with the reason and the fix. It loses to them when you want a full SEO audit or a live dashboard.
| Compared on | Blog refresh finder | Search Console reports | An SEO platform | A quarterly content audit |
|---|---|---|---|---|
| Finds posts losing clicks | Yes, weekly | If you compare dates | Yes | Yes, quarterly |
| Names the queries lost | Yes, per post | If you filter per page | Yes | Sometimes |
| Reads the post and suggests updates | Yes | No | Some do | Yes |
| Allows for seasons | Yes, against last year | If you compare | Some do | If you check |
| Can edit your posts | Told not to | No | Some can | Up to you |
| Full technical SEO audit | No | Partly | Yes | Sometimes |
| Setup effort | Connect three accounts | None | A subscription and setup | Days of work |
Search Console's own reports have every figure this agent uses, and are better when you want to explore. The work of comparing every post and reading each one is still yours.
An SEO platform is better when you need rank tracking, backlinks and site audits too. It costs a subscription, and its suggestions are not based on reading your own post.
Frequently asked questions
Can Blog refresh finder edit my posts?
It is told never to. The WordPress connection can create and update posts and add comments, so for a lock, switch those actions off in your project or connect an account that cannot publish (how access works).
Does it submit sitemaps or request indexing?
No. The Search Console connection can submit and delete sitemaps, and the agent is told never to. You can switch both off in your project.
How does it decide a post is decaying?
A post with at least 50 clicks in the earlier 28 days, by default, that lost 20% or more in the latest 28. Both figures can be changed.
What if the drop is seasonal?
If clicks are level with or above the same window last year, it says the fall is probably seasonal and ranks the post lower.
Does it work without WordPress?
Partly. If WordPress cannot be read, it still posts the losing pages and their lost queries, without the post checks. For another CMS, ask the builder for a version that reads it.
Why are the figures two days old?
Google's Search Console data is usually complete only to about two days ago, so the agent ends its window there.
Is Blog refresh finder free?
It has no price of its own, and every Toolspoke plan includes agents. Tool calls cost nothing, but each run draws on your usage balance. Pricing has the details.
Catch decaying posts before the traffic is gone
Connect Search Console, WordPress and Slack, set your blog path and switch on the schedule. Your first list lands on Monday at 10am.