Websites / Cloudflare
Website Launch Readiness and Deploy Verification
Needs review — This SOP contains our content but has not been verified by Nick. Treat as a working draft until marked Live.
Website Launch Readiness and Deploy Verification
Section titled “Website Launch Readiness and Deploy Verification”Use this SOP when a website change, clone sync, launch task, or post-merge deployment needs to be verified before the client or CSM is told it is live.
Who owns it
Section titled “Who owns it”Primary owner: Website / SEO Specialist Current assignee: Jakob Supporting owner: Operations for deployment access and CSM for client closeout
- Confirm the exact repo, branch, commit, preview URL, and production URL involved.
- Verify the build or deploy run completed successfully before checking the site.
- Open the affected route and confirm the expected marker, copy, component, or fix is present.
- Check critical conversion paths: phone links, primary CTA, forms, thank-you behavior, tracking scripts, and navigation.
- If this is a launch or cutover, confirm DNS, Cloudflare Pages custom domain, SSL, redirects, noindex/indexing policy, and canonical behavior only within the approved scope.
- Record the deployment evidence and any item that still needs Nick, Operations, or CSM action.
Definition of done
Section titled “Definition of done”The deploy is verified when the run succeeded, the expected change appears on the right URL, conversion paths still work, and the handoff notes clearly say whether the client-facing page is ready to announce.