Check your site before launch

A successful build or import means there is a site to review. Use your own important pages and user journeys to decide whether it is ready for visitors.

Check the site itself

• Open the homepage and the pages your main navigation and buttons lead to.
• Check header, footer, phone menu, images, and important downloads.
• Verify page addresses and old links that matter to existing visitors.
• Look for missing content, placeholders, blank pages, and layout problems that prevent use.

Small styling differences may be acceptable for your beta. Missing essential content or a broken booking, contact, or purchase flow needs attention before you depend on it.

Check content and permissions

Create a draft page or post in Content Admin. Save it and confirm it is not public. Publish it deliberately and check the public result. Understand that saving an already-published item can update it immediately.

Use separate test identities for site visitors and staff. Check what each role can see and change. Do not test destructive actions on useful customer records.

Test the features you will use

• Forms: Check required-field validation, a saved submission, and any expected notification.
• Store: Check product options, test checkout, recorded payment state, and the correct delivery result.
• Downloads or tickets: Confirm buyer access to the file, or an issued ticket and a successful test check-in.
• Site accounts: Check verification, sign-in, sign-out, and access to the correct account’s data.
• Inbox: Confirm a website question reaches Inbox, replies work, and any enabled email channel works.
• Scheduling: Check the saved schedule’s time zone and approval setting. Review an actual result before relying on unattended publishing.

Mark each applicable feature as working, failed, or not tested. An unused feature can remain disabled. Do not describe an untested feature as working.

Publish and check the public site

Follow Publish your site, then repeat the important checks at the public address. Configure live payments separately from test payments. Connect the domain only when you are ready, preserving existing email DNS records.

Keep the source site available during a migration until the important public flows pass. Report remaining problems with the page address, expected result, and observed result. See Troubleshooting.