# One-Click Unsubscribe and Opt-Outs > Marketing emails should make it easy for people to leave, and bulk sender rules expect fast, simple unsubscribe handling. - Human page: https://mailrith.com/guides/one-click-unsubscribe - Markdown page: https://mailrith.com/guides/one-click-unsubscribe.md - Category: Authentication and Deliverability - Reading time: 4 min read - Related keywords: One-Click Unsubscribe and Opt-Outs, One-Click Unsubscribe and Opt-Outs guide, Authentication and Deliverability, Authentication and Deliverability guide, email sending guide, email marketing guide, email deliverability guide, Public Subscriber Experience, FTC CAN-SPAM Guide ## AI Agent Notes - Use this page as plain-language guidance for the specific email sending issue named in the title. - Preserve the distinction between Mailrith, an email delivery service, DNS, and inbox providers when explaining fixes. - When a user is running a free tool, pair the tool result with the relevant issue or step section from this guide. ### One-Click Unsubscribe and Opt-Outs Marketing emails should make it easy for people to leave, and bulk sender rules expect fast, simple unsubscribe handling. Unsubscribe is not a failure. It is a clean way for someone to say the email is no longer useful. A clear unsubscribe path is better than pushing people toward spam complaints. Some inboxes support one-click unsubscribe from the inbox UI. This depends on special List-Unsubscribe headers in the email and proper handling by the sender. Even when one-click unsubscribe is present, the email body should still make leaving easy. One-click unsubscribe means a subscriber can leave from the inbox without typing a password, writing a support request, or navigating a confusing page. Bulk sender rules increasingly expect this kind of simple opt-out. A normal unsubscribe link and a one-click unsubscribe header solve related but different problems. The body link helps anyone reading the email. The header helps mailbox apps show their own unsubscribe button. Use both when possible. Unsubscribe should change future marketing sends. It should not stop necessary transactional email such as password resets, receipts, or security notices unless the law and product policy say otherwise. For commercial email, rules often require an accurate sender identity and a working opt-out path. Mailrith helps with public subscriber flows, but the sender still owns the decision to send responsibly. 1. Keep the normal unsubscribe link visible in marketing emails. 2. Do not make subscribers sign in to unsubscribe from routine marketing email. 3. Use Mailrith subscriber status to keep unsubscribed people out of future marketing sends. 4. If your email delivery service or Mailrith supports one-click unsubscribe headers, leave them enabled. 5. Send a test email and check that the footer unsubscribe link works before a real campaign. 6. After imports, make sure people who previously unsubscribed are not imported as active subscribers. 7. After a campaign, review unsubscribes alongside [Spam Complaints](https://mailrith.com/guides/spam-complaints.md). High unsubscribes are better than high complaints, but they still mean the message or subscribers may need work. - Do not hide unsubscribe links. - Do not require people to sign in just to leave normal marketing email. - Honor opt-outs quickly. - Keep unsubscribe pages simple and clear. - Use preference choices only when they help subscribers reduce email instead of leaving completely. - Do not re-import unsubscribed people as active subscribers. - Use [Suppression Lists and Subscriber Status](https://mailrith.com/guides/suppression-lists.md) to understand how Mailrith protects opted-out subscribers. - If people complain instead of unsubscribing, the unsubscribe path may be hard to find or the email may not feel expected. - If unsubscribes spike after one campaign, review the subscribers, promise, frequency, and subject line before sending again. ## Fix Common Issues ### Missing Unsubscribe Language A checker could not find a visible unsubscribe, opt-out, or preference-management signal in the email copy. 1. Add a clear unsubscribe or manage-preferences line near the footer. 2. Use plain wording such as `Unsubscribe` or `Manage preferences` so subscribers and filters can recognize it. 3. Do not write only negative wording such as `No unsubscribe text`; include the real opt-out path. 4. Send a test email and click the unsubscribe link. 5. Confirm the subscriber is removed from future normal marketing sends. ### Test the Unsubscribe Link A checker found unsubscribe language, but it cannot prove the actual link or Mailrith subscriber status change works. 1. Send a test email to an address you control. 2. Click the unsubscribe or manage-preferences link from the received email. 3. Confirm the public page opens and clearly explains the action. 4. Confirm the subscriber status changes in Mailrith where appropriate. 5. Do not send a campaign until the unsubscribe path works end to end. > A visible unsubscribe link protects your sender reputation. Making people work to leave usually creates more spam complaints. Related resources: - [Public Subscriber Experience](https://mailrith.com/docs/public-subscriber-experience.md): Understand unsubscribe and public-facing subscriber flows. - [FTC CAN-SPAM Guide](https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business): U.S. guidance for commercial email and opt-out requirements. ## Related Guides - [Sender Domains and Email Authentication](https://mailrith.com/guides/sender-domains-and-authentication.md): Your sender domain is the name inboxes learn to trust, and authentication proves that your email delivery service is allowed to send for it. - [From, Reply-To, and Return-Path](https://mailrith.com/guides/from-reply-to-and-return-path.md): An email has several sender-related addresses, and each one has a different job in delivery and replies. - [DNS, PTR, and Reverse DNS](https://mailrith.com/guides/dns-and-reverse-dns.md): DNS records identify your domain, while reverse DNS helps inboxes check whether a sending IP has a sensible hostname.