Official skill · Marketing

Marketing email review before send

v1.0.1 · Updated 4 November 2026

Checks a marketing email before send: subject and preheader, one CTA, mobile scan, links, merge-tag fallbacks and the footer. Use it when A newsletter or promo email is ready and you want a check before it goes out.

Add to my team's pod

Works in Claude, ChatGPT, and coding agents. On Team and Business, the official skill in your pod updates itself when we improve it.

When to use it

A newsletter or promo email is ready and you want a check before it goes out
Opens or clicks dropped and the next send needs a second look

What you give it

The email with subject, preheader, body and links
Audience and the email's one goal
Merge fields and fallbacks
Sender and list region

What you get

A send or fix-first verdict, exact line edits split into must-fix and worth-changing, and a checklist.

How it works

Check the inbox view The subject must not mislead about what's inside (CAN-SPAM). Our defaults: subject under 50 characters, no ALL CAPS words, no more than 1 emoji. Preheader under 90 characters, adds to the subject instead of repeating it, and isn't the default "View in browser" text. Sender name is a person or the brand people recognize.
Find the one CTA Count distinct actions. Our default: one primary action, repeated at most twice (button above the fold and once near the end). Two or more different actions is a fix-first unless it's a newsletter. Button label is verb-first and names the result ("Book your seat", not "Click here").
Scan as a phone reader Our default: assume a 375 px wide screen. The point and the button should be visible within the first screen (about 4 short lines plus a button). Paragraphs of 3 lines or fewer. Text is live text, not an image. Images have alt text.
Check every link Each URL goes where its label says, has UTM tags if the team uses them, and none points to a staging or preview domain. Flag duplicate links with different UTMs.
Test personalization For each merge tag, read the sentence with the fallback in place ("Hi there,") and with an empty value ("Hi ,"). An empty-value bug is fix-first.
Check compliance US (CAN-SPAM, per the FTC): accurate From and Reply-To, the email clearly identified as an ad, a valid physical postal address, and a clear way to opt out, honoured within 10 business days. Every sender to Gmail keeps the spam rate in Postmaster Tools below 0.3% (Gmail's target is below 0.1%). Gmail and Yahoo, for bulk senders (Gmail: more than 5,000 messages a day to Gmail accounts), also require one-click unsubscribe in the headers (RFC 8058) plus a visible unsubscribe link in the body, SPF, DKIM, and a DMARC policy (p=none is enough). Yahoo asks that unsubscribes are honoured within 2 days. Authentication and spam rate live outside the email; if the user can't confirm them, list them as "[check: sending setup]". Our default: a line saying why the reader gets this email. EU, UK, and other lists have their own consent rules; mark "[check: legal]" rather than stating law you haven't confirmed.
Give the verdict Fix first if any of these: broken or empty merge tag, missing unsubscribe or address, a wrong or staging link, no clear CTA, or a factual claim (price, date) that contradicts the input. Otherwise send, with optional edits.

Share it with your team

Add it to an AI Skill Pod and everyone on the team, contractors included, uses the same version from their own AI. Read the best ways to share AI skills with a team