Gmail’s bulk-sender rules apply to senders that send more than 5,000 messages a day to personal Gmail accounts: marketing messages need one-click unsubscribe headers and a visible link in the message body. A missing or broken opt-out can therefore fail both a recipient’s basic expectation and an important sending requirement.
An unsubscribe footer is the visible link in an email body that lets a recipient stop marketing messages or manage subscriptions. It is separate from the List-Unsubscribe header, which compatible mail clients can use to offer an opt-out outside the message. Put a clear working link in marketing messages, connect it to prompt suppression or preference updates, and use the header as an additional route—not a replacement.
What is an unsubscribe footer?
It is the recipient-facing opt-out route within the email itself, usually placed near the bottom with the sender’s identity and subscription information. The link should make the action clear without requiring the reader to hunt through the message or understand email headers. Under the FTC’s CAN-SPAM guidance, commercial email must give recipients a clear and conspicuous explanation of how to opt out.
The visible link and the List-Unsubscribe header are different parts of the message. A link appears in the body and is followed by the recipient; a header is message metadata that compatible mail clients can use to present an unsubscribe control. RFC 2369 defines the header, and RFC 8058 describes a one-click method. A message can include both, because they provide separate ways to express the same preference.
What to include in an unsubscribe footer
Keep the content short and recognizable. A recipient should understand who sent the email, what subscription they are changing, and how to stop messages. A preference-center link can sit beside the direct opt-out when you support multiple email categories.
A useful checklist:
- A clear link such as “Unsubscribe from marketing emails.”
- A separate “Manage email preferences” link when recipients can change individual categories.
- A recognizable sender or organization name.
- Concise wording that explains the email is part of a subscription.
For example:
You’re receiving product updates from Acme.
[Unsubscribe from all marketing emails] · [Manage email preferences]
The FTC guidance allows a menu of commercial email types, but that menu must also offer a way to stop all commercial messages from the sender. The opt-out method cannot require a fee or information beyond the recipient’s email address, and it must remain able to process requests for at least 30 days after the message is sent. These specifics shape the flow behind the words: a preference center should not become a barrier to opting out.
How to add an unsubscribe link to an email
Build the opt-out flow around a recipient-specific link. The token should identify the recipient and subscription without exposing the person’s email address in the URL. When the endpoint receives a request, update the appropriate preference or suppression record and confirm the result clearly.
A basic template pattern might look like this:
<a href="https://example.com/unsubscribe?token={{unsubscribe_token}}">
Unsubscribe from marketing emails
</a>
Include the equivalent route in the plain-text part of a multipart message:
Unsubscribe from marketing emails:
https://example.com/unsubscribe?token={{unsubscribe_token}}
Then test the full path, not just the template preview:
- Send a test message to an address with a known subscription state.
- Follow the HTML link and confirm the expected category changes.
- Repeat using the plain-text version.
- Send a subsequent campaign test and confirm the suppressed address is excluded.
- Test the preference-center option and the all-marketing opt-out separately.
For commercial email, CAN-SPAM says senders must honor opt-out requests within 10 business days. Gmail recommends honoring unsubscribe requests within 48 hours (Gmail subscription guidelines). We recommend applying the suppression as soon as the request arrives, so scheduled campaigns do not send to someone who has already opted out.
Unsubscribe link vs. List-Unsubscribe header
The body link and the header do different jobs. The visible link is part of the rendered email; the header gives a compatible mail client structured metadata to offer an unsubscribe action in its interface. A one-click header does not remove the need for a clear visible link in the message body for Gmail senders subject to its bulk-sender rules.
RFC 8058’s one-click pattern includes both headers. For example, a message might contain:
List-Unsubscribe: <https://example.com/unsubscribe/opaque-token>, <mailto:unsubscribe@example.com?subject=unsubscribe>
List-Unsubscribe-Post: List-Unsubscribe=One-Click
The HTTPS URI must identify enough information about the recipient and list to process the request automatically. The mailto option is a fallback permitted by RFC 2369; the one-click HTTPS flow uses the POST method. RFC 8058 also requires a valid DKIM signature that covers both headers, with both included in the DKIM-Signature h= tag.
When the recipient chooses the mail client’s one-click action, the client sends an HTTPS POST with List-Unsubscribe=One-Click in the request body. That endpoint must process the request without cookies or HTTP authorization and must not return an HTTPS redirect. This is why the header endpoint should be built specifically for one-click processing rather than pointed at a normal web page that expects a browser session.
| Route | Where it appears | How the recipient uses it |
|---|---|---|
| Visible opt-out link | Email body, in HTML and plain text | Opens the sender’s opt-out or preference flow |
List-Unsubscribe | Message header | Lets compatible mail clients offer an unsubscribe control |
| RFC 8058 one-click | List-Unsubscribe plus List-Unsubscribe-Post headers | Sends an HTTPS POST to process the opt-out |
Marketing emails vs. transactional emails
Treat a campaign subscription separately from the delivery of account-critical messages. Promotional campaigns need an opt-out route. A receipt, password reset, security alert, or reservation confirmation is tied to a transaction or account event; Gmail excludes transactional messages such as password resets and reservation confirmations from its one-click unsubscribe requirement (Gmail sender guidelines). An opt-out from marketing should not automatically suppress an essential account message.
Mixed-content messages need more care. CAN-SPAM classification considers how a recipient would understand the subject line and whether transactional content appears mainly at the beginning. A receipt that leads with a discount or product promotion may read like a commercial message. When the main purpose is promotional, send it as a campaign with the relevant opt-out handling instead of hiding marketing content inside a transactional template.
At Volanea, we keep transactional email, campaigns, and automations on one API, but those message types still need distinct sending logic. Our contact graph includes one-click unsubscribe, which helps teams connect campaign preferences to the recipient record without treating account delivery as a marketing subscription.
Can you remove or customize an unsubscribe footer?
You can customize the wording, placement, or design when your sending platform exposes those controls. Some platforms append a link outside the editable template, which explains why a preview or editor can omit it while the delivered email contains it. Inspect the final message before adding another link or removing a default one.
Whether the link is inserted by a template, a shared layout, or a sending service, removing the visible control does not remove the need for an appropriate working opt-out in commercial email. Replace a default route only after the replacement works in both HTML and plain text and updates the same subscription state. Check the delivered message in the systems your team actually uses—whether SMTP2GO, Braze, Raiser's Edge, NetSuite, or an in-house sender—because the final message, not the editor view, determines what recipients receive.
Best practices for reliable unsubscribe handling
A few implementation details prevent common frustrations and make opt-outs easier to maintain:
- Keep the link visible on mobile. Use readable text and enough spacing that a recipient can find it without zooming.
- Use accessible, specific link text. “Unsubscribe from product updates” communicates more than “click here,” including when read by a screen reader.
- Keep HTML and plain text in sync. Both message parts should offer a working way to opt out and reach preferences.
- Update the right subscription. A category choice should change that category, while a separate control can stop all commercial email.
- Apply suppression promptly. Check recipient state when a campaign is queued and again before delivery, so an opt-out does not remain in a stale batch.
- Test both routes. Click the body link, then inspect the headers and test the RFC 8058 POST against a test recipient.
At Volanea, we expose send records and delivery, open, click, bounce, and unsubscribe statistics, along with event logs. That gives teams a way to review whether an opt-out was recorded and compare it with subsequent campaign activity. Our SMTP relay supports transactional sending; for campaigns and automations, keep subscription state connected to the contact record and verify the final message behavior. Every feature ships on every plan; plans differ by monthly volume and domain count.
Common unsubscribe footer problems
A missing link can result from checking only a template preview instead of the delivered email. Inspect the final HTML and plain-text parts, then test a real link from a controlled recipient record. If the link is present but broken, check token generation, endpoint routing, and whether the token still maps to the intended recipient and subscription.
A generic URL can be just as frustrating as a broken one. Sending recipients to a homepage or asking them to log in adds steps; a direct, recipient-specific route should reach the action. CAN-SPAM limits the information and steps required to opt out, so avoid forms that demand extra personal details or a lengthy confirmation process.
Duplicate links usually point to multiple layers adding the same control—for example, a template and an automatically appended footer. Review the delivered message and locate which layer owns each link before changing either. Unexpected form fields are another sign that the opt-out route is doing too much; a direct unsubscribe action should not require completing a profile.
Finally, a global opt-out can frustrate recipients who only want to stop one category. Keep distinct preferences where useful, but make the all-commercial-email option easy to find. Whichever choice a person makes, campaign suppression should use the updated state before the next send.
FAQ
What happens if someone unsubscribes after a campaign is scheduled?
The recipient should be excluded when the campaign is actually sent, not merely when the schedule is created. Check the current suppression or preference record at send time, so a request received after scheduling still prevents a later delivery. For a queued campaign, test that the final recipient selection respects a newly recorded opt-out.
Should opening an unsubscribe link immediately change a subscription?
For a normal body link, avoid making an unsubscribe happen on a simple GET request: mail security scanners may fetch links before a person does. Show a clear confirmation action on the page, then apply the choice when the person submits it. RFC 8058 one-click requests are different: they use an explicit HTTPS POST from the mail client after the recipient chooses its unsubscribe control.
How do I prevent someone from opting out of the wrong list?
Bind each recipient-specific token to both the recipient and the relevant subscription or list, then validate those values at the endpoint. Show the category being changed on a preference page and provide a distinct all-marketing option. Test with an address subscribed to several categories to confirm that changing one preference leaves the others intact.
We built Volanea to bring transactional email, campaigns, and automations together while keeping contact storage unlimited. Start free with 1,000 emails a month.