What should you check before launching an AI-built website?

List the services, audiences, approved evidence, and next step. Ask the tool to help organize those facts, then check every resulting claim. It shouldn't invent customer quotes, project photos, credentials, or price policies.

A prototype may demonstrate a form without delivering its messages. A button may look like a booking integration while linking nowhere. Mark these as unfinished functionality during development.

Check account access, content, inquiries, privacy, and publishing before launch. Assign someone to verify each area.

Open the site as a new visitor on a narrow screen. Follow a service link, read the relevant proof, and reach the form by keyboard. Try an invalid submission, a controlled provider failure, and an accepted test. Check receipt separately with authorization.

Repeat with optional analytics declined. The form should still work. Look for personal details in URLs, analytics requests, browser logs, and error messages. A visual preview doesn't establish these behaviors.

Identify the framework, dependencies, third-party services, and renewals. Keep secrets outside public source and browser bundles. Apply updates through a reviewable process and test the affected behavior before release.

Record how to recover access, restore an approved version, and respond if a form stops working. A system nobody can maintain can be expensive even if its first draft was cheap.

If your requirements are small and you can verify the system, a DIY build may be a reasonable choice. If you need migration, custom workflows, sensitive data handling, or substantial writing, compare the time and expertise those tasks require.

Use the website proposal comparison to compare responsibilities. For an existing site, the repair-or-rebuild guide helps define the actual problem before choosing a platform.

Save the approved scope, test conditions, results, open defects, and person responsible for each dependency. Separate what was demonstrated from what still needs account access or owner confirmation.

DewBwah's website service describes its writing and implementation scope. It doesn't replace the need to agree on project-specific ownership, hosting, revisions, and ongoing support in the proposal.