← All posts
Deliverability

URL Shorteners in SMS Marketing: Why Links Get Blocked

Generic public link shorteners are a known risk for text filtering. Here is what the guidance says and how high-volume senders can reduce the risk.

Flowtext Team7 min read

URL shorteners in SMS marketing look harmless, but a generic public shortener is one of the more common ways to get a text flagged. Industry guidance says senders who shorten links should use a domain dedicated to them alone, not a shared public one. For teams running high-volume campaigns, especially during peak season, a filtered link means texts that never arrive and revenue that never shows up.

This post covers what the guidance says, where it is firm and where it is not, and what you can do about links in your own program.

Key takeaways

  • CTIA's messaging best practices say that if you use a URL shortener, it should have a web address and IP addresses dedicated to your exclusive use.
  • Shared public shorteners are widely reported to be rejected at 10DLC campaign review and linked to higher filtering risk.
  • CTIA's document is voluntary guidance, not a binding carrier rule, and enforcement can vary.
  • Links should clearly identify who you are and where they lead.
  • Watching delivery receipts and failures by error code helps you spot link-related filtering early.

Carriers filter text messages to protect their subscribers from spam and phishing. Links are an obvious thing to inspect, because they are how a scam text gets a recipient to a malicious page.

Free, public link shorteners are used by many senders, including bad actors. According to Twilio, a major messaging provider, US carrier policies strongly discourage shared public shorteners. Twilio ties this to spammers' frequent use of those domains, and says it raises the risk that your messages are filtered, with no recourse if they are.

So the issue is not that shortened links are inherently bad. A shared domain carries the reputation of everyone who uses it, and you cannot control that reputation.

What CTIA's guidance says

CTIA is the wireless industry trade association. Its Messaging Principles and Best Practices (published May 2023) address links directly. Section 5.3.2 says that where a URL shortener is used, senders should use one with a web address and IP address(es) dedicated to the exclusive use of the message sender.

The same section says embedded links should not conceal or obscure the sender's identity, and should not be intended to harm or deceive. Link domains, and the sites they redirect to, should unambiguously identify the website owner and include contact information such as a postal address. You can read the full document in CTIA's Messaging Principles and Best Practices (opens in a new tab).

One important caveat: CTIA describes the document as voluntary best practices. It says it does not impose or require contractual or technical implementation by stakeholders, including service providers, and that implementation methods may vary. It is not a binding carrier rule.

Can you use Bit.ly in text messages?

Many marketers ask whether they can use bit.ly in text messages. The short answer from the guidance is that you should not rely on it. A public shortener like bit.ly or tinyURL is exactly the kind of shared domain that CTIA's dedicated-shortener language and Twilio's guidance warn against.

There is also a registration angle. According to Twilio's documentation, public shorteners are rejected at 10DLC campaign review and at toll-free verification. (10DLC, or 10-digit long code, is the registration system US businesses use to send application-to-person texts over standard local numbers.) A third-party blog, MessageFlow's 10DLC URL shortener guide (opens in a new tab), reports the same: that public shorteners such as bit.ly and tinyURL are not accepted in 10DLC registration, and recommends a branded HTTPS short domain dedicated to the sender.

Two cautions apply:

  • The sources do not agree on the exact rejection code, and we have not verified which is current, so avoid relying on a specific code.
  • Registration rejections are described more clearly in the sources than live-traffic filtering, so how any given carrier treats a public shortener in live messages is not fully documented here.

The common recommendation is a branded short domain: a short link on a domain you control, such as a shortened version of your company name. Because the domain is yours alone, it does not inherit the reputation of strangers' traffic, and it can clearly identify you as the owner, which fits the CTIA language above.

Twilio says branded custom-domain short links meet carrier expectations. But Twilio's own documentation also notes that a custom domain that behaves like a redirect service can still be rejected at campaign review. In other words, branded short links are generally the safer path, not a guarantee.

For high-volume senders, some practical points follow from the guidance:

  • Use a domain dedicated to your own messaging, not a shared one.
  • Make the destination page clearly identify your business, with contact information.
  • Use HTTPS.
  • Don't use the domain as a general-purpose redirect for other people's links.

Also note that the right approach depends on where you send. Twilio says other countries may not forbid public shorteners outright, while US guidance is stricter.

What we don't know yet

Several points are still unresolved, and it's worth being honest about them:

  • Carriers' own policy text was not reviewed for this post, so claims about how specific carriers filter links rest on provider guidance, not on the carriers' published rules.
  • It is not established that carriers filter based on link-domain reputation or on how consistently a link is used across a campaign. No source we relied on states this.
  • Whether a branded-domain setup carries its own registration or warm-up requirements is not verified.

Treat everything above as guidance and risk, not as a universal or guaranteed rule.

What this means for high-volume SMS senders

At scale, a link problem is rarely a single failed message. If a link or domain is the trigger, filtering can affect a large share of a campaign at once, often with little visible warning. Carriers do not always report that a message was filtered, so a blocked text can look like silence, not an error.

When filtering is reported, it can surface as a message-filtered error. Twilio, for example, uses error code 30007 for "Message filtered." That is one provider's code, and a carrier-level error code reference was not part of this research, so check your own provider's documentation for the equivalent codes.

This is where measurement matters. Delivery receipts and failure analysis grouped by error code let you see whether failures cluster around a specific link, domain, or campaign, rather than guessing. Flowtext's features include carrier delivery receipts, failure analysis grouped by carrier error code, and 24/7 number-health monitoring, which together help senders spot patterns like this. Flowtext reports a 98.9% average delivery rate and a 0.4% spam-block rate across its platform.

What to do now

  1. Audit your links. List every domain used in your live texts, including those in automated sequences and templates.
  2. Remove public shorteners. Replace bit.ly, tinyURL, and similar shared domains with a domain dedicated to you.
  3. Set up a branded short domain. Use HTTPS, and make sure it belongs to your business alone.
  4. Check the destination pages. Confirm each one clearly identifies your business and includes contact information, such as a postal address.
  5. Confirm your registration. Make sure the sample messages in your 10DLC campaign registration use the same kind of links you actually send.
  6. Track results by link. Tag links per campaign so you can compare delivery and failures when something changes.
  7. Monitor failures by error code. Look for spikes in filtered messages after any change to links or domains.
  8. Test before peak season. Send a small batch with a new link setup and review delivery results before a large send.

Frequently asked questions

Can you use bit.ly in text messages?

You can technically include one, but it is not advisable for business texting in the US. CTIA's best practices say a shortener should be dedicated to the sender alone, and Twilio reports that public shorteners are rejected at 10DLC campaign review. A branded domain is the usual alternative.

Not all links are blocked, but links can contribute to filtering. Shared public shorteners are a known risk because spammers use them often. Carriers do not always report filtering, so blocked messages can go unnoticed without delivery monitoring.

No. CTIA describes its Messaging Principles and Best Practices as voluntary and says it does not impose contractual or technical requirements on providers. However, messaging providers and carriers may apply stricter rules in practice, such as at campaign registration, so following the guidance is the safer course.

Next steps

Links are one of the easier deliverability factors to fix, and one of the more costly to ignore. If you want to see how delivery receipts and failure analysis can show where your texts are being filtered, explore Flowtext's features, or review how we approach compliance.

This post is general information, not legal advice. Consult counsel about your own messaging programs.

Tags

  • SMS deliverability
  • URL shorteners
  • carrier filtering
  • 10DLC
  • SMS compliance
← Back to all posts

Ready to run the playbook?

Sign up and onboarding gets you from registration to your first send on Flowtext.