Skip to main content
In a review-first publishing setup, a generated draft waits for a decision before it goes live. Use the blog detail page to read the content, inspect the product’s checks, and make changes before approving it. Approval authorizes a workflow action; it does not independently verify the article or provide expert signoff. Check Publishing Modes & Autopilot before relying on a review queue. Draft for me is the documented review-first preset; Full autopilot publishes without that human approval step. See Blog Status Lifecycle for the state names.

The review flow at a glance

A finished draft awaiting review has status Pending Review (generated_pending_review). From the detail page, you can:
  • Approve: move it to Ready to Publish (approved).
  • Reject: keep it in Rejected so you can revise or regenerate it.
Editing the body of a pending draft changes its technical state to modified_pending_review. The calendar still shows a Pending Review badge, but the version awaiting your decision includes your edits. Read the changed version before approving it. Open the post from Content SEO to use its available Approve or Reject actions.

What you see before you approve

The editor provides the article title, slug, metadata, featured image, and body. Use that view to review the content; also check the published destination after publishing, because a CMS theme or integration can render it differently. The detail page also surfaces:
  • SEO score and suggestions: inspect the category breakdown and specific gaps. The internal score, including any numerical threshold shown, is not an accuracy certificate or a Google ranking score. See SEO Scoring Explained.
  • Readability: an English-specific scoring check. It does not replace a fluent review of another language or a careful review of technical explanations.
  • Images: check relevance, alt text, and whether any generation failed. Use image-only retries when the text is complete; see Retry failed images only.
  • Compliance findings: an enabled Compliance Profile can show violations or missing disclosures. No banner does not prove that compliance was checked or that a post meets professional obligations.
Before approving, read the complete draft and check:
  1. The title’s promise is answered for the intended reader.
  2. Offers, contact details, product features, and important claims match approved information or supporting sources.
  3. Quotations, testimonials, and examples have appropriate evidence and permission.
  4. Links, images, and metadata are useful and accurate.
  5. Any required specialist review has actually happened and has a record.
Edit a specific passage or image when the rest of the draft is useful. If regenerating, save wording you need to keep: the regeneration guide explains that previous versions are not retained.

Approving a draft

  1. Open the blog from Content SEO.
  2. Read the current content and inspect score suggestions, images, and any compliance findings.
  3. Make the necessary edits and complete any required professional review.
  4. Click Approve when the version is ready for publication.
The documented flow moves it to Ready to Publish. The next action depends on the project’s setup:
  • Publish now: the Publish Now action sends the post through the configured publishing path. Connected CMS destinations include WordPress, Webflow, Ghost, Shopify, Zepio, and custom webhooks.
  • API/deploy-hook publishing: the documentation also describes marking a post published and firing a deploy hook for sites that pull content through the Public Blog API. Check that the receiving build or website actually updated; a recorded publish status is not proof of successful downstream deployment.
  • Scheduled publishing: approved and scheduled posts can enter the automatic publishing queue at their publish time. Check the saved mode, destination, and schedule; approval alone does not describe every part of that setup.
See Publishing for connection requirements and Publishing Modes & Autopilot for the preset behavior. In a compliance-enabled project, the documented hold/block gate can affect publication; see What happens at publish.

Rejecting a draft

Reject keeps the draft in the project rather than approving it. The documented flow preserves its calendar slot, title, keyword, and content so you can decide what to do next:
  • Regenerate the plan: request a fresh title and excerpt for the same keyword when the topic or angle needs work.
  • Regenerate the content: rewrite the article against the plan when the writing needs a new pass. Save useful text first.
  • Approve Anyway: use the documented action on a rejected draft when you have reviewed it and changed your decision.
Rejecting a draft is different from regenerating it. The latter replaces content, so do not interpret keeping a rejected draft as a general promise that all versions are recoverable.

Who can approve

The documented review actions require Editor access or higher: Owner, Admin, or Editor. Viewers can read drafts but cannot approve, reject, edit, or publish them. See Workspace & Team to review project access. An access role grants product permissions, not a professional credential. Assign the appropriate reviewer for regulated or specialized claims before granting final publication approval.

Where approval notifications appear

The documentation describes in-app notifications and email when a blog is ready for review or published, with a link to the post. Check the dashboard’s review queue rather than relying only on receiving an email. A notification does not establish who reviewed the draft or what they checked. If several members can approve, agree who is responsible for factual and specialist review. Team-wide notification does not replace that assignment.

After you publish

A published post shows Published, with View Live when a destination returns a URL. Open the actual page to inspect its title, body, images, links, and disclosures. For a pull-model site, verify the deployed page after its build completes. The documented Sync Changes action sends edits from a published post to the destination. Check the live result after syncing. Unpublish returns the post toward a draft state, and Republish can publish it again; destination behavior depends on the integration, so confirm what is publicly visible rather than assuming every platform removed the page.