Refresh the pages that actually slipped.
It checks the page’s real Search Console position and only writes a refresh brief for the ones that slipped.
6 steps · runs on demand · added to your workspace as a draft
Branch early
Healthy pages cost nothing. The slipping one gets a brief.
Most pages are fine. The run should find that out before it spends anything.
01 · Three pages, their real position over ninety days.
02 · Two held. The branch ends the run for them — nothing spent.
03 · One slid from fourth to eleventh. The run continues.
04 · It reads who overtook you, not just that you fell.
05 · The brief is ordered by what actually cost the position.
Search Console · average position90 days
- /pricing3 → 3healthy · run stops
- /docs/setup5 → 5healthy · run stops
- /blog/aeo-guide4 → 11slipped · continue
Who overtook you
rival-a.com/aeo-guide
Published five weeks ago. Opens with a definition, carries a comparison table, cites a 2026 dataset.
Refresh brief · by what lost the position
- 1Answer the question in the first 40 words
- 2Add the comparison table they have and you don't
- 3Replace the 2024 figures with dated, current ones
What it does
Pre-built, then yours to customize.
Add it to your workspace in one click. Sensible defaults and example inputs are already filled in.
Reads from · writes to
- Google Search Console
- Web search
The template, step for step
- Trigger
- GSC metrics
- Branch (if/else)
- LLM call
- Notify
- Notify
Added to your workspace as a Draft, with example inputs filled in. Every step is yours to change.
- 01
Driven by real Search Console position
- 02
Branches early, so healthy pages cost nothing
- 03
Reads who overtook you, not just that you fell
- 04
Refresh brief prioritised by what lost the position
In, and out
You give it a page URL. This is what comes back.
- Shape
- 6 steps
- On demand
- run mode
- 1
- click to add
- /blog/aeo-guide4 → 11brief written
- /pricing3 → 3skipped
- /blog/geo-tools6 → 14brief written
Illustrative output.
The steps
What happens on every run.
- pull_search_console
- branch_on_decay
- fetch_current_page
- read_who_overtook_you
- write_refresh_brief
- save_or_log_healthy
6 steps · Runs on demand0 / 6
Run history keeps each step's output and runtime, and the input of every step that completed.
Before & after
The time this gives back.
The templates that publish put a Human review step before the CMS step, and nothing ever posts to Reddit for you. Review is a step, not a lock: a workflow you build or edit can publish or message a channel without one, so add it wherever you want the sign-off.
Doing it by hand~3.5 hrs
Content refresh from GSC decay~40 min
Bars to scale: the time a person spends, each way.
Doing it by handyour team
- Checking positions page by page~1h
- Working out who overtook you~1h
- Writing the refresh brief~1.5h
Per page, by hand~3.5 hrs
Content refresh from GSC decayLive
- Agent checks and branchesauto
- Agent reads the competitionauto
- Agent writes the briefauto
- You ship the refresh~40m
One agent run~40 min
FAQ
Questions, answered.
Slipping off page one for a query the page used to hold. The Branch step uses the real Search Console position, so it is measured rather than assumed.
The run logs it and stops. That is deliberate — a refresh agent that produces a brief for every page trains you to ignore it.
No. It produces a prioritised brief. Drafting is the article agent, and publishing still gates on human approval.
Free to start
Add this agentto your workspace.
Start free. Customize the steps, run it on demand or on a schedule, and approve anything that ships.