A writing gate stands between the AI and you.
Every draft is checked before a PR may open: substance, structure, alt text, working links, and a banned-phrase list for AI filler. Failures never become PRs.
writer-gate: 0 failures required
early accessWorks with sites built on Astro, Hugo, 11ty, Jekyll, or Next.js.
We write your blog. You approve every word.
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
mergepress/post-winterizing-checklist+412 −0
Passed the writing gate0 failures
Committed by mergepress[bot]Verified
Approve & merge
MergePress Content in detail
The invisible plumbing rides in the same diff.
Sitemap, schema, internal links, an IndexNow ping on merge. You approve the post. The SEO mechanics come with it.
the diff: what rides along with every post
every-post.diff+5 guarantees
1## alongside the post you approved:
2+sitemap.xml, with a lastmod that only changes when content does (truthful lastmod)
3+Article + Organization schema, valid JSON-LD (rendered, not promised)
4+internal links from your homepage and recent-posts block (the #1 fix for “Discovered, not indexed”)
5+descriptive alt text on every image (accessibility and image search)
6+IndexNow ping the moment the PR merges (Bing + the AI engines)
7## zero extra approvals needed. It’s one diff.
Approve from your inbox, or review it like code.
Owners approve by email with one tap. Developers review the PR like any other. Either way, the approval is recorded: who, when, how.
Verified live, then verified indexed.
We check the published page by its content, then follow Google’s index nightly until it’s in. Regret a post? Revert the merge. Everything in that diff leaves together.
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, cancel any time. Founding rates lock in for as long as you stay. 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: no per-word charges, no meters, no setup fee. A product that isn’t live yet, like Local, 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. If approvals keep expiring, a person reaches out. 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, 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.
What do the products need access to?
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.
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.
Get early access
Cancel any time. Everything stays in the repo.