Skip to main content
Regenerating Content lets you request a new plan, rewrite selected text or replace an image. Choose the smallest change that addresses the problem, keep a copy of anything you want to retain, and review the saved result. AI requests can fail or change details you intended to keep.

Before you start

AI regeneration requires project-editor access and checks the project owner’s blog subscription or valid trial. A collaborator’s own subscription is not the entitlement being checked. Some controls show a disabled state; others report a restriction when you try the action. Read the displayed error rather than assuming every unavailable action has the same cause. Treat regeneration as a replacement of the selected saved content. Copy important wording or images before requesting it. An editor’s undo history is not a reliable backup of a completed server-side regeneration, and this guide does not promise a restore function for an earlier saved article. Avoid editing an old copy while image generation is still updating the post. A save that would overwrite newer image URLs with stale placeholders can be rejected, and the editor can reload the latest content. Keep your intended edits separately so you can reapply them after refreshing.

Regenerate the plan only

Use Regenerate plan for a completed plan whose title, type or brief needs a different approach. It requests a new title, blog type, excerpt and category from the current business grounding. It refreshes the plan metadata without generating the article body. The saved assigned keyword stays linked to the post. If there is no assigned keyword, the helper can choose one and save it. The action does not move the scheduled date. If you need a different date, use the separate scheduling workflow. The request can include other project titles to discourage repetition. This is guidance, not guaranteed deduplication across every article. Read the new title and brief for fit with the keyword and the intended reader.

When it’s available

Plan regeneration accepts To be generated, Rejected and Missed posts whose plan is completed. A placeholder whose plan has not finished is not eligible. A successful refresh of a rejected post returns it to To be generated; a missed post keeps its Missed status and original scheduled date. On a rejected post, the Regenerate status action refreshes this plan. It does not immediately rewrite the article. For a written draft, use the focused editing options below. See Blog Types for the format labels used in a plan.

Regenerate a section

Use a section rewrite when the surrounding article is useful and one paragraph, heading or other text block needs work. Open Edit Article, click the text sections you want to select, check the selected-section count, and set the controls before clicking Regenerate. Each selected section gets a separate rewrite request. The editor attempts to replace successful sections in their existing positions and saves the accumulated body changes after the requests settle. Some sections can succeed while others fail. A changed view alone is not confirmation that saving succeeded; check any save error and reopen the post to inspect the saved version. The writer is instructed to preserve HTML tags and the main topic while changing the wording. The response is not a structural or factual guarantee. Check headings, lists, links, numbers and the meaning of the selected passage after the rewrite, including its connection to the neighboring text.

The tone slider (Formal to Casual)

The slider runs from 0 to 100, with 50 as the initial value. Toward Formal requests more formal wording; toward Casual requests a relaxed tone. At 50, the current instruction is conversational and friendly. Review the actual wording rather than treating the slider as a fixed voice preset.

The length slider (Shorter to Longer)

The length slider also runs from 0 to 100, initially 50. Lower values request a shorter section, while higher values request more detail. At 50, the instruction asks for about the same length or slightly longer. It does not enforce a word count or add verified facts on your behalf.

Optional instruction (Re-Prompt)

Use Re-Prompt for a concrete revision, such as “explain the prerequisite before the steps” or “remove the repeated introduction.” Keep the instruction within 1,000 characters, which the API accepts. Selecting a tone or length does not replace the need to check whether the revision answers the reader’s question. If you request a business example, price or offer, provide verified details. A rewrite request is not a source for a new customer story or a claim about your service.

Regenerate a single image

Open Edit Article and select the image. The image controls distinguish New concept from Edit current. Choose New concept for a different scene, or Edit current to send the existing image as a reference with instructions for a specific change. Click Generate new image or Apply edit, as shown for the selected mode, and wait for the completed result or error. The initial response starts background work; it does not establish that the replacement has finished. A successful replacement is saved into the blog and can update its featured/header image when those used the selected URL.

The style slider (Modern to Realistic)

The Modern to Realistic slider guides the image request toward a clean, abstract or photographic treatment. It starts at 50. Choosing Edit current asks the generator to retain the reference’s composition, but the result can still change layout or details. Creating a new concept uses the service’s default size, so neither mode guarantees the original aspect ratio.

Optional custom prompt (Image Prompt)

The current prompt field is labeled New image concept or Edit instructions, depending on the mode. Keep it within 1,000 characters. Edit current requires a nonempty instruction and an existing image from the blog. With New concept, an empty field can fall back to the original planning context, alt text, title or keyword. Providing a prompt alone does not choose between creation and editing in this editor. Check the selected mode before submitting. See Image Generation for size requests, image styles, uploaded replacements and review checks.

Retry failed images only

Choose Retry images when the writing is useful and the post records failed image attempts. The retry uses the original image-plan entry for each recorded failure, requests that image again, and attempts to replace its placeholder. It skips the article-writing step and leaves successful images outside the failed list alone. This is additional image work, not a free retry promise. Editing a prompt for a separate image replacement does not change the original plan used by Retry images. If a plan entry is missing or the original request keeps failing, inspect the error and choose a suitable replacement rather than repeating the same request indefinitely.

When it’s available

The retry accepts Generation failed and Generated, pending review posts with recorded failed images. It is blocked during generation and for approved or published posts. If no failures are recorded, the action can report that there is nothing to retry. A retry can recover all, some or none of the missing images. When successful generated images are present, the post moves to Generated, pending review. If there was no featured image, a newly recovered hero is preferred, otherwise the first newly recovered image can fill that slot. Check the featured choice and any placeholders that remain. An older Generation failed post with saved text and failed images can be refused by the full-generate action and directed to Retry images. This safeguard is specific to that state; it is not a guarantee that every full-generation request on a written draft will be blocked. See AI Error Recovery & Retries for other failure paths.

Regenerate the entire blog from scratch

A full-generation request can replace the current body, image plan and generated images. Copy the material you want to retain before using one, and check the action’s availability for the post’s current status. The full-generation API accepts To be generated, Generation failed, Missed, Generated pending review and Modified pending review, subject to its access and generation-limit checks. The standard blog-detail actions for written review drafts are Edit Article, Approve and Reject. This guide does not assume a full-rewrite button appears there. In particular, Regenerate on a rejected post is the plan refresh described above. Choose the section or image controls for a focused repair; consult Blog Generation for the full workflow.

A note on editing reviewed posts

Saving body changes to Generated, pending review normally marks the post Modified, pending review. Image regeneration uses a separate saved-image workflow and can leave that status unchanged. Review both the text and images after an AI action; an unchanged status is not evidence that the content stayed the same. For an already-published article, a saved draft change does not prove the live website updated. Body edits can mark the post as needing sync, while image replacement paths have different behavior. Follow the available publishing controls and inspect the live article before treating the update as complete.

Which option should I use?

Choose the action by what needs to change and what is already useful. Refresh a completed plan before writing, rewrite selected text for a focused correction, replace an unsuitable image, or retry recorded image failures. Keep a backup and inspect the saved result before approving or publishing the article.

Choose a regeneration action by the problem

ProblemActionCheck afterward
A completed plan’s title or brief needs workRegenerate planTitle, type, excerpt, keyword and date
One or more selected text blocks need revisionSection RegenerateMeaning, markup, links and whether saving succeeded
An image needs a different scene or a specific changeNew concept or Edit currentSelected mode, returned image, alt text and featured choice
Recorded images failed but the writing is usefulRetry imagesRecovered images, remaining placeholders and errors
Most of the article needs replacingA full-generation workflow, where availableBackup retained, replacement saved and full editorial review