Safe Automated Content Publishing With Git

You hand a tool write access to your repository and a fair question follows: what else can it touch? For a small business site, the answer matters more than any feature list. A bad commit can break a checkout page, overwrite a template, or take the site down on a Friday night. Most owners and solo founders have no developer on call to sort that out. Safe automated publishing comes down to a few plain controls: where the tool can write, who approves changes, how you see what happened, and how you undo it. This page explains what those controls look like when content goes into Git, and how ConveyLoop handles each one, so you can decide how much to trust automation and how much to review.

What keeps a hands-off publisher from causing damage

Limit where the tool can write

The first safeguard is scope. ConveyLoop commits pages to a single target subdirectory, /conveyloop/seo by default, and only creates, changes or deletes files inside it. It does not read application code. If a commit would touch anything outside that folder, it is refused.

There are size limits too. By default, one publish cannot change more than 200 files or delete more than 50. A manifest file, conveyloop-manifest.json, records what it wrote, so it can remove unpublished pages without deleting anything it did not create.

Choose how much happens without you

Publishing defaults to a direct commit to the branch. If you want a look first, switch to pull request mode. On GitLab it is a merge request. ConveyLoop works on its own branch and opens the request for you to merge.

Separately, you pick an approval mode: Auto, Semi or Review. Drafts get a rules check and an AI review against facts from your site, with up to two rewrites. Content that cannot be verified goes to a review queue instead of being published.

Confirm it went live, and know how to undo it

A publish is only useful if the page shows up. ConveyLoop checks about three minutes after publishing, again ten minutes later, and once more thirty minutes after that. The Git window shows 'Live on your site'. If a page is missing, it gives you a prompt for an AI coding agent to fix the setup.

Every page keeps a version history with side-by-side diffs and one-click rollback. Because each publish is a Git commit, you also have your normal Git history. Hosts that deploy on push, such as Vercel, Netlify, Cloudflare Pages and Render, rebuild from the commit. In testing on Netlify, a new page was live ten seconds after commit.

Know the limits. Self-hosted Git editions are not supported yet, only GitHub.com, GitLab.com and Bitbucket Cloud. Sites behind a password or Cloudflare Access cannot be read by ConveyLoop or search engines.

How ConveyLoop Helps

ConveyLoop connects to one repository per project from Project Setup, using the GitHub App on GitHub.com, or GitLab.com and Bitbucket Cloud. It writes into its own folder, never reads your application code, and refuses commits outside that folder. You choose direct commit or pull request, and Auto, Semi or Review approval. Each publish is checked three times for going live, and every page can be rolled back. Disconnecting opens a pull request that removes its files. You stay in control of the repository the whole time.

Frequently Asked Questions

Can an automated publisher break my website code?

ConveyLoop is designed not to. It writes only inside its own folder, never reads application code, and refuses any commit touching files outside that folder.

Do I have to review every change?

No. Pull request mode lets you review each change before merging, while direct commit publishes straight to the branch. Auto, Semi and Review modes set how much goes live without you.

Which Git hosts work?

GitHub.com, GitLab.com and Bitbucket Cloud. GitHub Enterprise Server, self-managed GitLab and Bitbucket Data Center are not supported yet.

What happens if I disconnect the repository?

ConveyLoop opens a pull request that removes its files. It never deletes them directly, and it deletes only files it wrote, tracked in a record.

How do I know a page actually went live?

ConveyLoop fetches the page about three minutes after publishing, then ten and thirty minutes later. The Git window shows 'Live on your site' when it finds it.

Will it work with my hosting setup?

It works with hosts that deploy on push, including Vercel, Netlify, Cloudflare Pages and Render. Sites need a one-time routing change, typically one route or rewrite rule.

Can I undo a bad rewrite?

Yes. Each page has version history with side-by-side diffs and one-click rollback.