Customer actions lead, once they can be counted.
A connected report headlines calls and direction requests. Until then it says “not connected yet”. It never invents a number.
What was done and what it changed, in Google’s own numbers. When a page slips, the fix shows up as a pull request, not a line item.
Your June report
412
clicks from Google search
2
pages we flagged as slipping
What we fixed, and whether it worked
28 days before vs 28 days after, with a 7-day gap so reindexing isn’t credited to either side.
A connected report headlines calls and direction requests. Until then it says “not connected yet”. It never invents a number.
Four detectors run on your Search Console history: decay, striking distance, starved clicks, cannibalization. Each finding becomes a refresh PR with the evidence in it.
28 days before against 28 days after, with a settling gap. The verdict prints either way. A page with too few clicks gets no verdict rather than a noisy one.
A number that wasn’t measured is never printed. “Not connected yet” means exactly that.
The ones people ask before letting anything near a site they’re responsible for.
Never. A merge needs a recorded approval: your one-tap email link, your PR review, or you merging it yourself. Silence means nothing ships.
No. Not because we’re careful, but because we’re constrained. Nothing reaches your site until you merge it, and GitHub blocks CI access server-side. The worst case is a PR you close.
No. Month to month, cancel any time. Founding rates lock in for as long as you stay. Leaving is one uninstall, not a migration.
You keep everything. It was always in your repo, so there’s no export because there was never an import. Uninstall the App and our access is gone instantly. Two footnotes: you remove our Google manager access yourself if you used Local (we remind you), and we keep the log of your approvals. That log is your own audit trail.
No. The listed price is the whole price: no per-word charges, no meters, no setup fee. A product that isn’t live yet, like Local, is never billed at all.
No. Owners approve from email with a preview and a one-tap link. Developers can review every diff like any other code.
One reminder, then the cycle quietly expires and the slot rolls forward. Nothing is lost. If approvals keep expiring, a person reaches out. We never treat silence as a yes.
The opposite bet. Volume tools dump 30 unreviewed articles a month, the exact pattern Google now targets. We ship a few posts a human explicitly approved, with the audit trail to prove it.
Content and Insights, today. Local is fully built and waiting on Google’s API approval; create your account and we onboard you the day it clears. Everything further out lives on the roadmap page, not the price list.
Content: three GitHub permissions on the repos you choose. Insights: a read-only Search Console connection. Local: our Google account added as a manager on your profile, removable any time. None of them ever hold CMS logins or deploy keys.
Blog writing: git-backed sites (Astro, Hugo, 11ty, Jekyll, Next) on Cloudflare Pages, Vercel, or GitHub Pages. Local: any platform at all, Wix and WordPress included.
We re-measure every change in your own Search Console data, 28 days before against 28 days after, and print the verdict either way. When a change loses, your report says loss.
Sign up, install the app, and the first pull request follows. Prefer a person first? Email us.
Cancel any time. Everything stays in the repo.