Template Provenance Check (QA)

Template Provenance Check (QA)

1. 01

   Freeze the template and page inventory before any client-facing review

   Export the list of every template, section, and global style in use, then lock edits so QA runs against a fixed build rather than a moving target.

2. 02

   Verify the AI-generated copy against the client's own source material

   Compare headline, service descriptions, and meta text to the client's brand guide and prior campaign language; flag any claim the client has not approved in writing.

3. 03

   Test the site on the three devices your client's audience actually uses

   Pull device share from the client's analytics, then check layout, tap targets, and form behavior on those viewports instead of a generic desktop-mobile-tablet sweep.

4. 04

   Confirm forms, checkout, and booking flows submit to a destination the client owns

   Send a live test submission and trace where the record lands; a form that posts to the builder's default inbox creates a data custody problem at handoff.

5. 05

   Check indexation and structured data before launch, not after

   Confirm canonical tags, sitemap submission, and schema fields resolve correctly, since retrofitting these on a live site costs more than catching them in staging.

6. 06

   Document which builder features are native versus plugin-dependent

   Note every third-party dependency, its renewal date, and who holds the license, so the client is not surprised by a lapsed subscription three months into the retainer.

7. 07

   Record the QA result per page with a named reviewer and timestamp

   A pass or fail line per page, signed by the person who checked it, gives the agency a defensible record if the client disputes a defect later.