Testing complete user flows instead of pages is the advice I wish more launch checklists started with. A form that shows a success message while the stored and delivered chain is broken is the most common gap I see, and the client usually learns about it from a customer who never heard back.

The lost response plus retry case is a good one to include, because duplicates look like a backend problem and are really a launch testing problem. The same goes for redirects. Mapping old URLs to specific 301s instead of sending everything to the homepage protects years of search history that a redesign can quietly throw away.

"A staging pass is evidence about staging" should be printed on every handover document. Naming a website owner after launch is the part small businesses skip most often, since the agency leaves and nobody inherits the forms.

Do you recommend a fixed set of flows to retest after every content update, or only after code changes?