HTML Email QA Checklist (2026): 25 Tests Before You Send

Sending an HTML email without QA is like launching a website without previewing it on mobile, desktop, and different browsers—except email is harder. Each inbox (Gmail, Outlook, Apple Mail, Yahoo, mobile apps) interprets HTML differently, and small mistakes can lead to broken layouts, missing images, clipped messages, spam placement, or subscribers clicking the wrong thing.

This 2026 checklist gives you 25 must-do tests you can run before every campaign. Use it whether you build emails with a drag-and-drop builder or you code custom HTML and import it.

If you’re working with Mailpro, you can build and edit emails in the Email Builder, or bring your own code via Import HTML. If your email lives on a web page (or you’re copying HTML from a URL), you can also use Import URL/HTML.

How to use this QA checklist

1. Run the quick critical tests first (links, subject line, preheader, unsubscribe, mobile).
2. Then check rendering (desktop + mobile + dark mode) and deliverability risks (spam triggers, authentication alignment).
3. Finish with tracking and post-click checks (UTMs, landing pages, conversions).

Tip: Save these steps as an internal SOP and require a second person to sign off before important sends. One extra pair of eyes prevents expensive mistakes.

HTML Email QA Checklist (2026): 25 tests

A) Message essentials (tests 1–6)

1) Subject line passes the “truth + clarity” test

Read your subject line and ask: is it honest, specific, and aligned with the email content? Avoid misleading phrasing that causes quick deletes or spam complaints. In 2026, inbox providers heavily reward “expected mail” and punish bait.

2) Preheader text is intentional (not “View in browser…”)

Many inboxes show 40–100 characters of preview text. Make sure your preheader supports the subject line and doesn’t accidentally reveal template leftovers, random navigation text, or “Click here if images don’t load.”

3) “From name” and “From email” match brand expectations

Consistency matters. If subscribers signed up for “YourBrand Weekly,” don’t suddenly send from “Marketing Team” or a new domain. Unexpected sender identity increases spam reports and reduces opens.

4) Reply-to is correct and monitored

If your campaign invites replies (questions, RSVPs, quotes, support), your reply-to must go to a real inbox someone checks. Even if you don’t expect replies, some subscribers will respond—and those replies are valuable signals and feedback.

5) Audience and segmentation are correct

Confirm you’re sending to the right list, the right segment, and the right language group. Double-check exclusion rules (internal staff, test accounts, previous purchasers, etc.). A perfect email sent to the wrong people is still a failure.

6) Send time is correct (time zone + day)

Verify scheduled time and time zone. Many teams accidentally schedule a “Monday morning” send for the wrong region or send at midnight because of a mismatch between account time and local time.

B) Links, CTAs, and navigation (tests 7–11)

7) Every link works (and goes to the correct page)

Click every link—yes, every one—including logo links, footer links, icons, buttons, and social icons. Look for:

• Typos, missing https, or broken redirects
• Wrong language version (EN landing page for ES subscribers)
• Links that accidentally point to staging or old campaigns
• Links that open to 404 pages on mobile

8) Button CTAs are tappable on mobile

A CTA that looks fine on desktop can be frustrating on mobile if it’s too small or too close to another link. Aim for comfortable tap targets and enough spacing. Test with your thumb, not just your mouse.

9) Primary CTA appears above the “scroll cliff”

You don’t need to cram everything at the top, but your main action should appear early—especially for promotional or time-sensitive emails. If your CTA only appears after long intro text, many readers will never reach it.

10) “View online” (web version) works if you use it

If you include a web-view link, test it. It’s often used by recipients with strict image blocking or unusual clients. A broken web version damages trust and support load.

11) Footer links are complete and compliant

Confirm your footer includes required elements for your region and email type:

• Unsubscribe link (functional)
• Sender identity (company/brand name)
• Physical address where applicable
• Privacy policy link if you reference tracking or personalization

C) Rendering and layout (tests 12–17)

12) Test in at least 3 major inboxes: Gmail, Outlook, Apple Mail

At minimum, preview in:

• Gmail (web + mobile app)
• Outlook (desktop + web if possible)
• Apple Mail (iOS and/or macOS)

Why: Outlook still behaves differently than many clients, and iOS Mail has its own quirks. You want to catch spacing issues, font fallbacks, and broken columns before your audience does.

13) Mobile layout is readable without zooming

Check that:

• Text is legible (avoid tiny font sizes)
• Line lengths are comfortable (no long single lines)
• Padding doesn’t collapse
• Columns stack properly

14) Dark mode doesn’t break contrast

Dark mode is no longer optional. Test your email in dark mode environments (iOS Mail, Gmail app, Outlook). Look for:

• Logos disappearing on dark backgrounds
• Text color getting inverted in ugly ways
• Buttons losing contrast
• Images with transparent backgrounds looking strange

15) Images don’t cause layout shifts when blocked

Many clients block images by default. Turn images off and review the email:

• Does the layout still make sense?
• Do headlines still communicate value?
• Do buttons still look like buttons?
• Are there large empty gaps?

16) Key content is live text (not baked into images)

Avoid placing your headline, offer, or critical details only inside an image. Live text is more accessible, more searchable, loads instantly, and is more resilient to image blocking.

17) Font fallback looks acceptable

Many email clients don’t support custom web fonts reliably. Ensure your fallback stack looks good (spacing, weights, and line heights). If your design depends on one specific font to “work,” it’s likely to break somewhere.

Working the QA list? Mailpro’s plans include client previews and test sends — so you catch the broken bits before your subscribers do.

D) Content quality and deliverability risk (tests 18–22)

18) Spam-trigger risk check: balance text, links, and images

A single factor rarely sends you to spam—but combinations do. Watch for:

• Too many links (especially shorteners)
• Image-heavy emails with minimal text
• Overly aggressive language (ALL CAPS, too many exclamation marks)
• Suspicious formatting (hidden text, tiny font, odd characters)

Keep a natural, readable layout and avoid “shouting” promotions. In 2026, engagement signals matter more than gimmicks.

19) Authentication alignment check (SPF, DKIM, DMARC)

Before sending at scale, confirm your sending domain is properly authenticated and aligned. If your message fails authentication or alignment, it may be rejected or routed to spam—especially at corporate domains.

20) “From domain” matches the links and branding

If you send from one domain but your links or images load from a completely different domain, some filters treat it as suspicious. Consistency helps trust and deliverability. This is especially important for transactional-style campaigns and security-sensitive audiences.

21) No broken personalization tokens

If you use personalization (first name, company, dynamic content), test it with:

• A contact that has the field filled
• A contact that does not have the field filled

You want graceful fallbacks like “Hi there,” instead of “Hi {{firstname}},”.

22) Legal compliance check (unsubscribe + consent expectations)

Confirm that:

• Unsubscribe is one click (or very close) and works
• Your email matches what the user consented to receive
• You’re not emailing people who opted out
• Your footer includes required sender information where applicable

Even when local laws differ, the safest path is to follow best practices: transparent identity, easy opt-out, and respectful frequency.

E) Tracking, measurement, and post-click experience (tests 23–25)

23) Tracking parameters are correct (UTMs or analytics tags)

If you use UTMs, confirm consistency:

• utm_source, utm_medium, utm_campaign are spelled consistently
• Campaign names follow your naming rules (no random variations)
• Links aren’t double-tagged or broken by extra characters

Clean tracking makes reporting meaningful. Messy tracking makes teams argue with data instead of improving campaigns.

24) Landing pages load fast and match the promise

Click your main CTA on mobile data and check:

• Loads quickly (especially images and scripts)
• Matches the offer and message from the email
• Has clear next steps (purchase, signup, download, book)
• Doesn’t show a pop-up that blocks the content immediately

25) Final “human test”: read it like a subscriber

Before you send, do one last read-through asking:

• Would I understand this in 5 seconds?
• Is the message helpful or relevant?
• Is there one clear action?
• Is the tone consistent with my brand?
• Is anything confusing, awkward, or too long?

This sounds simple, but it catches embarrassing errors that tools won’t.

Extra QA tips for teams that send frequently

Create a repeatable pre-send workflow

If you send weekly or daily, consider a two-step workflow:

1. Creator completes checklist items 1–22 and sends a test email to internal reviewers.
2. Reviewer confirms items 7–17 (especially links and rendering), then signs off on 23–25.

Keep an “approved modules” library

Most layout issues come from reinventing the wheel. Build a small library of proven blocks:

• Header + logo module
• Hero section with headline + CTA
• 2-column product block that stacks correctly
• Testimonial module
• Footer module with compliance links

Whether you build in the Email Builder or import custom HTML, consistent modules reduce QA time and surprises.

When importing HTML, QA the code structure too

If you’re bringing in custom code, do an additional quick scan:

• Are tables properly nested and closed?
• Are image dimensions set to prevent jumps?
• Is there any unsupported CSS that might break Outlook?
• Are there accidental extra wrappers that create unexpected spacing?

In Mailpro, you can import a custom template using Import HTML. If you’re pulling HTML from a webpage or URL, use Import URL/HTML to bring the content in—then run the same rendering checks.

Quick printable version (copy/paste)

If you want a fast version to paste into your internal docs, here’s the checklist in one place:

1. Subject line is clear and honest
2. Preheader is intentional
3. From name/email are consistent
4. Reply-to is correct
5. Audience/segment is correct
6. Send time + time zone verified
7. All links work and go to the right pages
8. Buttons are tappable on mobile
9. Primary CTA appears early
10. Web-view link works (if used)
11. Footer links are complete and compliant
12. Preview in Gmail, Outlook, Apple Mail
13. Mobile readability: no zooming needed
14. Dark mode contrast is safe
15. Layout still works with images off
16. Key message is live text
17. Font fallback looks fine
18. Spam-risk balance: text/links/images
19. SPF/DKIM/DMARC aligned
20. Domains match branding and links
21. Personalization tokens tested with fallbacks
22. Unsubscribe + consent expectations met
23. UTMs/analytics tags verified
24. Landing pages load fast and match promise
25. Final human read-through

Conclusion

In 2026, inbox competition is intense. The brands that win aren’t just the ones with the best offers—they’re the ones that deliver a smooth experience: correct rendering, fast reading, trustworthy identity, and clean post-click journeys.

Use this checklist before every send, and you’ll catch the problems that quietly destroy performance: broken links, dark mode disasters, confusing CTAs, compliance gaps, and tracking mistakes.

Whether you build from scratch using the Email Builder, or bring in your own design with Import HTML (or Import URL/HTML), the QA habit is what turns “nice emails” into reliable results.