App indexing connects your app content to search engines. When done right, users find your app's content through Google, tap a result, and land directly in the app on the relevant screen. When done wrong, you get broken links, wasted crawl budget, and search results that lead to dead ends.<\/p>\n\n\n\n
These best practices reflect the current state of Google and Apple search as of 2026. For the technical setup, see Google app indexing setup<\/a>. For the complete strategy, see app indexing and SEO for mobile apps<\/a>.<\/p>\n\n\n\n Third-party deep link domains ( Use your own domain:<\/p>\n\n\n\n Benefits of using your own domain:<\/p>\n\n\n\n Verification files must be served correctly. Common problems:<\/p>\n\n\n\n The The Test with the Digital Asset Links tool<\/a>.<\/p>\n\n\n\n A deep link URL that only works in the app is a dead end for:<\/p>\n\n\n\n Every deep link URL should serve a real web page:<\/p>\n\n\n\n The web page should have real content, not just "download our app." A product deep link should show the product on the web. An article deep link should show the article. For web fallback configuration, see Tolinku deep linking docs<\/a>.<\/p>\n\n\n\n Structured data tells search engines what the page content represents. Use the appropriate schema.org<\/a> type for each content type:<\/p>\n\n\n\n1. Use Your Own Domain for Deep Links<\/h2>\n\n\n\n
yourapp.app.link<\/code>, dynamic-links.provider.com<\/code>) create a dependency on another company's infrastructure. They also fragment your link equity across two domains.<\/p>\n\n\n\nGood: links.yourapp.com\/products\/shoes\nGood: yourapp.com\/products\/shoes\nBad: yourapp.app.link\/xyz123\nBad: provider.page.link\/?link=...\n<\/code><\/pre>\n\n\n\n\n
apple-app-site-association<\/code> and assetlinks.json<\/code> directly.<\/li>\n<\/ul>\n\n\n\n2. Verify App Links and Universal Links Correctly<\/h2>\n\n\n\n
Apple (AASA)<\/h3>\n\n\n\n
apple-app-site-association<\/code> file must:<\/p>\n\n\n\n\n
https:\/\/yourdomain.com\/.well-known\/apple-app-site-association<\/code><\/li>\nContent-Type: application\/json<\/code><\/li>\n{\n "applinks": {\n "apps": [],\n "details": [\n {\n "appIDs": ["TEAM_ID.com.yourapp.bundle"],\n "components": [\n { "\/": "\/products\/*", "comment": "Product pages" },\n { "\/": "\/categories\/*", "comment": "Category pages" }\n ]\n }\n ]\n }\n}\n<\/code><\/pre>\n\n\n\nAndroid (Digital Asset Links)<\/h3>\n\n\n\n
assetlinks.json<\/code> file must:<\/p>\n\n\n\n\n
https:\/\/yourdomain.com\/.well-known\/assetlinks.json<\/code><\/li>\nContent-Type: application\/json<\/code><\/li>\n[{\n "relation": ["delegate_permission\/common.handle_all_urls"],\n "target": {\n "namespace": "android_app",\n "package_name": "com.yourapp",\n "sha256_cert_fingerprints": ["YOUR_SHA256_FINGERPRINT"]\n }\n}]\n<\/code><\/pre>\n\n\n\n3. Every Deep Link URL Needs a Web Fallback<\/h2>\n\n\n\n
\n
User with app installed \u2192 opens app to correct screen\nUser without app \u2192 sees web page with content + app install prompt\nGooglebot \u2192 sees indexable web page with structured data\n<\/code><\/pre>\n\n\n\n4. Add Structured Data to Every Deep Link Page<\/h2>\n\n\n\n