The Complete Email QA Checklist for 2026
Every check you should run before hitting send. Organized by category, with specific items to verify and tips for automating the process so nothing slips through.
Last updated: March 2026
Email QA is the last line of defense between your campaign and your subscribers. A broken link, a wrong UTM, a missing alt tag, or a rendering failure in Outlook can cost you clicks, attribution data, or subscriber trust. Most teams rely on manual spot-checks or rendering previews alone. Both leave gaps.
This checklist covers every category of pre-send validation: metadata, links, UTM parameters, images, CSS compatibility, accessibility, and legal compliance. Use it as a reference for manual QA, or automate the entire thing with a tool that runs these checks for you.
1. Metadata & Sender Information
The fields that determine how your email appears in the inbox before it's opened. Get these wrong and open rates suffer.
Subject line is finalized and matches the campaign brief
Draft subject lines make it to production more often than anyone admits.
Subject line length is under 60 characters (or intentionally longer)
Most mobile clients truncate around 35-40 characters. Desktop clients show 60-80.
Preheader text is set and complements the subject line
If you don't set it, email clients pull the first text from the body — often 'View in browser' or navigation links.
Sender name is correct for this campaign
Sender name is the #1 factor in open decisions. Make sure it's the right brand, person, or department.
From address and reply-to address are correct
A noreply@ address is fine for transactional. For marketing, reply-to should go somewhere monitored.
Campaign code matches the brief (including country/locale suffix)
Campaign attribution in your analytics depends on exact campaign code matches.
Copyright year is current
A 2024 copyright in a 2026 email signals neglect. Check the end year in ranges.
ESP personalization tokens are valid (not broken or placeholder)
'Hello {{first_name}}' in production is a classic fail. Verify tokens resolve.
2. Link Validation
Every link in your email should resolve, point to the right destination, and be correct for this specific campaign.
All links return HTTP 200 (no 404s, 500s, or timeout errors)
Broken links are the most common email QA failure and the easiest to catch automatically.
No staging or test environment URLs remain
Links to staging.example.com or localhost slip through when copying from dev environments.
Links point to the correct landing pages for this campaign
A link can return 200 and still be wrong — pointing to last quarter's promotion or a generic homepage.
CTA button links match the intended destination
Mismatched CTA text and destination erode trust. 'Shop the Sale' should go to the sale page.
Unsubscribe link is present and functional
Required by CAN-SPAM and GDPR. Most ESPs add this automatically, but verify it works.
View-in-browser link works (if present)
If you include one, it needs to actually resolve. Otherwise, remove it.
Social media links point to correct profiles
Footer social icons are often copied from templates without updating.
No redirect chains longer than 2 hops
Long redirect chains slow load times and can trigger spam filters.
3. UTM & Tracking Parameters
UTM parameters drive your campaign attribution. One wrong value corrupts weeks of analytics data.
utm_source is set and correct (e.g., 'email', 'newsletter')
Missing utm_source means the traffic shows up as 'direct' in Google Analytics.
utm_medium is 'email' (not 'Email', 'e-mail', or blank)
Inconsistent casing creates duplicate medium entries in analytics.
utm_campaign matches the campaign identifier in your brief
This is how you attribute conversions back to the specific email send.
utm_content differentiates links within the email (e.g., 'hero_cta', 'footer_link')
Without utm_content, you can't tell which link in the email drove the click.
No test or placeholder UTM values remain (e.g., 'test', 'xxx', 'TODO')
Test values in production contaminate your attribution data.
UTM parameters are consistent across all links in the email
Mixed utm_source values within the same email create confusing analytics.
Special characters are properly URL-encoded
Spaces and special characters in UTM values can break tracking.
4. Images & Alt Text
Images are blocked by default in many corporate email clients. Alt text is your fallback — and an accessibility requirement.
All images load (no broken image URLs)
Broken images are immediately visible and destroy credibility.
Every content image has descriptive alt text
Required for accessibility. Also displayed when images are blocked.
Alt text is descriptive, not a filename ('IMG_2847.jpg') or placeholder ('image')
Generic alt text fails screen readers and wastes the image-blocked fallback.
Decorative images and spacers have empty alt text (alt='')
Screen readers skip empty alt attributes. Describing a spacer pixel adds noise.
Image file sizes are optimized (total email weight under 800KB)
Heavy images increase load time and push you toward Gmail's 102KB clipping threshold.
Images render at correct dimensions on mobile
Fixed-width images wider than 320px overflow on small screens.
Hero images have styled alt text for the images-off experience
When images are blocked, styled alt text preserves the visual hierarchy.
5. CSS Compatibility & Rendering
Email clients strip, modify, or ignore CSS differently. What works in Chrome won't necessarily work in Outlook.
Email HTML is under 102KB (Gmail clipping threshold)
Gmail clips emails larger than 102KB, hiding content behind a 'View entire message' link. Most subscribers won't click it.
No CSS properties that Outlook strips (border-radius, background-image on divs, flexbox, max-width)
Outlook uses Word's rendering engine. Modern CSS properties are unsupported.
Critical styles are inlined (not just in a style block)
Some email clients strip the <style> tag entirely. Inline styles always survive.
Dark mode colors don't invert to unreadable combinations
Email clients can force dark mode, inverting light backgrounds and text colors.
Tables are used for layout structure (not divs)
Table-based layout is still the most reliable approach for email across all clients.
Media queries are used for responsive design (with inline fallbacks)
Gmail strips media queries from non-AMP emails. Inline widths provide the fallback.
Fonts fall back gracefully in clients that don't support web fonts
Outlook, Gmail, and older clients ignore @font-face. Specify system font fallbacks.
Test rendering in top 5 clients for your audience (typically Gmail, Apple Mail, Outlook, Yahoo, mobile)
Rendering previews catch visual issues that rule-based analysis alone can miss.
6. Accessibility
Approximately 15% of the global population has some form of disability. Accessible emails reach more people and comply with legal requirements.
All content images have meaningful alt text
Screen readers depend on alt text to convey image content to blind and low-vision users.
Color contrast ratio is at least 4.5:1 for body text (WCAG AA)
Low contrast text is unreadable for people with vision impairments and in bright light.
Font size is at least 14px on desktop, 16px on mobile
Small text is difficult to read on all devices, especially for older users.
Heading hierarchy is logical (H1 followed by H2, not H1 then H3)
Screen readers use heading structure for navigation. Skipping levels confuses the flow.
Layout tables have role='presentation'
Without this attribute, screen readers announce table structure, confusing users.
The HTML tag has a lang attribute set correctly
Screen readers use the lang attribute to switch pronunciation and language models.
Link text is descriptive (not 'click here' or 'read more')
Screen reader users often navigate by links alone. 'Click here' provides no context.
Touch targets (buttons, links) are at least 44x44px on mobile
Small tap targets cause mis-taps and frustration on touchscreens.
Animated GIFs don't flash between 2-55Hz
Flashing in this frequency range can trigger seizures in people with photosensitive epilepsy.
7. Legal & Compliance
CAN-SPAM, GDPR, and CASL have specific requirements for commercial email. Non-compliance carries financial penalties.
Unsubscribe link is present and easy to find
Required by CAN-SPAM (US), GDPR (EU), and CASL (Canada). Must be functional.
Physical mailing address is included
CAN-SPAM requires a valid physical postal address in every commercial email.
Sender identity is accurate (not misleading From or Subject)
CAN-SPAM prohibits deceptive header information and misleading subject lines.
Content matches the consent scope (sending what subscribers signed up for)
GDPR requires that processing (including email) matches the consent given.
Privacy policy link is present
Best practice for GDPR compliance and subscriber trust.
List-Unsubscribe header is configured in your ESP
Gmail and Apple Mail display a native unsubscribe button when this header is present.
Automating Your Email QA Checklist
Running through this checklist manually on every email send is thorough but time-consuming. Most teams skip items under deadline pressure. The checks that get skipped are the ones that cause production incidents.
The best approach is to automate the mechanical checks and focus human attention on the judgment calls. Here is what can be fully automated:
Checks you can automate today
Checks that benefit from AI judgment
Run this entire checklist automatically
Email QA Tool automates the mechanical checks from this list and adds AI judgment for subject lines, CTAs, content, and compliance. Upload your HTML, tell it what to check, and get results in seconds. Fix issues inline without touching code.
Free trial includes 5 emails with all checks. No account required to start.