First and foremost, message content always plays a role in where your messages wind up. Message content is complex and includes things like copy, URLs, disclaimer text, from addresses, etc. We recommend that you set up a small list of email addresses that you can check with each of the major ISPs and test all of your emails prior to sending. Gmail provides some good insight… For example, you may see a message in spam with the following:<\/p>\n\n\n\n
![\"\"](\"https:\/\/heathertankersley.com\/emaildelivered\/wp-content\/uploads\/2022\/03\/Why-is-this-message-spam1.png\")
<\/figure><\/div>\n\n\n\n(This indicates that is’ message content almost entirely).<\/p>\n\n\n\n
2. Sending domain<\/strong><\/p>\n\n\n\n If you are getting a high number of complaint, or are sending messages that ISPs generally suspect as spam, you may wind up with problems related to your domain. For example, if you look in a Gmail spam folder, you may see something like:<\/p>\n\n\n\n In this case, your sending domain is most likely ruined. You’ve either had a lot of complaints or you may have sent repeated content that appears spammy, for example.<\/p>\n\n\n\n 3. Domain seasoning<\/strong><\/p>\n\n\n\n This generally only applies to you if you are using a new domain. However, if you start your sending with a brand new domain, and have content\/complaint problems early on, this could roll into a long term problem with your domain.<\/p>\n\n\n\n 4. Domain Privacy<\/strong><\/p>\n\n\n\n We have seen evidence as of late that having domain privacy on for your sending domain does cause some problems with deliverability and inbox placement. In other words, services like “privacy guard” should be avoided when it comes to the domain that is being used in your headers\/return path.<\/p>\n\n\n\n![\"\"](\"https:\/\/heathertankersley.com\/emaildelivered\/wp-content\/uploads\/2022\/03\/Why-is-this-message-spam.png\")
<\/figure><\/div>\n\n\n\n