How MergePress works.

One loop: propose, approve, ship, verify. Every module is work that rides it. Here’s what’s built, what’s next, and what we won’t build.

Propose. Approve. Ship. Verify.

  1. Proposed

    We open a pull request

    We study the repo, then open a PR: post, images, schema, internal links.

  2. Approved by you

    You approve it, or you don’t

    One tap from the inbox, or a normal PR review.

  3. Merged

    Your own pipeline deploys

    The merge triggers the deploy you already have.

  4. Live, verified

    We confirm it’s live and indexed

    We check the page by its content, then follow Google’s index nightly until it’s in.

Next on the rail

Buildable on the rail we already have. None of these are built yet, and none are for sale. The waitlist links are how you vote.

Decay Scanfree

A one-time check-up of your Search Console data: which pages are slipping, and what they’re costing you.

planned

Join the waitlist

Presence Snapshotfree

One page that grades your site health and profile completeness. The before picture.

planned

Join the waitlist

AI-visibility panel

Are ChatGPT and Google’s AI Overviews citing you? A panel inside Insights reports, a feature here, a whole product elsewhere.

planned

Join the waitlist

Newsletter rail

The month’s approved posts become your customer newsletter, one more approval, zero more writing.

planned

Join the waitlist

Facts-as-code

One facts file in your repo drives your site, schema, and profile. When they drift, the fix arrives as a PR.

planned

Join the waitlist

Booking page as a PR

A Cal.com-backed booking page, shipped as a diff you can read.

planned

Join the waitlist

Social echoes

Approved posts echoed to Facebook and LinkedIn with per-channel wording, the Google echo already ships inside Local.

planned

Join the waitlist

Case-study pages from your own reports

Your verified wins, turned into proof-of-work pages.

planned

Join the waitlist

Planned, further out

New infrastructure, not just new playbooks. On the roadmap; we take no money for anything in this ring.

  • Call tracking & attributionplanned
  • Review-request textingFTC-clean, consent-firstplanned
  • Citation & NAP watchplanned
  • Reputation Radarwatches the directories that have no write APIs. and says so instead of pretendingplanned
  • MergePress MCPconnect Claude or ChatGPT to your portfolio, read-only questions today, PR-gated changes the only write pathplanned
  • Local rank mapmap-pack positions from a measured SERP data provider, not scraping guesses averaged into a feel-good numberplanned

Where the rail is headed

roadmap

Approval Ledger

Every approval is already a first-class record, who, when, which channel, which diff, how to revert. The ledger turns that into an exportable compliance file, for practices and firms that must prove human oversight of every published word.

roadmap

Playbooks-as-code

Growth playbooks as versioned, readable text in a repo, diffable, reviewable, shareable. Agencies will be able to author and sell vertical packs without waiting on us to build every module.

roadmap

Fleet PRs

One reviewed change, rolled out to every client site as individual pull requests that honor each client’s own approval rules. Change thirty sites with one review, and every client still sees exactly what changed.

What we won’t build, and why.

If it doesn’t end in a diff you can review, it isn’t a MergePress module. So: no CRM, no two-way SMS inbox, no voice AI, no courses, no communities, no e-signatures. Everything that ships to a surface you own rides the rail; conversation tools are integrations, not modules. We’d rather stay the best at one motion than become a worse copy of an everything-platform.

  • CRM & pipelines
  • Two-way SMS inbox
  • Voice AI
  • Courses
  • Communities
  • E-signatures

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.