Deep links are URLs that send users directly to specific content inside your mobile app. Instead of landing on your app's home screen, users arrive exactly where you want them: a product page, user profile, checkout flow, or any other screen in your app.<\/p>\n\n\n\n
This guide covers everything you need to know about implementing deep links in 2026. We'll explore the different types of deep links, walk through implementation on iOS and Android, examine common pitfalls, and share best practices from production apps handling millions of deep link clicks.<\/p>\n\n\n\n
A deep link is a URL that points to a specific location within a mobile app rather than simply launching it. Think of deep links as the mobile equivalent of web URLs. Just as Deep linking solves a fundamental problem in mobile apps: without it, every external link to your app dumps users on the same generic home screen. Users then have to navigate through your app to find what they came for, assuming they remember what that was. Many won't bother.<\/p>\n\n\n\n The technical implementation varies by platform. iOS uses Universal Links, Android uses App Links, and both platforms support custom URL schemes. Modern deep linking platforms like Tolinku<\/a> handle these platform differences automatically, letting you focus on defining your link routes rather than wrestling with configuration files.<\/p>\n\n\n\n There are three main types of deep links, each solving different problems. For a focused breakdown, see types of deep links: standard, deferred, and contextual<\/a>.<\/p>\n\n\n\n Standard deep links work when the app is already installed. They use either custom URL schemes ( Custom URL Schemes:<\/strong><\/p>\n\n\n\n HTTPS Deep Links (Universal Links\/App Links):<\/strong><\/p>\n\n\n\n Standard deep links fail when the app isn't installed. Custom URL schemes show an error. HTTPS links fall back to the web, which might be what you want, or might not.<\/p>\n\n\n\n Deferred deep links remember where the user wanted to go, survive the app installation process, and route them to the correct screen after they open the app for the first time. This solves the "install gap" problem.<\/p>\n\n\n\n Here's how deferred deep linking works:<\/p>\n\n\n\n The magic happens through device fingerprinting or deterministic matching. The deep linking service matches the click before install with the app open after install using device characteristics like IP address, user agent, screen resolution, and timezone.<\/p>\n\n\n\n Contextual deep links carry additional data beyond just the destination. This data persists through the installation process and provides context when the user arrives in the app.<\/p>\n\n\n\n Contextual deep links enable powerful use cases:<\/p>\n\n\n\n iOS supports two deep linking mechanisms: custom URL schemes and Universal Links. Apple strongly recommends Universal Links for production apps.<\/p>\n\n\n\n URL schemes are the older approach. You register a custom protocol in your app's Info.plist:<\/p>\n\n\n\n Then handle incoming URLs in your AppDelegate:<\/p>\n\n\n\n The problem with URL schemes: any app can claim any scheme. If two apps register Universal Links solve the security and uniqueness problems of URL schemes. They're HTTPS URLs that open in your app when it's installed, or fall back to your website when it's not.<\/p>\n\n\n\n For the full iOS deep dive, see Universal Links: everything you need to know<\/a>. Setting up Universal Links requires:<\/p>\n\n\n\n Apple App Site Association file<\/strong> (hosted at Xcode configuration<\/strong> (Associated Domains):<\/p>\n\n\n\n Swift implementation<\/strong>:<\/p>\n\n\n\n Apple's Universal Links documentation<\/a> provides additional implementation details.<\/p>\n\n\n\n The AASA file must be served over HTTPS with a valid certificate, return a 200 status code, and have the correct Content-Type header ( Android also supports two deep linking mechanisms: custom URL schemes (via Intent Filters) and App Links (Android's equivalent to Universal Links).<\/p>\n\n\n\n Intent Filters are configured in your AndroidManifest.xml:<\/p>\n\n\n\n Handle incoming intents in your Activity:<\/p>\n\n\n\n App Links are verified HTTPS URLs that open directly in your app without showing the disambiguation dialog. For the full Android guide, see Android App Links: the complete guide<\/a>. They require:<\/p>\n\n\n\n Digital Asset Links file<\/strong> (hosted at AndroidManifest.xml configuration<\/strong>:<\/p>\n\n\n\n Google's Android App Links documentation<\/a> covers the verification process in detail.<\/p>\n\n\n\n Deferred deep linking requires tracking the user's intended destination before they install your app, then retrieving it after installation. You can build this yourself or use a deep linking platform. For a dedicated walkthrough, see deferred deep linking: how it works<\/a>.<\/p>\n\n\n\n The basic approach uses device fingerprinting:<\/p>\n\n\n\n Before install<\/strong>: When a user clicks a deep link without your app installed, redirect them to a web page that:<\/p>\n\n\n\n After install<\/strong>: When the app opens for the first time:<\/p>\n\n\n\n Here's a simplified server implementation:<\/p>\n\n\n\n Building deferred deep linking yourself means handling:<\/p>\n\n\n\n Platforms like Tolinku<\/a> handle this complexity for you. After SDK integration, deferred deep linking works automatically:<\/p>\n\n\n\n Deep links directly impact your App Store Optimization (ASO) and organic search rankings. Both Apple and Google index deep link content, making your app discoverable through search. For a focused guide, see app indexing and SEO for mobile apps<\/a>.<\/p>\n\n\n\n Apple indexes Universal Links content in several ways:<\/p>\n\n\n\n To optimize for iOS indexing:<\/p>\n\n\n\n Google indexes App Links content for Google Search results. When users search for content that exists in your app, Google can show app installation buttons or direct app results.<\/p>\n\n\n\n Enable app indexing in Android:<\/p>\n\n\n\n This is the most common iOS deep linking issue. Universal Links fail silently when misconfigured. See debugging AASA files<\/a> and testing Universal Links<\/a> for detailed troubleshooting.<\/p>\n\n\n\n Common causes:<\/strong><\/p>\n\n\n\n Debugging steps:<\/strong><\/p>\n\n\n\n Android App Links verification happens asynchronously after app installation. If verification fails, your links open in the disambiguation dialog.<\/p>\n\n\n\n Common causes:<\/strong><\/p>\n\n\n\n Debugging steps:<\/strong><\/p>\n\n\n\n When deferred deep links fail, users land on the home screen after installing your app, defeating the purpose.<\/p>\n\n\n\n Common causes:<\/strong><\/p>\n\n\n\n Solutions:<\/strong><\/p>\n\n\n\n Common causes:<\/strong><\/p>\n\n\n\n Best practices:<\/strong><\/p>\n\n\n\n Well-designed deep link routes make your app more discoverable and easier to integrate with other apps and marketing campaigns.<\/p>\n\n\n\n Good:<\/p>\n\n\n\n Bad:<\/p>\n\n\n\n Human-readable URLs are easier to share, remember, and debug. They also perform better in search results.<\/p>\n\n\n\n Include versioning in your routes to maintain backwards compatibility:<\/p>\n\n\n\n Or use different paths for different versions:<\/p>\n\n\n\n When a deep link points to content that doesn't exist (deleted product, private profile, expired offer), don't crash or show an error screen.<\/p>\n\n\n\n Users might type URLs manually or modify them. Support common variations:<\/p>\n\n\n\n Include optional parameters that provide context without breaking the core functionality:<\/p>\n\n\n\n These parameters help with:<\/p>\n\n\n\nhttps:\/\/example.com\/products\/shoes<\/code> takes you to a specific product page on a website, a deep link like myapp:\/\/products\/shoes<\/code> or https:\/\/example.com\/products\/shoes<\/code> can take you directly to that same product inside the mobile app.<\/p>\n\n\n\nTypes of Deep Links<\/h2>\n\n\n\n
1. Standard Deep Links<\/h3>\n\n\n\n
myapp:\/\/path<\/code>) or HTTPS links that the operating system recognizes should open in your app.<\/p>\n\n\n\nmyapp:\/\/product\/123\nmyapp:\/\/user\/johndoe\nmyapp:\/\/settings\/notifications\n<\/code><\/pre>\n\n\n\nhttps:\/\/myapp.com\/product\/123\nhttps:\/\/myapp.com\/user\/johndoe\nhttps:\/\/myapp.com\/settings\/notifications\n<\/code><\/pre>\n\n\n\n2. Deferred Deep Links<\/h3>\n\n\n\n
\n
3. Contextual Deep Links<\/h3>\n\n\n\n
https:\/\/myapp.com\/invite?referrer=alice&campaign=summer2024&discount=20\n<\/code><\/pre>\n\n\n\n\n
How Deep Linking Works on iOS<\/h2>\n\n\n\n
Custom URL Schemes on iOS<\/h3>\n\n\n\n
<key>CFBundleURLTypes<\/key>\n<array>\n <dict>\n <key>CFBundleURLSchemes<\/key>\n <array>\n <string>myapp<\/string>\n <\/array>\n <\/dict>\n<\/array>\n<\/code><\/pre>\n\n\n\nfunc application(_ app: UIApplication, \n open url: URL, \n options: [UIApplication.OpenURLOptionsKey : Any] = [:]) -> Bool {\n \/\/ Parse the URL and navigate to the appropriate screen\n if url.scheme == "myapp" {\n let path = url.path\n let queryItems = URLComponents(url: url, resolvingAgainstBaseURL: false)?.queryItems\n \n \/\/ Handle navigation based on path and query parameters\n \/\/ Example: myapp:\/\/product\/123?source=email\n if path.starts(with: "\/product\/") {\n let productId = String(path.dropFirst("\/product\/".count))\n navigateToProduct(id: productId)\n }\n }\n return true\n}\n<\/code><\/pre>\n\n\n\nmyapp:\/\/<\/code>, iOS picks one arbitrarily. There's no verification that the app claiming the scheme is legitimate. For a detailed comparison, see URI schemes vs Universal Links<\/a>.<\/p>\n\n\n\nUniversal Links on iOS<\/h3>\n\n\n\n
\n
https:\/\/yourdomain.com\/.well-known\/apple-app-site-association<\/code>):<\/p>\n\n\n\n{\n "applinks": {\n "apps": [],\n "details": [\n {\n "appID": "TEAMID.com.company.app",\n "paths": [\n "\/product\/*",\n "\/user\/*",\n "\/invite\/*"\n ]\n }\n ]\n }\n}\n<\/code><\/pre>\n\n\n\napplinks:yourdomain.com\n<\/code><\/pre>\n\n\n\nfunc application(_ application: UIApplication,\n continue userActivity: NSUserActivity,\n restorationHandler: @escaping ([UIUserActivityRestoring]?) -> Void) -> Bool {\n \n guard userActivity.activityType == NSUserActivityTypeBrowsingWeb,\n let url = userActivity.webpageURL else {\n return false\n }\n \n \/\/ Handle the Universal Link\n handleDeepLink(url: url)\n return true\n}\n\n\/\/ For iOS 13+ with SceneDelegate\nfunc scene(_ scene: UIScene, continue userActivity: NSUserActivity) {\n guard userActivity.activityType == NSUserActivityTypeBrowsingWeb,\n let url = userActivity.webpageURL else {\n return\n }\n \n handleDeepLink(url: url)\n}\n<\/code><\/pre>\n\n\n\napplication\/json<\/code>). iOS downloads this file when the app is installed and periodically afterwards to check for updates. For setup details, see the AASA file setup guide<\/a>.<\/p>\n\n\n\nHow Deep Linking Works on Android<\/h2>\n\n\n\n
Intent Filters on Android<\/h3>\n\n\n\n
<activity android:name=".MainActivity">\n <intent-filter>\n <action android:name="android.intent.action.VIEW" \/>\n <category android:name="android.intent.category.DEFAULT" \/>\n <category android:name="android.intent.category.BROWSABLE" \/>\n \n <!-- Custom URL scheme -->\n <data android:scheme="myapp" \/>\n <\/intent-filter>\n \n <intent-filter>\n <action android:name="android.intent.action.VIEW" \/>\n <category android:name="android.intent.category.DEFAULT" \/>\n <category android:name="android.intent.category.BROWSABLE" \/>\n \n <!-- HTTPS URLs -->\n <data android:scheme="https" \n android:host="myapp.com" \n android:pathPrefix="\/product" \/>\n <\/intent-filter>\n<\/activity>\n<\/code><\/pre>\n\n\n\noverride fun onCreate(savedInstanceState: Bundle?) {\n super.onCreate(savedInstanceState)\n setContentView(R.layout.activity_main)\n \n handleIntent(intent)\n}\n\noverride fun onNewIntent(intent: Intent) {\n super.onNewIntent(intent)\n handleIntent(intent)\n}\n\nprivate fun handleIntent(intent: Intent) {\n val action = intent.action\n val data = intent.data\n \n if (Intent.ACTION_VIEW == action && data != null) {\n val path = data.path\n val productId = data.getQueryParameter("id")\n \n when {\n path?.startsWith("\/product\/") == true -> {\n val id = path.removePrefix("\/product\/")\n navigateToProduct(id)\n }\n path?.startsWith("\/user\/") == true -> {\n val username = path.removePrefix("\/user\/")\n navigateToUser(username)\n }\n }\n }\n}\n<\/code><\/pre>\n\n\n\nAndroid App Links<\/h3>\n\n\n\n
\n
autoVerify="true"<\/code><\/li>\nhttps:\/\/yourdomain.com\/.well-known\/assetlinks.json<\/code>):<\/p>\n\n\n\n[{\n "relation": ["delegate_permission\/common.handle_all_urls"],\n "target": {\n "namespace": "android_app",\n "package_name": "com.company.app",\n "sha256_cert_fingerprints":\n ["FA:C6:17:45:DC:09:03:78:6F:B9:ED:E6:2A:96:2B:39:9F:73:48:F0:BB:6F:89:9B:83:32:66:75:91:03:3B:9C"]\n }\n}]\n<\/code><\/pre>\n\n\n\n<activity android:name=".MainActivity">\n <intent-filter android:autoVerify="true">\n <action android:name="android.intent.action.VIEW" \/>\n <category android:name="android.intent.category.DEFAULT" \/>\n <category android:name="android.intent.category.BROWSABLE" \/>\n \n <data android:scheme="https" \n android:host="myapp.com" \/>\n <\/intent-filter>\n<\/activity>\n<\/code><\/pre>\n\n\n\nImplementing Deferred Deep Linking<\/h2>\n\n\n\n
Building Deferred Deep Linking Yourself<\/h3>\n\n\n\n
\n
\n
\n
\/\/ Store click data\napp.post('\/api\/deeplink\/click', (req, res) => {\n const { fingerprint, destination, timestamp } = req.body;\n \n \/\/ Store in database with TTL (e.g., 24 hours)\n await db.clicks.create({\n fingerprint: hashFingerprint(fingerprint),\n destination,\n timestamp,\n expires: Date.now() + 24 * 60 * 60 * 1000\n });\n \n res.json({ success: true });\n});\n\n\/\/ Retrieve destination after install\napp.post('\/api\/deeplink\/match', async (req, res) => {\n const { fingerprint } = req.body;\n const hashedFingerprint = hashFingerprint(fingerprint);\n \n \/\/ Find recent clicks matching this fingerprint\n const match = await db.clicks.findOne({\n fingerprint: hashedFingerprint,\n expires: { $gt: Date.now() }\n });\n \n if (match) {\n \/\/ Delete the match to prevent reuse\n await db.clicks.delete({ _id: match._id });\n res.json({ destination: match.destination });\n } else {\n res.json({ destination: null });\n }\n});\n<\/code><\/pre>\n\n\n\nUsing a Deep Linking Platform<\/h3>\n\n\n\n
\n
\/\/ iOS - AppDelegate or SceneDelegate\nTolinku.shared.handleDeepLink { result in\n switch result {\n case .success(let deepLink):\n \/\/ Navigate to deepLink.url\n \/\/ Access context data via deepLink.parameters\n case .failure(let error):\n \/\/ Handle error or default navigation\n }\n}\n<\/code><\/pre>\n\n\n\n\/\/ Android - MainActivity\nTolinku.handleDeepLink(this) { result ->\n when (result) {\n is DeepLinkResult.Success -> {\n \/\/ Navigate to result.url\n \/\/ Access context via result.parameters\n }\n is DeepLinkResult.Error -> {\n \/\/ Handle error or default navigation\n }\n }\n}\n<\/code><\/pre>\n\n\n\nDeep Linking and App Store Optimization<\/h2>\n\n\n\n
iOS App Indexing<\/h3>\n\n\n\n
\n
import CoreSpotlight\nimport MobileCoreServices\n\nfunc indexContent(product: Product) {\n let attributeSet = CSSearchableItemAttributeSet(itemContentType: kUTTypeText as String)\n attributeSet.title = product.name\n attributeSet.contentDescription = product.description\n attributeSet.thumbnailData = product.image.pngData()\n \n let item = CSSearchableItem(\n uniqueIdentifier: "product-\\(product.id)",\n domainIdentifier: "com.myapp.products",\n attributeSet: attributeSet\n )\n \n item.expirationDate = Date.distantFuture\n \n CSSearchableIndex.default().indexSearchableItems([item]) { error in\n if let error = error {\n print("Indexing error: \\(error.localizedDescription)")\n }\n }\n}\n<\/code><\/pre>\n\n\n\nAndroid App Indexing<\/h3>\n\n\n\n
import com.google.firebase.appindexing.Action\nimport com.google.firebase.appindexing.FirebaseAppIndex\nimport com.google.firebase.appindexing.builders.Actions\n\nfun indexContent(product: Product) {\n val url = "https:\/\/myapp.com\/product\/${product.id}"\n \n val action = Actions.newView(\n product.name,\n url\n )\n \n FirebaseAppIndex.getInstance().update(\n Indexable.Builder()\n .setName(product.name)\n .setDescription(product.description)\n .setUrl(url)\n .setImage(product.imageUrl)\n .build()\n )\n \n FirebaseAppIndex.getInstance().start(action)\n}\n\noverride fun onStop() {\n super.onStop()\n \n \/\/ Log the end of the view action\n FirebaseAppIndex.getInstance().end(action)\n}\n<\/code><\/pre>\n\n\n\nCommon Deep Linking Problems and Solutions<\/h2>\n\n\n\n
Problem 1: Universal Links Not Opening the App<\/h3>\n\n\n\n
\n
\n
curl -i https:\/\/yourdomain.com\/.well-known\/apple-app-site-association<\/code><\/li>\ncurl -i https:\/\/app-site-association.cdn-apple.com\/a\/v1\/yourdomain.com<\/code><\/li>\nswcd<\/code> process errors<\/li>\n<\/ol>\n\n\n\nProblem 2: App Links Verification Failing<\/h3>\n\n\n\n
\n
# Test with Google's validator\nhttps:\/\/digitalassetlinks.googleapis.com\/v1\/statements:list?source.web.site=https:\/\/yourdomain.com&relation=delegate_permission\/common.handle_all_urls\n\n# Check verification status on device\nadb shell pm get-app-links com.your.package\n\n# Force reverification\nadb shell pm verify-app-links --re-verify com.your.package\n<\/code><\/pre>\n\n\n\nProblem 3: Deferred Deep Links Not Working<\/h3>\n\n\n\n
\n
\n
Problem 4: Deep Links Working in Development but Not Production<\/h3>\n\n\n\n
\n
\n
Best Practices for Deep Link Routes<\/h2>\n\n\n\n
1. Design Human-Readable URLs<\/h3>\n\n\n\n
https:\/\/app.com\/product\/nike-air-max-90\nhttps:\/\/app.com\/user\/johndoe\nhttps:\/\/app.com\/article\/deep-linking-guide\n<\/code><\/pre>\n\n\n\nhttps:\/\/app.com\/p?id=12345\nhttps:\/\/app.com\/content?type=usr&q=98765\nhttps:\/\/app.com\/x\/AbC123XyZ\n<\/code><\/pre>\n\n\n\n2. Version Your Routes<\/h3>\n\n\n\n
https:\/\/app.com\/v1\/product\/123\nhttps:\/\/app.com\/v2\/product\/nike-air-max-90\n<\/code><\/pre>\n\n\n\nhttps:\/\/app.com\/products\/123 # Old numeric IDs\nhttps:\/\/app.com\/product\/nike-air-max # New slugs\n<\/code><\/pre>\n\n\n\n3. Handle Missing Content Gracefully<\/h3>\n\n\n\n
func handleProductDeepLink(productId: String) {\n ProductService.fetch(id: productId) { result in\n switch result {\n case .success(let product):\n navigateToProduct(product)\n case .failure(let error):\n if error == .notFound {\n \/\/ Show search with the product ID pre-filled\n navigateToSearch(query: productId)\n } else {\n \/\/ Show home with a subtle error message\n navigateToHome(message: "Product not available")\n }\n }\n }\n}\n<\/code><\/pre>\n\n\n\n4. Support Multiple URL Formats<\/h3>\n\n\n\n
\/\/ All of these should work\n"https:\/\/app.com\/product\/123"\n"https:\/\/app.com\/products\/123"\n"https:\/\/app.com\/p\/123"\n"https:\/\/app.com\/item\/123"\n\n\/\/ In your router\nwhen {\n path.matches("\/products?\/\\\\d+".toRegex()) -> handleProduct(id)\n path.matches("\/p\/\\\\d+".toRegex()) -> handleProduct(id) \n path.matches("\/item\/\\\\d+".toRegex()) -> handleProduct(id)\n}\n<\/code><\/pre>\n\n\n\n5. Add Context Parameters<\/h3>\n\n\n\n
https:\/\/app.com\/product\/123?source=email&campaign=black-friday\nhttps:\/\/app.com\/invite\/abc123?referrer=johndoe&reward=10\n<\/code><\/pre>\n\n\n\n\n
Security Considerations<\/h2>\n\n\n\n