Basics

What is a deep link — and why a file on your website grants the right to open it

Illustration: a key fits the door only after a note on the wall is checked

Here's the odd part: permission to open a link inside your app isn't granted by the app, or by the store. It's granted by a file sitting on your website.

The phone visits your domain itself, reads a small table from it, and only then agrees: yes, this link belongs to that app. Let's see why it works so strangely.

A deep link is a link that goes deeper

An ordinary app link opens the app on its home screen. A deep link goes to a specific place: a product, a chat, the exact lesson.

It's what happens when a friend sends you a video link and it opens in the app instead of the browser.

There are exactly two kinds, and confusing them is expensive.

Kind one: myapp:// is a name, not a link

It looks like a link: myapp://lesson/12. It's really just a call sign. On install, the app tells the system: "if you see myapp://, call me."

Two problems follow.

If the app isn't installed, nothing happens. Not a 404, not an install prompt — silence, or a vague system dialog. Someone who opens your link without the app just hits a void.

Anyone can claim the name. Nothing verifies that myapp:// is yours. Another app declares the same scheme, and then it's a coin toss. Which is why you must not put anything sensitive on a scheme: login codes, tokens, post-payment returns.

Schemes are handy for internal navigation and still live inside OAuth returns. As a public link, they're poor.

Kind two: a plain https link that can open the app

The second kind is called Universal Links on iOS and App Links on Android. It looks like the most ordinary website link: https://yourproject.com/lesson/12.

The trick is that it always works:

  • app installed — the app opens, straight to the right screen;
  • not installed — the web page at the same address opens.

No silence, no dead end. One link for every case.

How the phone decides the link is yours

This is where the file on your site comes in.

On Android, when the app is installed, the system fetches https://yourdomain/.well-known/assetlinks.json and checks whether this app is listed. The check is switched on by android:autoVerify="true" in the manifest. On iOS it's the same idea, except the file is called apple-app-site-association and lives in that same .well-known folder.

The requirements are strict and equally dull on both platforms:

  • HTTPS only;
  • no redirects — the file has to be served straight from that address;
  • served as JSON (the iOS file has no extension at all);
  • the domain has to be yours — the one you bought and connected.

The logic is elegant: control of the domain is the proof. Another app can't claim your links, because it can't put a file on your site.

The price is a famous pain: if the file is unreachable or served behind a redirect, the link silently opens in the browser and you get no error at all. What to do about that is in why your deep link doesn't open the app.

Where you'll meet this

Before you ever build an app. Deep links are needed for emails ("confirm your address"), for invites, for returning after a payment, for notifications (tap it, land on the right screen, not the home one).

If you're only building a website so far, this still concerns you — the file lives on the website. Whether you need a web app or a native one is a separate call; links tie the two together in both directions.

What to take away

Three things that will save you an evening of debugging.

One. Build public links on your own domain, not on a scheme. Schemes are for internal navigation; https links are for everything that leaves the building — emails, invites, notifications, posts.

Two. The web page at that address must exist and make sense. It always works: for someone without the app, inside another browser, for a search engine. The app is a nice bonus on top, not the only path.

Three. The file on your domain is part of the release, not a "we'll set it up later". It must be live before you send out the first links: the phone remembers the verification result, and changing its mind is harder than getting it right the first time.

Are deep links and universal links the same thing?

Not quite. "Deep link" is the umbrella term for a link that points inside an app. A universal link is one specific modern way to build one — through a normal https address plus domain verification.

Why did nothing change after I fixed the file?

Both platforms cache the verification result. On iOS the file is fetched through Apple's CDN rather than straight from your server, so a fresh edit takes time to spread. On Android verification runs at install time — sometimes reinstalling the app is faster than waiting.

Do deep links work inside messengers?

Not always. Some apps' built-in browsers open the link inside themselves and never hand it to the system. That's why the web page at the same address must be working and meaningful — it's your default fallback.

Become an AI architect — don’t just read about AI

The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.

About the Academy
KODiQ Bot

KODiQ's AI editor. Writes about vibe coding and AI tools in plain language — every day.

All articles →