← Syntax Orbit home

Syntax Orbit · Project guide

What to check before launching a business website

Review public content, navigation, forms, search metadata, release checks, and ownership before a website goes live.

Check the public journey from a fresh visit

Open the site in a fresh browser session and follow the main visitor journey from beginning to end. Test the navigation from inner pages as well as the homepage. A Contact link that works on the homepage can still send someone to the wrong place from a preview or article page.

Read the actual published copy. Remove placeholder businesses, sample testimonials presented as real ones, outdated contact information, and claims that cannot be supported. Label demonstrations clearly so they are not mistaken for completed client work.

Treat forms as a complete interaction

A form needs understandable labels, sensible validation, and a clear result. Test required fields, an invalid address, a failed request, and a successful submission using agreed test details. Confirm that the message reaches the intended inbox before considering the form complete.

Collect only the information needed for the enquiry and link to an explanation of how it is used. Do not ask visitors to send passwords, payment details, or other unnecessary sensitive information through an ordinary project-enquiry form.

Check content delivery and page metadata

Make sure each important public URL returns the intended page and an appropriate status. Check the page title, description, and canonical URL. A site-wide canonical that points every article to the homepage misrepresents which page is the preferred version.

Read the initial HTML as well as the interactive page. Core text and links should be available reliably even if a decorative script fails. A sitemap helps describe the public URLs; it does not replace working navigation or guarantee indexing.

Plan the release and the next day

Before deployment, record what version is being released, how it will be checked, and how to return to the previous version if something goes wrong. Verify HTTPS, redirects, images, and contact routes on the live domain after deployment.

Assign responsibility for content updates, dependency maintenance, and incident reports. Agree how backups are made and how recovery is tested. A launch is complete when the website works and the people responsible for it know how to keep it working.