Use AI to turn approved information into a useful first draft, improve an existing passage, or review an article before publication. You decide which changes to keep and remain responsible for the facts, links, and final reader experience.
This guide focuses on Writing help and Draft review in the blog and documentation editors. Page Builder, the general site assistant, and the FAQ form have different controls and save behavior.
Before you begin
Open an article from Site → Blogs or Site → Docs, then select Write. The AI co-author panel contains Writing help and Draft review. If it is collapsed, use Open AI co-author to reopen it.
You need content-editing permission and a working AI setup for your site. If controls are unavailable, see Why can’t I see or edit a feature?. If a request reports a provider or model configuration problem, ask your site administrator to check the AI settings rather than putting credentials into the chat.
Before requesting a substantial rewrite:
- Save any work you want to preserve, and keep a copy of wording that must remain exact.
- Confirm you have opened the intended article. Be especially careful with similarly named drafts.
- Check for a scheduled release and coordinate changes before its publication time.
- Decide whether you want advice, a proposed edit, or a complete draft. Name the specific field or section you want changed.
The editor co-author proposes changes; it does not publish an article merely because you send a message or run a review. When using a general assistant that can operate site tools, state the boundary explicitly: “Prepare a draft for review; do not publish.”
Give the AI a clear brief and reliable sources
A useful brief explains five things:
- Reader: who the content is for and what they already know.
- Outcome: what they should understand or be able to do afterward.
- Source facts: the approved process, product details, or policy the content must follow.
- Format: an outline, short answer, step-by-step guide, introduction, or specific field edit.
- Limits: what must stay unchanged, what is unknown, and what the AI should avoid claiming.
For example:
Draft a customer guide for first-time users using only the approved steps below. Start with the outcome, list prerequisites, then write numbered instructions and troubleshooting. Keep the button names exactly as supplied. Do not invent missing settings or promise response times. Ask about missing information before drafting. Leave the title and article address unchanged, and propose the body for my review.
Add the actual approved steps to your request. If you only supply a topic such as “write about billing,” the AI has little basis for knowing how your business handles it.
Include the relevant source text, not just a link. A pasted URL does not prove that the assistant opened the page or read the latest version. For long material, give the sections needed for the task and identify their date or version when it matters.
Use sources you are allowed to share through your site’s configured AI service. Remove passwords, access keys, private customer records, and unrelated personal details. Ask for help with a representative example rather than pasting an entire customer conversation when a short, redacted summary is enough.
Draft or revise with Writing help
- Open Writing help in the AI co-author panel.
- Type your request in Message the AI co-author. Add the approved facts and the changes you want.
- If you want help with a passage, highlight the body text and check that the panel shows a selection scoped to the intended field. Use Clear beside the selection when you want the next request to cover something else.
- Choose Send message, or press Enter. Use Shift+Enter for a new line while composing your request.
- Read the response. It may ask for more context, offer suggestions for particular fields, or propose a follow-up request.
- Compare the proposed wording with the current text before accepting anything.
Suggested prompts and follow-up buttons can send a request immediately. Read them before selecting one, and wait for the current request to finish before starting another.
Keep revision requests specific. For example:
Shorten the selected introduction to two sentences. Keep its meaning and the existing link. Explain the reader’s outcome first, and remove promotional language. Do not add product claims or change the rest of the article.
Or:
Check this draft against the supplied instructions. List missing prerequisites, unclear steps, and claims that need confirmation. Do not rewrite the article yet.
Highlighting text helps focus the request, but it does not guarantee that the proposed change replaces only that passage. A suggestion can replace an entire field, including the full Body. Inspect the whole replacement for lost sections, links, examples, or conditions.
Accept, dismiss, or revise a suggestion
Suggestion cards identify the affected field and explain the proposed change. In Split view, compare Current and Proposed. Unified view shows the changes together.
- Accept applies the proposed replacement to the editor draft. It does not mean the article is saved or published.
- Dismiss removes the suggestion from the active findings without changing the article text.
- Undo last restores the most recently dismissed finding so you can reconsider it. It is not an undo button for text you already accepted.
Read the field label carefully. A suggested Title, Excerpt, Slug, SEO Title, SEO Description, Category, or Tags change has a different effect from a body rewrite.
Review a slug change particularly carefully on a published article: it can change the address readers use. Keep the existing address unless you intentionally plan a move and preserve old links. See Changing a page address without breaking links.
If only part of a suggestion is useful, dismiss it and make the smaller edit yourself, or ask for a revised suggestion. Do not accept a full replacement just to keep one sentence.
When a field has changed since the suggestion was produced, Accept may be unavailable because the suggestion no longer matches the draft. Ask for a fresh version or rerun the review. Do not overwrite newer work to make an old suggestion fit.
After accepting a change, read the edited article itself and save the draft deliberately. Co-author conversation or review history is separate from saving the article’s current content.
Run a draft review
Use Draft review once the article is complete enough to assess as a whole.
- Check that the current editor contains the version you want reviewed.
- Open Draft review and choose Run review. If a review already exists, the button is Re-run review.
- Wait for the review to finish. Read the summary and findings, not just the score.
- Work through the relevant categories, such as clarity, tone, structure, SEO, links, and factual issues.
- Inspect each proposed change and choose whether to accept it, correct the issue yourself, or dismiss an unsuitable finding.
- If you change the draft, rerun the review when you need guidance on the new version, then complete your own final checks.
The score is a writing assessment, not proof that the instructions work or that the facts are correct. A high score does not establish that a link was opened, a product feature exists, or a policy was approved. SEO suggestions also do not guarantee rankings or traffic.
Understand Info, Warn, and Block
Info is an improvement suggestion. Warn calls attention to an issue worth investigating. Neither label means you must accept the proposed wording.
Block is a publishing blocker when it belongs to the current review and remains unresolved. Read the reason and check the evidence. Apply a correct fix, or dismiss a finding you have verified is incorrect or inapplicable. Dismissing a finding records that decision; it does not correct the content for you.
Accept all blockers can apply several proposed replacements. Use it only after reading every affected field. It is not a general “approve this article” action, and some findings may still require attention afterward.
If the draft changes, the panel can show that the review is stale. Treat that as a reminder that the review describes an older version. Address any genuine issue it identified and rerun the review for current guidance rather than using unrelated edits to avoid a finding.
AI review is optional
You can review content yourself when AI review has not run or is unavailable. A current unresolved AI blocker still needs a decision, and the article must satisfy its normal save, preview, and publication requirements.
An AI review and a saved preview serve different purposes. The review suggests editorial changes. The preview lets you check the actual version and presentation your readers will receive.
Check the content yourself before publishing
Verify the parts an AI response can get plausibly wrong:
- Instructions: follow the steps using the current interface. Check button names, permissions, prerequisites, and the expected result.
- Claims: confirm prices, limits, availability, dates, policies, and promises against the authoritative source.
- Links: open the destination as the intended reader. Check downloads and section links as well as page addresses.
- Completeness: make sure the rewrite has not removed exceptions, recovery steps, accessibility information, or a necessary next action.
- Examples: replace sample names or values appropriately, and remove placeholders and internal drafting notes.
- Presentation: preview headings, lists, tables, code, images, and links on desktop and mobile.
Keep the title, summary, body, and search metadata consistent. For example, a shorter SEO description must not promise something the article no longer explains.
If you cannot verify a claim, remove it, qualify it accurately, or ask the person responsible before publishing. Do not turn an AI guess into a customer promise.
Save, preview, and publish the final version
- Read the full draft after applying suggestions, including metadata changes.
- Choose Save draft to preserve the current article.
- Preview the saved version and check its appearance, links, and address. If you edit again, save and refresh the relevant preview before release.
- Resolve any current release blocker shown by the editor. Do not assume an AI score replaces the publishing checks.
- Choose Publish or Publish changes only when the complete article is ready for readers.
- Open the public article and confirm that the expected version is live.
For the full authoring workflow, see Writing and publishing a blog post or Creating a documentation article.
The FAQ form behaves differently: saving a new FAQ publishes it immediately. Prepare and review an AI-assisted answer before saving it there. See Writing useful FAQs and publishing them.
Troubleshooting
The AI asks for information instead of writing
Supply the missing facts or narrow the request. If the body is empty, a request to “improve this article” may not provide enough to work from. Add an approved outline or source text rather than asking the assistant to guess.
A request fails or takes too long
Keep your current writing intact and read the error. Use the offered retry for a failed chat request, or rerun a failed review after checking the cause. Avoid repeatedly starting the same request while one is still running.
For provider, model, access, or usage errors, ask your administrator to check the site’s AI setup. You can continue editing manually. If no review result was returned, do not treat the attempt as a completed review.
Accept is disabled or a suggestion no longer matches
The field may have changed since the response, or you may not have editing permission. Check the message on the card. Request an updated suggestion instead of replacing newer text with the old version.
The review is stale after a small edit
Review context includes more than the body. A title, summary, slug, category, tag, or SEO change can make earlier guidance outdated. Rerun the review when you want it to reflect the current draft, and check the final saved preview separately.
The review keeps suggesting an unwanted change
Check the rationale against your audience, source facts, and existing links. You can dismiss an unsuitable finding and keep accurate wording. You do not need to rename an established article or change its address merely to improve a score.
Accepted text removed something important
Stop before publishing. Restore the missing content from your retained copy or carefully use an earlier saved revision, then review the whole draft again. Clear chat clears the conversation; it does not undo accepted article changes. Undo last beside dismissed findings only restores that finding.
If the change is already live, correct the saved draft and publish the reviewed correction. Use Understanding drafts, previews, and publishing to check which version readers are seeing.
Chat or review history did not save
Treat a persistence error as a warning that the co-author session may not be restored later. Save the article through Save draft, keep any source notes you need, and report the exact error. Do not assume a remembered conversation proves the article itself was saved.