X (Twitter) link not working? Why links won't open from X — and the fix

On this page

why links break in X
what breaks in any in-app browser, X included
what linkboo does
who this hits hardest
other platforms

Someone scrolls X, reads your post, and taps the link you put in it — or the one in your bio. They wanted the thing on the other side: the newsletter, the ticket, the login, the checkout. Instead the page opens inside X's own in-app browser, a stripped-down webview that doesn't know who they are. The sign-in button doesn't recognize them. The "subscribe" form asks for an email it should already have. The checkout drops the saved card. So they back out — and to you it just looks like a link nobody clicked through.

That isn't a content problem and it isn't a broken URL. It's where the tap happened.

Fix it with linkboo →

why links break in X

On mobile, X opens links in its own in-app browser by default rather than handing them off to Safari or Chrome. That webview can render a page, but it carries its own empty cookie jar — none of the sessions from the viewer's real browser come with it. So the logged-out webview breaks auth and checkout the same way every in-app browser does: the page loads, but the part that depends on "we already know this person" doesn't.

The result is a viewer who has an account — on the newsletter, the store, the ticketing platform, the app you're sending them to — landing on a page that treats them like a stranger. They get a login wall instead of a subscribe button, a "create account" form instead of one-tap checkout, a magic-link email that opens in the wrong browser and dead-ends. The intent was there. The session wasn't.

We named this problem the vanishing visitor and wrote the full mechanism explainer there. The short version: the cookie that proves who your visitor is lives in their real browser, and X's in-app browser can't reach it. Until the link escapes that webview, the conversion can't happen.

what breaks in any in-app browser, X included

These are the destination-specific failures we see most often. The mechanism is the same in every case — a logged-out webview — but each one breaks in its own way:

Magic-link logins — the login email opens in a different browser than the one that requested it, so the link never completes the session
OAuth redirects — "continue with Google/Apple" bounces through a redirect chain the webview can't finish
Passkeys — the device's saved passkey isn't available inside the webview, so the fastest login path silently disappears
beehiiv subscribes — the subscribe confirmation and double opt-in break when the click never leaves the in-app browser
Eventbrite checkout — the ticket purchase flow loses the cart and the saved payment method at the handoff
SoundCloud links — the track opens on the cookieless web player instead of the app, logged out
Vinted links — the listing opens in the webview without the buyer's session, so favoriting and buying both stall

If your destination isn't listed, the cause is almost certainly the same. The full fix index is here.

what linkboo does

linkboo replaces the raw URL in your X post or bio with a link-in-bio page (or a direct-route link — your choice) that has the in-app browser escape flow built into every outbound click.

It detects the webview and escapes it first — when a viewer taps your linkboo link from inside X, linkboo bounces the destination out to their real browser (Safari on iOS, Chrome on Android) before the destination page loads
The viewer's session comes with them — they land already logged in, so the subscribe button, the saved card, and the passkey are all there
No friction prompt — the viewer never has to know what "open in browser" means or tap a menu; the escape happens automatically
Graceful fallback — if the destination has an app installed, the link opens it; if not, it lands in the real browser, not the cookieless webview

linkboo is also a full link-in-bio page — multiple links, themes, profile photo, the things you'd expect from a Linktree or Beacons alternative. The escape flow is the wedge.

who this hits hardest

Anyone whose conversion depends on the viewer being recognized loses the most here: newsletter writers, ticket sellers, paid-membership creators, resellers, and anyone routing logins or checkout from social. If X is a meaningful traffic source for you, the X-specific breakdown — and the persona-level math — lives at linkboo for X creators.

other platforms

Same in-app browser, same logged-out webview, different app. If your traffic comes from more than one place, these break the identical way:

If you're weighing the broader link-in-bio category, linkboo vs Linktree is the closest mainstream comparison — and unlike a plain link-in-bio page, the escape flow is what actually fixes this.

The person who tapped your link wanted what was on the other side. Don't let X's in-app browser be the reason they didn't get there.