A run is arithmetic with a short piece of writing at the end: the same handful of calls per domain, movers ordered by distance travelled, a cut where your digest style says to cut, and anything crossing onto the first page or falling off it kept whatever its size. That is a well bounded loop, the sort of thing OpenCode is easy to point at, with the model behind it left to you.
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Rank digest 18 August 2026
Rank history shows visibility moving from 3,410 to 3,602 overnight. Kotiteatteri kaiuttimet went 11 to 3 on the category page, langattomat kuulokkeet 8 to 6, and levysoitin huolto slipped 4 to 9. Two vinyl storage terms appear in the top pages report for the first time. The pull for hifikauppa.fi returned its overview with no keyword movement attached.
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Semrush
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Tracked domains
The domains this digest covers, yours first and then any competitor worth watching, each with the Semrush database it should be read in, plus the sections of the site or kinds of terms you care about most.
Digest style
What lands in Slack each morning: which domain leads, how far a keyword has to travel before it earns a line, how many movers you want in each direction, and who to tag when a pull comes back empty.
Runs on OpenCode
Preselected for this page — connect your OpenCode account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
A three place slip deep on page four is noise; the same slip across the first page boundary is not. Ordering by movement is what makes a long list readable.
Where two of your urls swap on one term the digest says the ranking page changed and names both. Printed as a number alone it looks like a loss, and the fix goes to the wrong page.
Yes, since each domain is listed with the database it should be read in, so one digest can carry a UK domain and a German one. Every extra domain and database pairing is another pull and another set of units, which is the honest constraint. Most teams start with their own domain in one database and add competitors after a week of reading.
Free to start. Guided setup, a test run against staged conversations, and it's live.