A post-release checklist for your marketing website

A landing page can return HTTP 200 while its form fails, its campaign parameters disappear on a redirect, or its production template still carries a staging noindex directive. Run these checks on your pricing, signup, and demo pages after a release.

Run these checks on the live site

Print this checklist or copy it into the release ticket. For each item, record the owner, tested URL, device, timestamp, and a link to the evidence.

• Lead form. One successful test creates one backend record. Invalid inputs and failed requests leave a clear recovery path.
• Conversion event. One confirmed submission sends one event to the intended destination. Failed submissions and confirmation-page reloads send none.
• Campaign redirect. Open a URL with test campaign parameters. Check each redirect and the final URL for the expected parameters.
• Mobile load. Reproduce the experience on a representative device. Compare field data for the same page and device class when available.
• Indexability. Confirm the production canonical and robots directives match what you intend for each public page.

Submit a test lead

Start from a tagged campaign URL and submit a test lead on a mobile viewport. Check the success state and verify the record in your CRM or form backend. Try an invalid input and a double click. Verify that an unsuccessful submission shows a recovery path and that a retry creates at most one lead.

Check what your analytics recorded

Follow the event from the page to the intended reporting destination. A button click can fire while the form request fails. Use a confirmed success event for reporting, then test one successful submission, one failed submission, and one reload of the confirmation page. Follow the conversion tracking diagnostic for the detailed steps.

Check real mobile performance

Use lab tools to reproduce a slow page and field measurements to see how common the experience is. Compare the same URL, device class, and period. If load time worsened, inspect what changed in the page’s largest content element or its critical resources before removing scripts at random.

Verify indexing expectations

Check the deployed page for the intended canonical and robots directives. If a page is meant to appear in search, confirm that the canonical points to the correct production URL and that the page is eligible for indexing. An intentional noindex on a confirmation page is expected. Google Search Central SEO guide

For any failure, add the expected and actual result to the release ticket. For example, “Mobile Safari on /request-demo, 10:24 UTC. Success message appeared, but there was no backend record. Inspect the form request and repeat the test after the patch.” Keep test email addresses and other personal details out of shared screenshots.

Explore a sample investigation to see how observed goal activity and browser errors can help you choose what to reproduce.