Stage & publish WordPress, Webflow, Grav

Read the page. Show the diff.
Push it live.

Moose connects to your site, reads the live page, and shows you the exact before and after. Nothing is written until you click publish.

Hi, Moose · Publishing himoose.com · WordPress · Production
Best AI visibility tools for small agencies
Stage
Read the live post
Send to CMS
Pending, not live
Publish live
Waiting on you
Before and after
Before
We help agencies track their brand across AI search.
After
Hi, Moose is a desktop app that tracks how ChatGPT, Claude, and Gemini describe your brand, with local checks on five engines.
Publish live Roll back Moose read this from the live post 4 seconds ago. If it changes before you publish, I stop and tell you.
Three clicks, in this order

Nothing is written until the third click.

Reading, staging, and publishing are separate steps in Moose, so at every point you know exactly what state your site is in.

01
Stage

Moose fetches the live page and works out where the change goes. This step is read-only. Nothing is written to your site.

02
Send to CMS

The change lands in a pending state. A WordPress patch sits in post meta with the live post untouched. Webflow gets a draft. Grav gets an unpublished page.

03
Publish live

Now it goes out. WordPress and Grav take a server-side backup first, so one click puts it back the way it was.

The review step

You approve the words, not a summary of the words.

Moose shows the block as it stands and the block as it will read. What you approve is what gets written.

The diff is the real block. Before and after, rendered from the HTML on your live page, not a paraphrase of the plan.

If the page changed, I stop. The approval is bound to the exact content you saw. If someone edits the post in the meantime, the write is rejected instead of overwriting their work.

You pick where it lands. For WordPress inserts, the placement picker lets you choose the block. The model suggests the words. It does not choose the spot.

Backups and rollback. WordPress and Grav snapshot the page before applying. Rollback is one click, and it runs on the server.

Security

Your site credentials never leave your machine.

Hi, Moose is a desktop app, and your keys and tokens are stored on your computer, sealed with your operating system's own encryption. We do not keep a copy in the cloud.

Encrypted at rest. Credentials are encrypted with the macOS Keychain or Windows data protection before they touch disk, and they stay in the app's main process, away from the part of the app that renders the screen.

Not stored on our servers. When Hi, Moose issues your WordPress key, our servers keep a hash so the key can be listed and revoked, never the key itself. Webflow and Grav credentials are never sent to us at all.

Signed and timestamped. Every write to your site travels over HTTPS with an HMAC signature and a timestamp. The plugins reject anything unsigned or stale, so a captured request cannot be replayed later.

Off until you turn it on. The WordPress and Grav plugins ship with remote actions disabled. The switch lives in your own site settings, and it stays wherever you set it.

What each one can do

Built for WordPress, Webflow, and Grav.

Each platform gives Moose a different channel to write through, so the powers differ. Here is what Moose can do on each.

WordPress logoWordPress Deepest support
Hi, Moose AEO Agent plugin
Moose can
  • Patch titles and body copy on posts and pages
  • Insert a TL;DR above the lede or an FAQ below it
  • Create new draft posts and publish them
  • Add FAQ schema (JSON-LD) to the page head
  • Separate production and staging connections
  • Server-side backup and one-click rollback
Good to know

Writes go straight from your desktop to your site. No third party sits in the middle.

Webflow logoWebflow Official API
Official Webflow MCP, OAuth
Moose can
  • Edit headings, paragraphs, lists, and quotes on static pages
  • Write the page title and meta description
  • Edit rich-text blocks on CMS collection items
  • Publish an item as a draft, then take it live on your word
  • Add FAQ schema as page custom code
Good to know

Webflow publishes the whole site at once rather than one page at a time, so Moose holds everything as a draft and tells you what a publish will carry with it before anything goes live.

Grav logoGrav v1 connector
Hi, Moose Grav connector plugin
Moose can
  • Read and rewrite markdown and frontmatter
  • Create pages with a title, slug, and body
  • Write categories, tags, and the meta description
  • Publish by flipping the page to published
  • Server-side backup and rollback
Good to know

The v1 connector covers pages on your default template. You can widen that in the plugin config on your server.

Getting connected

Fifteen minutes, once.

WordPress and Grav use a small plugin on your site. Webflow connects through its official OAuth flow. In every case, the credentials stay on your machine.

WordPress logoWordPress
  1. 1 Generate an API key in Hi, Moose
  2. 2 Install the Hi, Moose plugin on your site
  3. 3 Paste the key, hit Test Connection
Webflow logoWebflow
  1. 1 Click Connect Webflow
  2. 2 Approve it in your browser
  3. 3 Your sites show up in the app
Grav logoGrav
  1. 1 Install the connector plugin
  2. 2 Generate a bundle in Grav Admin
  3. 3 Paste it into Hi, Moose once

Your site owner keeps control the whole way. The plugins ship with remote actions off until someone turns them on.

Stage & publish

Stop copying fixes into a CMS by hand.

Free to download. Connect a site, read a page, and see the diff before you commit to anything.