Posts in your voice, about things your customers actually search for. Each arrives as a pull request: approve it with one tap, or review it like code. Ignore it and nothing happens.
The homeowner’s winterizing checklist
Every draft is checked before a PR may open: a 1,600-word floor, heading structure, alt text on every image, at least one internal link, and forty banned phrases. Failures never become PRs. It runs offline, so it never checks whether a link answers — the build does that afterwards.
writer-gate: 0 failures required
A post PR adds the post and nothing else — no config churn, no vendored assets, nothing to untangle if you close it. Everything the draft had to clear to become that file is listed below.
the diff: one file, and what it had to clear
Owners approve by email with one tap. Developers review the PR like any other. Either way, the approval is recorded: who, when, how.
We fetch the published page and look for the post’s own text in it, so a 404 that happens to list recent posts can never read as proof of life. Index tracking runs nightly on top of that, once your Search Console is connected. Regret a post? Revert the merge.
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, 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.
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 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.
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, and every expiry is recorded on our side where we can see it. 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. 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.
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.
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.
Free while we finish setting up billing. No card, and cancel any time from your own account page.