Email: From Hotmale.com to Honeypots
4. Help Customers
Look at the text box on your sign-up page. Is it long enough? If your customers can't see their entire email addresses when they're typing, they can't tell if they've made a typo. Help them self-proof so they make fewer mistakes. At FreshAddress, we frequently see legitimate, deliverable email addresses that are over 50 characters long—remember that when you're designing your sign-up page.
Make sure the text in the entry box is legible. The font should be large enough to read easily and the font color should stand out.
Look at the error message your site generates. Does it help customers understand what they've done wrong so they can fix the problem(s)?
Some sites use a double-entry process: "Enter Your Email Address," then "Verify Your Email Address." You want to encourage people to type carefully, not force them to type twice. Many people simply cut and paste the faulty email addresses from one box to the other, so double-entry registration rarely solves the problem.
The best method of self-proofing is a confirmation page or a pop-up. Show what they typed again and they will probably notice typos or mistakes and go back and fix them.
5. Reward Accuracy
Tell your subscribers that if they enter their email addresses, they'll get an email back from you with a $5 off coupon or an offer of 10 percent off their next order. This encourages users to accurately enter their primary email addresses, not ones they rarely check.
6. Use Back-end Technology
Real-time email hygiene technology can scrutinize email registrations, enforce standard request for comments (RFC) codes, block problematic addresses, and catch and correct the millions of inadvertent email address entry errors people make every day.
There are official standards of what an email address must structurally contain. It has to have an @ sign and a period. It cannot have commas, quotation marks or spaces. Most sites check that each email address has an @ sign, a period and a couple other basics. Think about how you can go beyond the rules, checking beyond RFC standards, and start using technology to notice more obscure—yet still common—types of errors. These include: