A droid that watches your search presence the way you would if you had the time: it tracks where your key pages rank, catches the drops and the competitors out-publishing you, files a brief for the pages worth defending, and flags only the moves that actually threaten traffic — so an SEO slide gets caught in days, not in next quarter’s numbers.
Does
Tracks rankings, briefs the fixes
Where
Content-led SaaS, ~6-person marketing
Reaches people on
Slack
Works inside
The web, Airtable
Runs
Daily rank sweep + on every drop
01The situation
A page slips off the first results page weeks before anyone notices.
Rankings slipped in silence. A page would drift from the top of the results to the second page over a few weeks, traffic would quietly follow, and nobody noticed until a monthly report showed the dip — long after the moment to act had passed. Checking rankings by hand across dozens of keywords was tedious enough that it happened rarely.
Meanwhile competitors kept publishing fresher, deeper content and quietly overtaking pages that used to win. The team needed a daily watch on their search presence — and a brief in hand the moment a page started to slide, not a post-mortem a quarter later.
02How it works
How the droid took it on.
Rather than hope someone checks rankings, the team handed the watch over. Every morning the droid checks every keyword, diagnoses the drops, briefs the refresh, and escalates only a shift big enough to move strategy.
TASK#341SEO & ranking watchstanding
trigger
Every morning at 6:00, a full rank sweep
also
Any meaningful drop, plus a Friday digest
scope
Every tracked keyword and key page
runs as
A contained droid action per sweep or drop
memory
A ranking history per keyword, with the cause of each move
Set up once, in plain language: “check our rankings every day, tell me when one slips and why, brief the refresh, and only pull me in for a change big enough to move strategy.” The droid turned that into a standing job, the SEO analyst a small content team never had.
FIG. 1The durable task, exactly as it exists in the runtime.
Every sweep trips the same loop:
01Sweep fires6:00am, daily
02Droid wakesJust for the sweep
03Checks rankings + memoryResults, competitors, history
04Diffs the snapshotWhat moved, and why
05Briefs the fixRefresh brief in Airtable
06Material?Steady → log it · Drop → brief a refresh · Strategic → loop in a human
07Posts to #marketingThe ranking note
…then the next run picks it up, two hours later.
FIG. 2The loop each run walks.
03Ongoing handling
How it ran, keyword after keyword.
Here’s a week of rank-watching as it actually unfolded, down to how it reached for each tool. Only the one strategic SERP change ever needed a person.
Mon 6:00amsweep
Checked 48 keywords and caught one page slipping from #3 to #8 overnight.
Mon 6:20amdiagnose
Traced the drop to a competitor's fresher, deeper guide published last week.
Mon 6:35ambrief
Filed a refresh brief with the gaps to fill and the angle to reclaim the spot.
Wed 10:00amquestion
Answered a trend check on a climbing keyword and advised where to focus instead.
Thu 2:30pmstrategicescalated
Escalated a new SERP feature threatening the top traffic term, with the stakes and options.
Fri 4:00pmSEO digest
The week reconciled: 5 up, 2 down (briefed), 1 strategic shift escalated. Traffic trend still up.
The morning sweeps, the drops they catch, and a marketer's question land on the left. Watch the droid pick up each one and work it across the web and the tracker, bringing in a human only for the shift that warrants it.
The result
What changed, by the numbers.
Days, not quartersto know a page slipped
Cause, not just rankeach slip checked against the likely reason
Briefs in handrefreshes queued rather than merely flagged
Traffic defendedpages reclaimed before they bleed out
An illustrative workflow built from real product mechanics. The connected apps, the schedules and the run handling are how a droid actually works; the companies, the people and the figures are composites rather than a customer's numbers.
Try this workflow
Run this workflow yourself.
Copy the brief below and paste it into Unify. It’ll walk you through the prerequisites, connect what it needs, and stand the workflow up with you.
Workflow brief
I run content at a content-led SaaS company, and our rankings slip in silence. A page drifts off the first results page over a few weeks, traffic follows, and nobody notices until a monthly report shows the dip, long after the moment to act. Checking rankings by hand across dozens of keywords is tedious enough that it rarely happens, and meanwhile competitors keep publishing fresher content and overtaking pages that used to win.
Own SEO ranking watch. Apps/channels: the web (rank checks, search results, competitor content), Airtable (a rank tracker, one row per keyword with position history and the cause of each move), Slack #marketing (the running feed).
Run a full rank sweep every morning, react to meaningful drops, and post a Friday digest. On each sweep:
1. Check where we rank for every tracked keyword and pull the current results.
2. Diff against yesterday and update the tracker with what moved up, down, or held.
3. When a page drops meaningfully, investigate why, which is usually a competitor publishing something fresher or deeper.
4. Write a refresh brief (the gaps to fill, sections to add, the angle to reclaim) and queue it for the writer; post a short note to #marketing.
Use judgment on what reaches a person: log routine moves, brief the fixable drops yourself, and for a strategic shift, like a new SERP feature or a major competitor push on a top term, escalate to the head of content with the stakes and options. Keep a ranking history per keyword with the cause of each move, so trends have an explanation.
