Email list hygiene: a repeatable cleanup process
List hygiene is the process of keeping contact data usable and its sending rules intact. Verification is one step. Duplicates, stale records, consent and suppression history need separate handling so a technically valid address does not become an excuse to send the wrong message.
Open the relevant free tool →Verification is one part of a list review
Keep an untouched source copy
Export the fields needed for review and keep a source snapshot before making changes. Include the original address, record identifier, source and relevant dates. A clean output without a record of what changed is hard to audit. Avoid copying unnecessary sensitive customer fields into a verification upload.
Clean structure before network checks
Remove accidental surrounding whitespace and identify exact duplicates under your documented rules. Preserve malformed entries in an error report instead of silently dropping them. Do not strip plus tags or apply Gmail-specific dot rules to every provider. Keep normalization and original destination fields separate when a transformation could affect identity.
Verify and segment
Run technical checks, then create separate groups for clear failures, contextual risks and unresolved results. A shared-inbox address can be appropriate for a business contact, and a catch-all domain is not equivalent to an invalid recipient. Include the check date so a later user can tell whether the evidence is current enough for the next action.
Apply suppression and consent independently
A fresh valid result should never remove a suppression flag or invent permission to contact someone. Join the verification output back to your CRM using a stable identifier where possible. Preserve unsubscribe and permanent-bounce records across reimports. If you maintain multiple tools, designate one authoritative source for those sending restrictions.
Review the outcome before sending
Compare input rows, unique addresses, checked rows and exported rows. Explain any difference. Inspect a small sample from each result category and verify that the rules did what you intended. For ongoing maintenance, schedule reviews based on data age and actual use rather than applying a fixed interval to every contact regardless of context. Keep the process small enough to repeat reliably.
Worked example
A useful cleanup report includes: input count, exact duplicates, malformed entries, checked unique addresses, status counts, suppressed records retained and output count.