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.
early accessReads your own Search Console data. You add our Google service account to your property, and remove it whenever you like.
A monthly report your client actually understands.
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
/services/emergency-repair+38% clicksWin
/aboutno changeFlat
28 days before vs 28 days after, with a 7-day gap so reindexing isn’t credited to either side.
Calls & direction requestsnot connected yet. Never a fake 0.
illustration with sample data — not a real client’s report
MergePress Insights in detail
Decay detection, from your own data.
Four detectors run on your Search Console history: decay, striking distance, CTR gap, cannibalization. Each finding becomes a refresh PR with the evidence in it.
Every fix gets a verdict: win, flat, or loss.
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.
No fake zeros. Ever.
A number that wasn’t measured is never printed. “Not connected yet” means exactly that.
Fair questions
The ones people ask before letting anything near a site they’re responsible for.
Do you ever auto-publish?
Never. A merge needs a recorded approval: your one-tap email link, your PR review, or you merging it yourself. Silence means nothing ships.
Can you break my website?
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.
Is there a contract?
No. Month to month, no minimum, no notice period. Founding rates lock in for as long as you stay. There is no cancel button in the app yet — today you tell us and we stop, and nothing is charged in the meantime because billing isn’t on. Leaving is one uninstall, not a migration.
What happens when I cancel?
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.
Are there hidden fees?
No. The listed price is the whole price for that site: no per-word charges, no meters, no setup fee, and your first Google Business Profile is in it. What is billed on top is countable and printed here — another site, or a second profile on the same one. A product that isn’t live yet is never billed at all.
Do I need to know git?
No. Owners approve from email with a preview and a one-tap link. Developers can review every diff like any other code.
What if I never get around to approving?
One reminder, then the cycle quietly expires and the slot rolls forward. Nothing is lost, and every expiry is recorded on our side where we can see it. We never treat silence as a yes.
Isn’t this just AI slop?
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.
Which products can I use today?
Content and Insights. Both need one setup step before anything can run: Content needs the GitHub App installed on a repo, and Insights needs our Google service account added to your Search Console property — until it is, the report prints “not connected yet” rather than a number. Local is fully built and waiting on Google’s Business Profile 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.
What do the products need access to?
Content: three GitHub permissions on the repos you choose. Insights: our Google service account added as a user on your Search Console property — the scope Google grants there also permits sitemap submission, which is the only write we make with it. Local: the same Google identity added as a manager on your profile. You remove either one whenever you like. None of them ever hold CMS logins or deploy keys.
Which platforms do you support?
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.
How do I know any of this is working?
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.
Start in a few minutes.
Sign up, install the app, and the first pull request follows. Prefer a person first? Email us.
Start free
Free while we finish setting up billing. No card, and cancel any time from your own account page.