Skip to main content
Blog Generation turns an article plan into a saved draft through separate writing and image steps. Check the plan, keyword and project settings before starting. Afterward, review the saved text, links and pictures. A started request, a high SEO score or a pending-review status does not confirm the article is ready to publish.

What you need before you generate

You need edit access to the project and an active blog subscription or valid trial for the project owner. Generation also checks the applicable generation allowance. A paid plan alone does not establish that another request is within that allowance. See Quota & Limits for the separate limits. If Generate is disabled or the request is refused, read the subscription, access or limit message before retrying. Collaboration access does not replace these checks. Existing content and AI actions are different: do not assume that every editing or image tool remains available after a plan expires. Before starting, check the planned title, assigned keyword and brief. Review Preferences, Sources & Brand Voice and the post’s saved direction for instructions that should apply to this draft. Copy any existing text or images you want to retain before requesting a full replacement.

When the Generate button is available

Open the blog’s detail page. The plan card can show Generate Blog; the status action can show Generate Content for To be generated, Generation failed or Missed posts. On a Generation failed post, inspect the failure first so you choose between a writing retry and an image-only retry.

Choose the action for the current post

Current postAction to look forWhat to check
To be generated or MissedGenerate Blog or Generate ContentThe plan, keyword, settings and access
Generation failedThe failure panel or Generate ContentWhether text is saved and only images are missing
Generated or Modified, pending reviewEdit Article, Approve or RejectThe existing draft before choosing a replacement
RejectedRegenerateThe refreshed title and brief before generating the article
For a rejected post, Regenerate refreshes its plan and returns it to To be generated. It does not immediately rewrite the body. Written review drafts offer Edit Article, Approve and Reject in the standard workflow; do not assume a full-rewrite button appears there. See Blog Status Lifecycle for the status labels.

If only the images failed

Use Retry images when the article text is useful and the post records failed images. It uses the original image plan, skips the writing step and attempts to fill the failed placeholders. A retry can fail again or report that an original plan entry is missing. An older Generation failed post with saved text and failed images can be redirected away from a full generation to this image-only action. That safeguard does not cover every request to replace a written draft. Keep the text you want to retain and read AI Error Recovery & Retries before starting another full run.

The generation pipeline

A successful start response launches background work; it is not the completed article. The detail page polls for status, word count and image progress. Leaving the page does not itself cancel that work, but background work can still fail or be interrupted. If the displayed progress stops updating, reopen or refresh the post to check its current state before starting another request. Generation and publication are separate stages. Check the project’s Publishing Modes: an automated scheduled workflow can hand a completed generation onward for publishing, while manual or approval-required modes keep a separate review step. Do not assume every generated article will wait indefinitely for your approval.

Step 1 - Plan the post

The planning request asks for an outline, image plan, estimated word count, tags and suggested search metadata. The image-planning instructions recommend two to four images; that is guidance, not an enforced finished-image count. Generation starts from the post’s saved planned title. The planning step keeps that title and preserves an existing meta description rather than replacing either with a new AI suggestion. If you want a different title or brief, change or regenerate the plan before writing. Check the saved title, description and URL afterward.

Step 2 - Write the article

The writer receives the plan and project context. Your saved article-length preference supplies a target range, with Standard used as the fallback. This is a prompt instruction, not a guaranteed final word count. Use Word Count & Targets to decide whether the saved draft needs more detail or a tighter scope. The writer is instructed to produce semantic HTML with H2 and H3 headings, paragraphs and useful lists, without adding a body H1. It also receives linking guidance and can place image placeholders such as IMAGE_1. Review the actual headings, links and layout: instructions do not establish that every part of the returned draft is correct. The text is saved before the normal image phase, with those placeholders still present. Text ready, images pending means there is saved writing to inspect while image work continues. It does not mean the article is complete or ready to publish.

Step 3 - Generate the images

After the writing step, image work attempts to replace the planned placeholders with successful images. Some or all images can fail while the saved article still reaches Generated, pending review. Check the missing-image notice, remaining placeholders and featured image as part of your review. Image style, size requests and branding instructions guide generation; they do not verify the finished picture. Brand & Text can intentionally include typography, so a blanket promise that images contain no text would be misleading. See Image Generation for the current image choices and review steps.

Steering the output

Save per-post direction before generating. The writer receives that saved direction along with available business information, preferences, sources, brand voice and recent-post context. Describe the angle or detail you want and supply verified business facts. These inputs guide the request; they do not guarantee obedience, factual accuracy or a new angle. For example, a direction such as “explain the prerequisite before the steps” describes an editorial change without inventing a customer outcome. See User Direction for that field’s workflow.

SEO scoring

Use the displayed SEO score as a review aid. The headline value can combine rule-based checks with the writer’s assessment; when that assessment is absent or unusable, it falls back to the rule-based result. A high score does not verify your business facts, approve an image or guarantee search rankings. Read any available category breakdown and suggestions alongside the article. Fix issues that affect the reader, such as an unclear section or an unsuitable link, rather than padding the draft to chase a score. SEO Scoring Explained describes the scoring view.

Reviewing and editing in the blog editor

Open the saved blog and choose Edit Article when you have edit access. Check the title, URL, body, links, word count, pictures and alt text. Compare prices, service descriptions and other business claims with the material you supplied before approving or publishing. Use a manual edit for a direct correction. Use section regeneration or a single-image action when one part needs a new version. A section rewrite can save successful replacements even when another selected section fails, so reopen the post and inspect what was saved.

Regenerating content

Choose a focused rewrite when the surrounding article is useful. A full generation can replace the current body and image plan, so keep a separate copy of material you want to retain. Do not rely on editor undo as a backup for completed server-side work. For the controls and saving behavior of a section rewrite, image replacement, failed-image retry or plan refresh, use Regenerating Content. If a run failed or stopped progressing, use AI Error Recovery & Retries to choose the next action.