There are many reasons that mailbox providers could flag your email as spam.
Here are the most common reasons we see and how to fix them!
Sending From a Public Domain
If you send messages from a free domain like gmail.com, yahoo.com, etc., your messages will likely go to the spam folder. Make sure to send mail from a domain you own that matches your branding.
If the domain you send mail to has a DMARC policy, but you have yet to verify the domain with your SMTP provider, your messages will likely go to spam. Check with your SMTP provider for instructions on how to ensure your HighLevel messages pass DMARC.
List Health & List Collection
If all of the technical pieces above are covered, list health and list collection are the next most important factors to determine deliverability. Be sure that:
- Everyone on your list gave direct consent to receive email marketing from you
- Your cold subscribers are cleaned from your list regularly
- Your forms are secured with double opt-in
To learn more about why messages go to the inbox or spam folder, check out our Introduction To Email Deliverability post.
Sending Internal Mail
Are you sending messages to the same domain from which the message is coming? For example, sending from email@example.com to firstname.lastname@example.org. If so, it’s common for these internal messages to go to spam. This is because your mailbox sees that it’s receiving a message from itself, but it knows that it didn’t send the message. This makes your mailbox think it’s being spoofed and sends the message to spam.
If you’re sending internal mail to test your messages, we recommend using a free email like gmail.com. If you need to send mail internally outside of testing, you’ll want to have the person who manages mail for your domain whitelist the IP address of your SMTP provider.