We write the blog. Your clients just approve.

For the sites you manage. Every post arrives as a pull request; your client approves it from their inbox in one tap. We check it went live and got indexed.

Cancel any time. Everything stays in the repo.

github.com/your-site/pull/12

Built for

Developers and agencies with static-site clients: Astro, Hugo, 11ty, Jekyll, Next.js. Solo owners welcome.

Your clients need zero git

They approve from email: a preview and a one-tap link. The repo stays your side of the counter.

On WordPress or Wix?

Local still works. A Google listing needs no website access. Blog writing needs a repo.

A month, start to finish.

This is the whole rhythm. Your client touches it twice.

  1. Day 1

    Topic ideas land in the inbox

    Three ideas from their repo and their customers’ searches. One tap picks.

    Pick a topic for October

  2. Day 3

    The post arrives as a PR

    Written, gated, previewed. Approve from email or review it like code.

    Approve & mergeProposed

  3. Day 4

    Live, then indexed

    We check the published page, then follow Google’s index until it’s in.

    Live ✓ Indexed ✓Verified

  4. Day 30

    The report, with verdicts

    What shipped, what changed, and win, flat, or loss on every fix.

    refresh: +38% clicksWin

Three products. One approval loop.

Everything moves the same way: proposed, approved, shipped through your own deploy, verified.

Content and Insights are on sale today. Local waits on Google. The rest lives on the roadmap.

early access

We write your blog. You approve every word.

Posts in your voice, about things your customers actually search for.

  • Drafts clear a writing gate before you see them
  • Schema, internal links, sitemap in the same diff
  • Approve from your inbox or in GitHub
  • Verified live, then verified indexed
Get early access

Cancel any time. Everything stays in the repo.

built, awaiting Google

Your Google Business Profile, tended weekly.

Keeps your profile posting, answers reviews under your rules, and catches the edits Google makes without telling you.

  • Posts drafted from every article you approve
  • Review replies that wait for your OK
  • Profile edits caught and proposed as PRs
  • Your customers’ words aren’t our data
Join the Local waitlist

Cancel any time. Everything stays in the repo.

New review on your profile

five stars

“Came out same day and fixed the leak in under an hour. Explained what went wrong instead of just handing me a bill.”

a customer, 2 hours ago

Reply drafted for you

Waiting on you

“Thanks for taking the time to write this. Glad we could get it sorted the same day.”

Passed the reply gateno promises, no prices
Nothing posts until you approve
Waiting on one thing: you.
Google edited your hoursgbp/profile.jsonPull request
early access

A monthly report your client actually understands.

What was done and what it changed, in Google’s own numbers.

  • Leads and calls first, in plain English
  • Finds pages Google says are slipping
  • Every fix gets a verdict: win, flat, or loss
  • No fake zeros. Ever
Get early access

Cancel any time. Everything stays in the repo.

Your June report

30 of 30 days measured

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.

What it replaces on a retainer.

The work a content retainer actually costs today, done by hand.

What MergePress replaces
What you’re paying for nowTypicallyPublished priceMergePress
Writing the postsa freelance writer$200–500 per postincluded, every post gated and approved
The SEO plumbing on every postyou, in the repo: schema, sitemap, internal linksyour eveningrides in the same diff
Assembling the monthly client reportyou, in a spreadsheet2–4 hours per clientwritten for you, under your brand
Knowing whether any of it workednobody re-measureswin, flat, or loss, printed either way
Doing it by handa writer’s invoice plus hours you can’t billMergePress, $99/mo per site

Typical mid-market freelance rates, Aug 2026.

Get early access

Cancel any time. Everything stays in the repo.

What lands in your inbox and your repo.

Product illustrations, recreated from MergePress output formats. Sample data, marked as such.

Blog-post PR

early access

illustration with sample data

Google post

built, awaiting Google

Google Business Profile post

Book your furnace tune-up before the first freeze. Same-week slots are open now.

of the 1,500-character limit

validated against Google’s limits

illustration with sample data

Monthly report

early access

the front page of your report

  • Calls: not connected yet
  • month 2 of 6, on track
  • refresh verdict: prints win, flat, or loss

illustration with sample data

Review reply

built, awaiting Google

reply draft, your rules applied

Thanks, Dana. Glad the crew got your heat back the same day.

policy gate: passed

illustration with sample data

Profile-drift PR

built, awaiting Google

Google changed your hours

1Mon–Fri 9–5
2+Mon–Fri 9–6

merge to accept, or close to push your version back

illustration with sample data

What signing up actually gets you.

Not a dashboard you have to live in. A small set of surfaces, each with one job.

  • The GitHub App

    Installed on the one repo you choose. Three permissions, nothing else. Uninstalling closes the only door we have.

  • Approvals in your inbox

    Topic choices, previews, and one-tap approvals by email. Silence means nothing ships.

  • Your client view

    A private page, reached from an emailed link: what shipped, what’s waiting, every approval given.

  • A monthly report in plain English

    Customer actions first, then the work and its verdict. Win, flat, or loss, printed either way.

  • For agencies: your brand on everything

    Client workspaces under one login. Reports and emails carry your logo, not ours.

Our permission screen is the pitch.

The typical AI content tool asks for your CMS admin login. We ask for three GitHub permissions. The interesting part is what they don’t include.

Install MergePress

3 permissions
  • ContentsRead & write

    Read your site to learn its structure and voice; create branches and commits for proposed posts.

  • Pull requestsRead & write

    Open the PR, read your review, merge only after you approve.

  • MetadataRead

    Mandatory GitHub baseline: repo name, default branch.

That’s the whole list. No workflows. No secrets. No deploy keys.

Our GitHub App install screen, recreated. The permission set is frozen in our public security doc.

PR-gated

Every change is a pull request you can read line-by-line. Your approval is the only key that merges it, and it’s recorded: who, when, through which channel.

Git-native

Your site already ships from a repo. MergePress speaks that language instead of asking for CMS passwords, and everything we write is yours, in your git history, forever.

You keep the keys

No deploy credentials, no CI access, no secrets. Enforced by GitHub’s servers, not by our promises. Uninstall and our GitHub access is gone instantly.

Status chips on everything.

If you can’t buy it today, the page says so before you can pay.

See the roadmap

The security page is the spec.

The same document we registered the GitHub App from. Three permissions, frozen and public.

Read it

A writing gate before every PR.

Drafts that fail it are rewritten or discarded. They never reach you.

How the gate works

Founding rates, while we earn the case studies.

Agency

$299per month

For agencies and developers shipping MergePress under their own brand.

  • + $79/mo per client site
  • Everything in Pro, per client workspace
  • White-label reports & emails
  • One dashboard for all your clients

Local is included and never billed until it’s live on a profile. Any website qualifies, Wix included.

You set the cadence. Most sites do two to four posts a month; three posts worth approving beat thirty worth deleting.

Cancel any time and keep everything. It was always in the repo.

Full pricing details

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.

  1. Pick a plan and sign up. Founding rates, month to month.
  2. Install the GitHub App on the repo you choose. Three permissions, no CMS logins, no deploy keys.
  3. We read the repo and open the first PR. Your client’s approval merges it.

Founding rates. Cancel anytime; your repo stays yours.