An AI-generated website can be a starting point. Before handing it to a business owner, verify the parts that affect customers and the people who will maintain it.
## Confirm ownership and ongoing costs
Identify who owns the domain, hosting account, builder workspace and connected services. Check which capabilities depend on a subscription and what happens if it ends.
Document export or transfer options from the platform's current terms and controls. Do not promise the client they can move everything unchanged without testing what is actually available.
## Replace invented business details
Read every public page. Confirm prices, opening hours, addresses, service areas and qualifications with the owner. Remove unsupported testimonials, stock success statistics and guarantees the business has not approved.
Check images and sample content for placeholders. A polished page can still contain an invented team member or a contact detail left over from a template.
## Exercise the important customer paths
Test the contact form, booking link, purchase flow where applicable and the messages users see after submitting. Use an agreed test method that does not create a real charge or send unwanted messages.
Verify receipt in the intended destination. A success message on the page does not prove an email arrived. Also check validation, an unsuccessful submission and the route for obtaining help.
## Test routine updates with the owner
Ask the owner to change one authorized piece of copy using their own account. Confirm what can be edited, whether saving publishes and how the previous wording can be recovered.
If the native editor meets the need, use it. If it exposes more control than the owner needs, assess the actual permission options before adding another system. ReCopyFast can provide an installed editing layer for existing website copy, but it does not replace the builder or rewrite its source files.
## Review the public site after publishing
Check navigation, links and text wrapping on narrow and wide screens. Open the public URL independently of the builder's preview. Review page titles and intended search visibility, while remembering that publication does not guarantee indexing.
Finish with a [one-page handoff record](/blog/website-handoff-checklist-client-updates): account owners, editable content, publication behavior, recovery instructions and support contacts. The website is ready for handoff when the intended operator can carry out the next real update and knows what to do when a task needs help.
## Confirm ownership and ongoing costs
Identify who owns the domain, hosting account, builder workspace and connected services. Check which capabilities depend on a subscription and what happens if it ends.
Document export or transfer options from the platform's current terms and controls. Do not promise the client they can move everything unchanged without testing what is actually available.
## Replace invented business details
Read every public page. Confirm prices, opening hours, addresses, service areas and qualifications with the owner. Remove unsupported testimonials, stock success statistics and guarantees the business has not approved.
Check images and sample content for placeholders. A polished page can still contain an invented team member or a contact detail left over from a template.
## Exercise the important customer paths
Test the contact form, booking link, purchase flow where applicable and the messages users see after submitting. Use an agreed test method that does not create a real charge or send unwanted messages.
Verify receipt in the intended destination. A success message on the page does not prove an email arrived. Also check validation, an unsuccessful submission and the route for obtaining help.
## Test routine updates with the owner
Ask the owner to change one authorized piece of copy using their own account. Confirm what can be edited, whether saving publishes and how the previous wording can be recovered.
If the native editor meets the need, use it. If it exposes more control than the owner needs, assess the actual permission options before adding another system. ReCopyFast can provide an installed editing layer for existing website copy, but it does not replace the builder or rewrite its source files.
## Review the public site after publishing
Check navigation, links and text wrapping on narrow and wide screens. Open the public URL independently of the builder's preview. Review page titles and intended search visibility, while remembering that publication does not guarantee indexing.
Finish with a [one-page handoff record](/blog/website-handoff-checklist-client-updates): account owners, editable content, publication behavior, recovery instructions and support contacts. The website is ready for handoff when the intended operator can carry out the next real update and knows what to do when a task needs help.