Sending URLs in Text Messages

Including URLs (or links) in your text messages is a great way to share information with your recipients. Unfortunately, many spammers use links to run scams. Major carriers have identified patterns used by spammers to run scams and have introduced filters to block those messages. This article covers best practices when using links in your text messages. 

Best Practices

  • Make sure you include a valid URL that links to a real web page or document (carrier spam filters will detect invalid URLs and block messages containing them).
  • Avoid links that redirect to a different URL than the one included in your message (this can also trigger spam filters).
  • Avoid using generic URL shorteners such as and tinyurl. The carriers have increased blocking of messages containing these types of URLs because they are heavily used by spammers for phishing and sending fraudulent links.
  • If you want to shorten your URL, many of those same services allow you to create a custom (or branded) link that is unique to your organization. These custom shortened URLs are allowed and will not cause message delivery issues. We at Text-em-All do not create custom or branded links as part of our service. 

Invalid Content Result

This result means that the carriers have blocked your message for containing a non-compliant URL.

If you receive the " Invalid Content" broadcast result and are sending a Google Drive link, one potential workaround is listed below. Please note that this workaround does not always work! Carriers are increasingly blocking even regular Google Drive links. 

The workaround: 

Try shortening the link to remove whatever comes after the word 'view.' Typically, this will mean removing "?usp=share_link" from the URL. 

For example,

would then become

As long as you remove the end of a Google Drive link like that so that it ends with the word "view," it will not redirect and will stay as is.

Blocked URLs

These URLs are currently being blocked due to abuse by scammers.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us