A website launch checklist for coding agents / Galactrex

Before the agent builds: define one real journey

Use Brief to turn one real use into a spec, agent rules and tasks. Name the visitor, what they need to do and what proves the journey works. Leave unanswered decisions visible instead of letting a generated implementation turn them into assumptions.

Write down the route from entry to success: for example, product page, sign-in, offer selection and confirmed access. Define the empty, loading and failure states as part of that journey. A screenshot of the landing page does not prove the flow.

Before deployment: check what is exposed

Use Leak Check for a project folder or public page to find exposed files, keys and risky settings. Read the findings and fix the items that matter for the actual deployment.

A public check cannot prove every access rule. Test signed-in and signed-out behavior, plus different account roles where relevant. Keep private configuration outside the public output and verify that a guessed private URL does not reveal its contents.

After deployment: audit the page people receive

Use Launch Check against the actual public address. Review the server response, index rules, canonical URL, title, description, share image and sitemap membership. Check that the correct HTTPS URL loads and that referenced assets exist.

Open the page on a phone and in a fresh browser session. Follow its primary action, not just the hero animation. Test the URLs people will share or find through search, including direct links to individual products and guides.

Make the content worth the click

A useful page tells visitors what the product does, who it fits, how to start and what its limits are. Use a title and description that match that page. Link a product to its setup guide and give the guide a clear route back to the working app.

Keep public facts readable without account access. Authentication can protect the app's private work while the public product page explains it. Structured data should describe the visible facts; it is not a place for fabricated reviews or features that have not shipped.

Check the result and leave a release trail

Brief is included in Creative. Leak Check uses Creative access; Launch Check's public tool page shows the current access and run limits. Sign in and check the plan information before a run.

Record the changed routes and their runtime dependencies, publish the intended release and verify the new assets through a fresh browser. Automated findings guide the work; they do not certify the whole site's security or guarantee a search rank. Use real search and journey data to judge the next improvement.