From a website to a verified launch

Before you start

• A compatible Codex or Claude Code account, access to your own website project and permission to inspect or change it. INMC is optional and does not supply AI credits.
• One intended audience, one primary action and approved brand assets. Use a test environment first; prepare an approved test recipient if you will test email delivery.
• Search Console needs a verified property and the correct account. Public launch, DNS, paid services and permissions are separate decisions. No exact usage saving or search ranking is promised.

How to use it

1. Replace the placeholders and paste the prompt in your website project. Start with inspection and the five-line brief. Do not ask for a complete redesign before identifying a specific problem.
2. Run the readiness table. For a form, separately check validation, submission receipt and delivery to the approved destination; a button click or success toast alone is insufficient.
3. Authorize the smallest needed fix. Recheck its acceptance criterion at a narrow mobile width and with keyboard navigation. Keep untested cases marked UNVERIFIED.
4. When the public page is ready, verify title, canonical, index/noindex intention, crawlable links and sitemap. Use your verified Search Console property and distinguish submission from Google indexing.
5. Save the evidence and remaining blockers in a handoff. If capacity is low, reduce the task scope and continue later; do not weaken acceptance checks just to finish.

ILLUSTRATIVE EXAMPLE

Make it concrete.

Illustrative scenario: a solo founder has a one-page service website. The primary action is “Request a consultation.” The mobile page looks correct, but the form only shows a toast and delivery has not been tested. Mark delivery UNVERIFIED; use an approved test address, confirm the stored receipt and destination delivery before calling the lead flow ready. This is not a measured customer case study.

Expected output

• A five-line brief: audience, job, primary action, constraints and unknowns.
• A table with criterion, PASS/FAIL/UNVERIFIED, evidence and next check; each claim traces to something actually observed.
• A short list of launch blockers and a handoff. Example: “Form UI PASS; durable receipt PASS; email delivery UNVERIFIED; next: one authorized destination test.”

Check the result

• The site has one clear action and the copy matches the intended audience.
• The action works with keyboard and mobile layout; the form result distinguishes storage, delivery and recipient acknowledgement.
• Only the intended public HTML is eligible for indexing. Private/admin/technical routes stay excluded; duplicate Markdown retains its canonical HTML.
• No unsupported claim says Google indexed, ranked or certified the site. The primary workflow can still be used without the paid pilot.

If the result is off

• No project access: provide relevant non-sensitive files or screenshots and ask for an inspection-only plan. Do not share passwords or session links.
• Form email does not arrive: inspect storage, relay status and the authorized destination separately. Keep it unverified; do not send repeated tests to real customers.
• The AI keeps redesigning: restate the specific failure, brand constraints and one acceptance criterion. Work on one blocker.
• Search Console is unavailable: finish the public page and record the access step as pending; do not bypass verification or CAPTCHA.