Review or auto publish: choosing your level of control

Every project publishes in one of two modes. In review mode, nothing goes live until you read it and approve it: each finished piece waits for your sign-off. In auto mode, content that has passed every check publishes on its own, without you clicking approve on each one.

The crucial point is that the safety layer runs identically in both modes. Auto does not mean unchecked. It only means you have chosen not to be the final manual step. Uniqueness, quality, pace and compliance are enforced either way.

New projects begin in review on purpose. When you are getting started, you want to see exactly what the engine produces for your business, in your voice, before any of it reaches your live site. Reading the first batch or two builds trust and often surfaces a tweak to your positioning that improves everything afterwards.

Review mode is also the safer default for anyone. There is no downside to it beyond the few seconds it takes to approve a piece, and it keeps you in full control of your domain from day one.

Once you have seen enough content to trust the output, and your positioning is settled, auto mode removes the last manual step so the loop runs entirely on its own. It suits a mature project producing steady, on-message content where reading every piece has stopped adding value.

You can switch back to review at any time, and you can set the mode per project, so a well-established site can run on auto while a new one stays in review. Whatever you choose, the pace limit still applies, so auto never becomes a flood.