How do I perform a Content & UX QA for Mail LP?
Ensure that one-page landing pages created for mailer campaigns are accurate, consistent with the approved mailer, and fully functional. These pages should clearly reflect the promotional message and be optimized for user engagement and conversion.
Content & UX QA checks a Direct Mail landing page (the page a mailer's QR code opens) before Lead Review and before the client sees it. Keep the approved mailer PDF open the whole time: the page must match it.
Before you start
- Open the client's Build Out To Do List (the link is in the HubSpot ticket's Buildout To Do List field).
- Check that the designer's Mail LPs tab is complete. Every box should be ticked. Leave a BugHerd note for the designer on anything that isn't.
- Read the handoff document. Answer the open items that are for QA, and pass the rest to the client, Onboarding Lead/Specialist or the Creative Lead.
- Open the Mail LP link and check that the BugHerd sidebar loads, and that the install-script step is marked done in the BugHerd project.
Option A: QA with Claude
Use this when you have Claude. Copy the prompt below into Claude, fill in each source, and send it. Claude's report is your first pass: review it, then log the real issues in BugHerd. If Claude isn't available, use Option B.
I need a final Content & UX QA for this Direct Mail landing page. Don't change anything on the site or in any tool. Only check and report. Sources (paste a link or the text after each): 1. Mail LP link: 2. Mailer PDF (Mailer Final Creative File): 3. QR code link (dmredirects.com): 4. Handoff document (handoff.md): 5. HubSpot company: 6. HubSpot ticket: 7. Build Out To Do List (Mail LPs tab): 8. Slack channel: 9. Drive folder: What to check: - Every step in the Mail LPs tab of the Build Out To Do List. - Every special matches the mailer word for word: name, price, description, conditions, expiration date and fine print. - Every call button shows the direct mail tracking number from HubSpot (the number printed on the mailer is different on purpose). - The URL is promo-<client>.dentist-near-me.com (multi-location: promo-<client>-<location>.dentist-near-me.com), and the QR code link opens this page. - Anything the client or team asked for in the ticket or the Slack channel. - Proofreading: spelling, grammar, capitalization, spacing, punctuation, placeholder text (lorem ipsum, template text) and em dashes. - Google Ads banned terms (https://support.google.com/adspolicy/answer/2430794), such as Botox, Nitrous Oxide and Neuromodulator. Flag each one with a compliant alternative. How to report: 1. A table of every check: Pass, Fail or Couldn't check, the page or section, and what you saw. 2. Issues ready for BugHerd, one per line: page, what's wrong, the fix. Don't create BugHerd tasks until I confirm. 3. Open items for the handoff document, each with who it's for: the client, the Onboarding Lead/Specialist or the Creative Lead. If a source is missing or you can't open something, say so. Never guess.
Some checks need a real person and device, so always do these by hand:
- Scan the QR code on the mailer with your phone.
- Tap-to-call on a real phone.
- Submit the form once and confirm it goes to the Thank You page.
Option B: QA without Claude
Use this when Claude isn't available. Work through each part below.
The checks
- Mailer: open the mailer PDF (the Mailer Final Creative File on the ticket).
- Offer: every special matches the mailer word for word: name, price, description, conditions (for example new patients only), expiration date and fine print. The offer is easy to see.
- Headline and brand: the headline matches the mailer. Logo, favicon and colors match the brand and the mailer. The hero photo fits the practice and its demographics.
- Phone: every call button shows the direct mail tracking number from HubSpot, and tap-to-call works on mobile. The number printed on the mailer is different on purpose.
- Practice info: practice name matches HubSpot. Address, map and office hours are correct. Book Now goes to the practice's booking link. Reviews are for this practice and doctor, with no duplicates.
- Copy: no lorem ipsum, typos or em dashes. One H1 with the city and state.
- Links and forms: the Thank You, Privacy Policy and Accessibility pages are updated and their links work. Submit the form once and confirm it goes to the Thank You page.
- GTM: view the page source, search for GTM- and confirm the ID belongs to this client.
- URL: the page is at promo-<client>.dentist-near-me.com (multi-location: promo-<client>-<location>.dentist-near-me.com).
- QR code: the dmredirects.com link opens this page. Don't change the redirect yourself: Gina must be told before any change.
- Devices: check desktop, tablet and mobile. Nothing overlaps or is cut off.
Ad compliance: banned terms
Google Ads can disapprove ads that lead to pages with restricted medical terms. Search the page (Ctrl+F / Cmd+F) for the terms on the internal Banned Terms List, such as Botox, Nitrous Oxide and Neuromodulator.
- Log each one as a BugHerd task with a Google-compliant alternative.
- Ask the Compliance Lead if you're not sure about a term or its replacement.
Proofreading
Read all the text on the page for typos, placeholder text and em dashes. If you have another AI tool, paste the text in with this prompt:
Act as a proofreading expert tasked with analyzing the copy below. Your job is to identify any misspellings, spelling inconsistencies, case inconsistencies, errors in spacing, and missing punctuation. Additionally, search for any terms that are banned by Google, as listed on this page: Google Ads Policy - Banned Terms (https://support.google.com/adspolicy/answer/2430794). Flag any banned terms and point out their occurrence in the text. Also, check for placeholder copy (such as Lorem Ipsum), em dashes or other errors and flag them accordingly. Do not make changes to the copy; just highlight the issues that need attention.
Check each flagged issue and log the real ones in BugHerd.
How to report issues
- Log every issue as a BugHerd task on the page where it appears, assigned to the designer.
- Don't edit the site yourself. The designer makes every change, so the code and the checklist stay in sync.
Wrap up
- Check that every issue is a BugHerd task assigned to the designer.
- Update the handoff document with anything still waiting on the client, Onboarding Lead/Specialist or the Creative Lead.
- Update the HubSpot ticket: note that QA is done and what is left, then move the ticket on.
- Mark your task as done in Monday. On the Projects board, update the project's person and status.
The BugHerd sidebar comes off at launch. After QA, the Creative Lead does the Lead Review before the page goes to the client.