Talk to a person. We reply within one working day.

SEO and AI search
Web
AI
Resources
WorkAboutStart a project

App development · 17 Nov 2026 · 6 min read

Deep links and universal links explained for app owners

A deep link takes a person to a specific screen, not just to the front door. This guide explains how the pieces fit and where they usually fail.

The short answer

A deep link is a link that opens a specific screen inside an app. Universal links on iOS and app links on Android use ordinary web addresses: if the app is installed and the domain is verified, the app opens, and if not, the website loads. They fail mostly through setup errors on the domain, in-app browsers and routes the app no longer handles.

A deep link points to a place inside the app

A deep link is a link that opens a particular screen in an app, such as one product, one booking or one article, rather than just the app's start screen. Think of the difference between telling someone the address of a building and telling them the room number.

They matter wherever someone leaves another place to enter your app: an email, a text message, a QR code on a poster, a social post, a web page or a notification. Without deep links, each of those drops the user at the start and leaves them to search. With them, the journey continues where the message promised.

The main kinds of mobile link

There are a few families of link, and the names are used loosely, so it helps to separate them.

KindWhat it looks likeBehaviour
Custom scheme linkAn address starting with the app's own name instead of httpsOpens the app if installed. Nothing sensible happens if it is not, and any app can claim the same scheme
Universal link (iOS)A normal https web addressOpens the app if installed and verified, otherwise loads the page in the browser
App link (Android)A normal https web addressThe same idea on Android, using Android's own verification
Deferred deep linkA link that survives an installAfter the user installs from the store, the app opens on the intended screen

Universal links and Android app links are generally preferred over custom schemes because they fall back to a working web page and are tied to a domain you own. Deferred deep links usually need extra support from your developer or a third-party service, and platform rules on what can be passed across an install change, so check the current documentation.

How a link opens the app or the website

The route is simple to describe. The user taps a normal web address. The operating system checks whether an installed app has claimed that domain, and whether the claim is verified. If yes, the app opens and receives the full address. If not, the browser loads the page.

The verification step is a small file that your website serves from a standard location on your own domain. On iOS it is called apple-app-site-association, and on Android it is called assetlinks.json, and both live under the well-known folder of the site. The file lists which apps may handle which paths. The app also declares the domain in its own configuration, so the claim is made from both ends and cannot be forged by someone else's app.

This means a deep link is partly a website job. Whoever controls your domain, redirects and hosting needs to be in the conversation from the start, not after the app is built.

What the app does when it opens

Opening the app is only half of it. The app must read the address, decide which screen it means and show it, even if the user is not signed in, the app was closed or the screen is several levels deep. This is called routing, and it needs planning.

Decide what happens in awkward cases. If the link is for a private order and the user is logged out, send them through sign-in and then on to the order. If the item no longer exists, show a clear message and a way forward, not a blank screen. If the link comes from an older app version that cannot handle the route, fall back to the home screen with a note.

Use one clear address structure shared by the website and the app. When both use the same paths, one link works everywhere, and your analytics can compare the two fairly.

What breaks deep links

Most failures fall into a short list, which makes the first debugging pass easy.

  • The verification file is missing, in the wrong place, served with the wrong content type or hidden behind a redirect or a login.
  • The app configuration names a different domain or path from the one used in the link.
  • The link is wrapped by an email or ad tracking service, so the address the phone sees is not the one you verified. Tracking domains need their own set-up.
  • The link is opened inside another app's built-in browser, which may not hand it to the operating system.
  • The user once chose to open the link in the browser, and the system remembers that choice. Both platforms let users change this per app in settings.
  • A site redesign changed paths or added redirects, and the app no longer understands the new address.
  • The app version on the phone is old, so it does not contain the route.
  • Typing a web address directly into a browser's address bar often loads the website instead of opening the app, which is normal behaviour and not a fault.

Privacy and safety in links

Treat everything in a link as untrusted input. Anyone can write a link, so the app must check values before acting on them, just as a website validates a form. Do not place personal data or secrets in the address, because links are copied, logged and shared. For sensitive actions such as resetting a password, require the user to confirm inside the app.

If a link leads straight to a screen that needs a permission such as the camera, the system prompt will appear with no preparation. Plan the explanation first; our guide to app permissions and privacy basics covers what to tell users.

How to test deep links properly

Test each link type on real devices, in both platforms, in the situations people really use. A short test plan:

  1. App installed and closed, link tapped in a message app.
  2. App installed and already open on another screen.
  3. App not installed, link tapped, then the store, then install and open.
  4. User logged out, then logged in.
  5. Link opened from an email app, a social app and a web page.
  6. Old version of the app still installed.
  7. Link for a missing or removed item.

Add these to the checklist described in how to test a mobile app before launch. Closed testers can try links in the wild too; see beta testing an app with closed testing and TestFlight for how to run that stage.

Keeping links working after launch

Links are a promise you made in emails, printed material and posts that cannot be recalled. So they need maintenance. When you change the website's paths or add a redirect, check the verification file and the app's routing still agree. When you retire a screen, decide where its links should go. The checklist in app maintenance after launch is a good home for these checks.

Watch for trouble in your data. A drop in sessions that start from links, or crashes on launch from a particular route, can point to a broken route. Setting up reporting early makes that visible; see what to set up first for crash reporting and analytics.

If you want a developer to design the link structure alongside the app, the mobile app development page describes what Liftup Technologies builds.

Related guides

Questions and answers

What is a deep link?

A deep link is a link that opens a specific screen inside an app, such as one product or booking, instead of only the start screen. It can come from an email, message, QR code, web page or notification.

How do universal links and app links open the app or the website?

They use ordinary web addresses. When a user taps one, the operating system checks whether an installed app has a verified claim to that domain. If so, the app opens on the right screen. If not, the page loads in the browser, so the link still works.

What breaks deep links?

Common causes are a missing or misplaced verification file, a mismatch between the link and the app configuration, tracking wrappers that change the address, in-app browsers, saved user choices to open in the browser, changed website paths and outdated app versions.

Do I need deep links for my app?

If people will arrive from emails, ads, messages, QR codes or your website and you want them on a specific screen, yes. A small app that is only opened from the home screen may not need them yet.

Can a deep link work if the app is not installed?

A universal or app link falls back to the web page. A deferred deep link can carry the user through the store and install to the intended screen, but this usually needs extra work and depends on current platform rules, so check the documentation.

Who sets up deep links, the developer or the web team?

Both. The app side handles routing, while the website side hosts the verification file and keeps paths and redirects consistent. Agree who owns each part before building.

Tell us what you are building.

A short call, a written plan and a fixed quote. No obligation.

Get a free quote