# Page Test QA Checklist

Before launching a page experiment, run through this checklist to make sure everything is working correctly. A broken variation can skew your results and create a bad experience for visitors.

***

### Visual Check

* [ ] **Visit the control page** — Confirm it looks exactly like your current live page with no changes
* [ ] **Visit each variation** — Verify your design changes are appearing correctly
* [ ] **Check on mobile** — Load each variation on a mobile device (or mobile emulator). Layout issues are most common on smaller screens.
* [ ] **Check on desktop** — Verify each variation on a full-width desktop browser
* [ ] **Check on tablet** — If your audience has significant tablet traffic, test that too
* [ ] **Compare side by side** — Make sure the only differences between control and variation are the changes you intended. Watch for unintended differences in spacing, fonts, or missing sections.

### Functionality Check

* [ ] **Add to Cart button works** — Click "Add to Cart" on each variation and confirm it adds the correct product
* [ ] **Navigation works** — Click through menus, breadcrumbs, and internal links on each variation
* [ ] **Product images load** — Verify all images, thumbnails, and galleries render correctly
* [ ] **Forms work** — If the page has forms (email signup, contact, etc.), test them on each variation
* [ ] **Videos and media play** — If your variations include embedded video or other media, confirm they load
* [ ] **Quick view / modals work** — If your theme uses quick view popups or modals, test them on each variation

### Third-Party Apps

* [ ] **Reviews app displays** — Confirm your reviews widget (Judge.me, Loox, Stamped, etc.) shows up on each variation
* [ ] **Upsell/cross-sell apps work** — Check that any upsell widgets or "frequently bought together" sections appear
* [ ] **Subscription widget works** — If the page has a Subscribe & Save option, verify it's functional on each variation
* [ ] **Live chat / support widgets load** — Confirm chat widgets (Gorgias, Tidio, etc.) appear on each variation
* [ ] **Trust badges and seals display** — Any trust badges or security seals should be present

### Tracking Verification

* [ ] **Page view is tracked** — Visit each variation and confirm a page view event appears in the experiment's Raw Data → Events table
* [ ] **Correct variation is assigned** — Check that the event shows the right variation ID
* [ ] **Add to Cart event fires** — Add a product to cart and verify the event appears
* [ ] **Consistency on revisit** — Close and reopen the page. Confirm you see the same variation (cookie-based assignment should persist).

### Template Check

* [ ] **Correct templates are assigned** — In the experiment overview, verify each variation is pointing to the intended template
* [ ] **No 404 errors** — Each variation URL should load correctly, not show a "page not found" error
* [ ] **Template changes are saved** — If you recently edited a template in the Shopify theme editor, confirm the changes are live

### Multi-Page Experiments (If Applicable)

* [ ] **Test across multiple products/pages** — If your experiment runs across all product pages (or all collection pages), visit several different pages within that type to confirm the variations are loading consistently
* [ ] **Scoped products work** — If you scoped the experiment to specific products, confirm the experiment only runs on those pages and not on other product pages

***

### Quick Test Flow

If you're short on time, at minimum do this:

1. Visit the page in a fresh incognito/private window
2. Verify you see one of the variations
3. Add a product to cart
4. Go through checkout (or at least start it)
5. Check the Raw Data tab in Elevate to confirm events were tracked

This covers the most critical path — if this works, the fundamentals are solid.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.elevateab.com/elevate-helpcenter/page-testing/page-test-qa-checklist.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.