An AI draft can give you wording to work with. It cannot establish whether your prices, features, customer stories or results are true. The person publishing the page remains responsible for those claims.
## Supply a factual brief
Start with the audience, the page's purpose, the available product features and the action you want readers to take. Include the facts the draft may use and explicitly identify anything still undecided.
Ask for gaps to be marked rather than filled with plausible details. If there is no approved customer story, the draft should not invent a founder, business name or measured result.
## Review every claim, not just the tone
Highlight numbers, comparisons, quotations, feature descriptions and promises. For each, record the evidence and the person who can approve it. Remove statements that cannot be supported.
A statement such as “clients doubled their bookings” needs actual evidence. Rewriting it as “clients can double their bookings” still leaves an unsupported promise. Replace it with a concrete description of what the workflow does.
## Distinguish examples from customer evidence
Hypothetical examples can explain a process if they are clearly presented as examples. “Suppose a café changes its opening hours” is different from claiming a named café used your product and increased revenue.
Do not turn a fictional scenario into a testimonial through headings such as “success story” or “real-world results.” Readers should not need to guess whether the story happened.
## Check the product in its current form
Walk through the behavior the copy describes. Does the feature exist in the released product? Does it require installation or a particular role? What does it leave unchanged?
For ReCopyFast, the relevant workflow is editing existing website copy after a developer installs the script. It should not be described as a general blog generator, website builder or a tool that rewrites the site's source files.
## Edit for usefulness
Replace broad promises with an answer, an example or a step the reader can take. Remove repeated introductions and conclusions. Read the page aloud and cut sentences that do not advance its purpose.
Keep the approved copy in a reviewable document. When changes involve pricing, commitments or sensitive claims, involve the responsible subject-matter reviewer before publication.
## Verify the published result
Check the actual URL, heading, links and mobile layout. Confirm that the approved version is visible and keep the prior wording for recovery. The [website handoff checklist](/blog/website-handoff-checklist-client-updates) provides a reusable change-request format and publication checklist.
## Supply a factual brief
Start with the audience, the page's purpose, the available product features and the action you want readers to take. Include the facts the draft may use and explicitly identify anything still undecided.
Ask for gaps to be marked rather than filled with plausible details. If there is no approved customer story, the draft should not invent a founder, business name or measured result.
## Review every claim, not just the tone
Highlight numbers, comparisons, quotations, feature descriptions and promises. For each, record the evidence and the person who can approve it. Remove statements that cannot be supported.
A statement such as “clients doubled their bookings” needs actual evidence. Rewriting it as “clients can double their bookings” still leaves an unsupported promise. Replace it with a concrete description of what the workflow does.
## Distinguish examples from customer evidence
Hypothetical examples can explain a process if they are clearly presented as examples. “Suppose a café changes its opening hours” is different from claiming a named café used your product and increased revenue.
Do not turn a fictional scenario into a testimonial through headings such as “success story” or “real-world results.” Readers should not need to guess whether the story happened.
## Check the product in its current form
Walk through the behavior the copy describes. Does the feature exist in the released product? Does it require installation or a particular role? What does it leave unchanged?
For ReCopyFast, the relevant workflow is editing existing website copy after a developer installs the script. It should not be described as a general blog generator, website builder or a tool that rewrites the site's source files.
## Edit for usefulness
Replace broad promises with an answer, an example or a step the reader can take. Remove repeated introductions and conclusions. Read the page aloud and cut sentences that do not advance its purpose.
Keep the approved copy in a reviewable document. When changes involve pricing, commitments or sensitive claims, involve the responsible subject-matter reviewer before publication.
## Verify the published result
Check the actual URL, heading, links and mobile layout. Confirm that the approved version is visible and keep the prior wording for recovery. The [website handoff checklist](/blog/website-handoff-checklist-client-updates) provides a reusable change-request format and publication checklist.