A shortened link shows a "preview" screen for one of five different reasons, and only two of them are actually caused by the shortener. One is you, or whoever shared the link, triggering an opt-in preview feature. The other is the shortener flagging the destination as risky. That's the whole list of things the shortener can actually be blamed for. The other three reasons belong to someone else entirely: a social app's own outbound-link warning, the destination site's own cookie or age gate, or a branded splash the platform chose to add as a feature. If you searched "url shortener without preview" or "link shortener without preview" hoping for the name of a tool, the honest answer depends on which of these five you're actually looking at, and that's what the rest of this sorts out.
Why is Bitly showing a preview page?
This is the most searched version of the question, so it's worth answering directly before the general breakdown. There are three realistic explanations, and they aren't equally likely.
The first is a modifier someone added before sharing the link. Several shorteners, Bitly among them, have historically let a user append a symbol to the end of a short URL (a plus sign, on a bit.ly link) to see a stats or destination preview instead of being redirected straight through. If the link ends in an extra character, strip it and load the bare short link again. Worth confirming against the live link rather than trusting any single writeup, including this one, since shortener features change without much notice.
The second is a safety interstitial, and it works differently from the first. Bitly, like most link platforms, runs automated checks on the destinations behind its links and interposes a warning page on ones it has flagged, whether from abuse reports, a match against a known-bad list, or scanning of the destination page itself. The link's creator can't turn this off, because it was never their setting in the first place. It's Bitly's own judgment call about where the link leads, made to protect the reputation of its own domain.
The third is the one people misdiagnose most often: the "preview" was never Bitly's at all. It's the destination site's own cookie banner, age gate, or login wall. It shows up the instant after the redirect completes, and gets blamed on the shortener purely because of the timing. Open the destination URL directly, skipping the short link entirely, and check whether the same screen appears. If it does, the shortener was never involved.
The five things people call a preview page
Outside of Bitly specifically, the same five categories cover almost every complaint typed as "why is my link showing a preview," across any shortener. Separating them matters. Each has a different owner and a different fix, and a lot of the confusing advice floating around exists because someone answered one category for a person describing another.
| What you're seeing | What it actually is | Who controls it | What to do |
|---|---|---|---|
| A warning that the destination may be unsafe or has been reported | A safety interstitial | The shortener | Check the destination against a malware or Safe Browsing checker, then use the platform's appeal or report-a-mistake path if it's clean |
| A stats or "here's where this goes" screen after a symbol was added to the URL | An opt-in preview feature | The shortener, triggered by whoever shared the link | Remove the modifier and share the bare short link |
| A branded page with a logo and a continue button, shown on every link | A splash or interstitial the platform chose to add | The link platform, as a product decision | Check whether the account owner can turn it off, or pick a platform where it defaults off |
| A "you're leaving the app" prompt inside Instagram, TikTok, or Facebook | The social platform's own outbound-link warning | The social app | Nothing to fix on the link side. It happens to any external link tapped from inside that app |
| A cookie banner, login wall, or age check | The destination site's own consent or age gate | The destination, not the shortener | Not a link tool issue. Raise it with whoever runs the landing page |
How do I get a URL shortener without a preview?
There is no single toggle called "disable preview," because "preview" covers five mechanisms owned by four different parties. What you can actually control:
- Modifier-triggered preview: drop the modifier before sharing. Entirely in your hands, and it has nothing to do with which shortener you picked.
- Branded splash the platform adds as a feature: check whether it ships off by default or on. Some platforms show one to every visitor as a fixed product choice. Others make it optional for the account owner and default it off, which is the setting worth checking before you sign up rather than after you've already built links out on it.
- Social platform's outbound-link warning: no link tool controls this one. It happens the same way on a link from any other shortener.
- Destination's cookie or age gate: not a link tool problem at all. Raise it with whoever runs the landing page.
- Safety interstitial from a flagged destination: the fix lives somewhere else entirely, and it's worth doing properly rather than working around it.
Why did my link get flagged, and what actually fixes it?
The instinct when a warning page shows up is to blame the shortener and go hunting for one with a cleaner reputation. Sometimes that helps for a while. But the flag almost always attaches to the destination, not the short link itself, and pointing that same destination at a different shortener just carries the same problem along with it. Chasing a new tool to dodge a flag is treating the symptom, not the cause, and it rarely buys more than a few weeks before the same pattern catches up.
Two things commonly get a destination flagged that have nothing to do with anything the link's creator did: the domain had a prior owner who used it for something abusive, or an automated scanner mistook something on the page (an aggressive redirect chain, an ad network, a compromised plugin) for malicious behavior. In both cases the fix lives on the destination side. Run it through a malware or Safe Browsing checker, look for anything that resembles injected script or an unexpected redirect, and if the site is genuinely clean, most platforms have an appeal path for exactly this situation. It's slower than switching tools, but it's the only fix that actually holds, since a new shortener pointed at the same flagged destination tends to pick up the same flag once enough traffic runs through it.
Does a custom domain actually fix it?
A custom domain changes the reputation surface, and it's worth being precise about what that means rather than selling it as a cure. A shared shortener domain carries the history of every link ever created on it, most of which you had no part in. If a fraction of those links were abusive, the domain's overall reputation absorbs some of that, and an unrelated link on the same domain inherits a bit of the scrutiny along with it.
A domain you own has no such shared history. It starts closer to neutral and stays that way as long as your own usage stays clean, which is a real advantage for anyone sending meaningful volume through short links. That's also why custom domains sit behind a paid plan on most platforms, Raydar included, rather than shipping free on every account. It isn't a guarantee, though: a brand-new domain has no reputation yet, which is different from a good one, and careless use builds a bad reputation on your own domain just as fast as a shared one can hand you someone else's. Set the DNS and SSL up correctly, and use the domain only for links you're willing to stand behind. Do that and it earns a clean history instead of inheriting a stranger's. If you're sending any real volume through short links, the setup hassle is worth clearing well before the reputation payoff ever shows up, and I wouldn't wait until a flag forces the issue.
How Raydar handles this
Worth being specific, since it's the exact question a lot of people land on this page to answer. Raydar's link pages support an optional branded interstitial, called the curtain internally, and it ships off by default. Nobody visiting a Raydar link sees a page they didn't choose to show. The account owner has to turn it on themselves. Off by default is the right call here, and it's the real difference against platforms that insert a splash page as a default product decision: whoever creates the link decides whether visitors see one, not the platform.
That doesn't touch the other four categories. A Raydar link can still trigger a social platform's own outbound warning, since that's entirely the app's call, and a destination flagged by a safety scanner will still draw scrutiny regardless of which shortener sits in front of it, for the same reasons covered above. If what brought you here is a warning page rather than a branded splash, work through the destination first. That's where the actual fix lives, on Raydar or anywhere else.
For the broader safety question behind all of this, see is a URL shortener safe to use. If you're earlier in the process and want the basics on what a shortener does before worrying about preview pages, what is a URL shortener covers that.