TL;DR. There are five reasons a link opens a web page instead of the app. The tap happened inside another app's browser, the destination has no proper app link configured, the app is not installed, the URL is not the canonical one the app recognises, or a redirect chain broke the handoff. A deeplink handles all five, because it detects the context and picks the route that works on that device.

If you have tried three things and none of them worked, it is probably because you were fixing the wrong one of these.

Reason one, the tap came from inside another app

This is the most common cause by a wide margin. Instagram, TikTok, Facebook, X, LinkedIn and Snapchat all open links in their own embedded browser. The operating system never gets to evaluate whether an app should handle the link, so it renders as a web page.

You can confirm this in seconds. Open the same link in Safari or Chrome. If it opens the app there and not from Instagram, the webview is your problem.

Reason two, the destination has no app link set up

Universal Links on iOS and App Links on Android only work if the destination app has declared the domain and hosted a verification file. Many sites never did this. If the destination has not set it up, no link you publish will open an app, because there is nothing to open.

Reason three, the app is not installed

Obvious but worth stating, because the failure looks identical from the outside. A link that relies on a URI scheme will do nothing at all here rather than falling back gracefully, which is why publishing raw schemes to a public audience is risky.

Reason four, the URL is not the canonical one

Apps recognise specific URL patterns. A shortened, redirected or parameter heavy version of the same destination may not match the pattern the app registered, so the handoff never triggers even though the page loads fine.

Reason five, a redirect chain broke the handoff

Every hop in a redirect chain is a chance for the app handoff to be lost. Links that pass through several trackers before arriving often end up on the web version for this reason alone.

The one fix that covers all five

1. Take the canonical destination URL, the clean one, not a chain of redirects.

2. Paste it into the deeplink generator on OpenUp.

3. Publish the generated link instead of the original.

4. Test it from inside the actual social app on a real phone.

5. Check the fallback by testing on a device without the destination app installed.

The generated link detects the in app browser, attempts the native app using whichever mechanism fits the device, and falls back to the web so nobody hits a dead end.

Cause and fix

The bottom line

Most people troubleshooting this are trying to fix their phone, their settings or their destination page. The problem is almost always the context of the tap, and the only piece you control is the link you publish.

Frequently asked questions

Why does it work for me but not for my followers? You probably tested in your browser, they tapped from inside a social app.

Can I fix this on the destination site? Only if you own it, by configuring Universal Links and App Links.

What if the destination has no app at all? Then the web is the correct outcome and the fallback handles it.

Does shortening a link break deep linking? It can, if the redirect chain loses the handoff. A deeplink service handles the redirect itself.

Is the fix free? Yes.

Last updated: September 2026. Written by the OpenUp.to team.

Internal links deeplink generator, in app browser problem, short link