White Page and Target Page QA Checklist

Record the White Page and Target Page URLs, release identifiers, host owners, intended markets, language, and campaign. Confirm the approved artifact before testing so a later deployment cannot be mistaken for the reviewed page.

Check title, headings, text, images, disclosures, links, forms, error states, and responsive layout. Verify each page on its own merits; a correct destination selection does not certify the page's claims or policy compliance.

Inspect HTTPS, redirects, asset requests, console errors, cookies, query parameters, performance under ordinary conditions, and unknown paths. Repeat through the configured redirect, reverse proxy, or iframe mode because delivery can change behavior.

For every intended Target case, include a corresponding conservative or exceptional case expected to receive White Page. Compare visible response, final URL where relevant, event reason, and campaign attribution.

Store screenshots or response evidence, test events, unresolved defects, approver, and test date beside the page versions. Keep the previous working page available until the new pair survives the agreed monitoring window.