{"id":1270,"date":"2026-05-31T09:00:00","date_gmt":"2026-05-31T14:00:00","guid":{"rendered":"https:\/\/tolinku.com\/blog\/?p=1270"},"modified":"2026-03-07T03:49:03","modified_gmt":"2026-03-07T08:49:03","slug":"android-app-links-multiple-domains","status":"publish","type":"post","link":"https:\/\/tolinku.com\/blog\/android-app-links-multiple-domains\/","title":{"rendered":"Handling Multiple Domains with Android App Links"},"content":{"rendered":"\n

Most apps start with a single domain for deep linking: links.yourapp.com<\/code>. Then growth adds complexity. Marketing wants go.yourapp.com<\/code> for campaigns. The rebrand adds newbrand.com<\/code>. A partner integration needs partner.co\/yourapp<\/code>. Each domain needs its own App Links configuration, its own Digital Asset Links file, and its own intent filter entries.<\/p>\n\n\n\n

Getting multi-domain App Links right requires understanding how Android verifies each domain independently, how intent filters interact when multiple domains are declared, and how to avoid the common pitfalls that cause verification to fail on some domains while working on others.<\/p>\n\n\n\n

For the single-domain setup, see the Android App Links complete guide<\/a>. For the Digital Asset Links file format, see the setup and verification guide<\/a>.<\/p>\n\n\n\n

How Multi-Domain Verification Works<\/h2>\n\n\n\n

Android verifies each domain in your intent filters independently. When your app is installed, the system:<\/p>\n\n\n\n

    \n
  1. Scans all <intent-filter><\/code> elements with android:autoVerify="true"<\/code>.<\/li>\n
  2. Extracts every unique android:host<\/code> value.<\/li>\n
  3. Fetches https:\/\/{host}\/.well-known\/assetlinks.json<\/code> for each host.<\/li>\n
  4. Verifies that each file contains your app's package name and SHA-256 fingerprint.<\/li>\n<\/ol>\n\n\n\n

    Critical rule (Android 12+):<\/strong> If ANY domain fails verification, ALL domains may be treated as unverified on some devices. On Android 11 and below, each domain was verified independently: a failure on one domain didn't affect others. Android 12 changed this to an all-or-nothing model for some OEMs.<\/p>\n\n\n\n

    This means every domain you declare must have a valid, accessible assetlinks.json<\/code> file. A single misconfigured domain can break App Links for all your domains.<\/p>\n\n\n\n

    Manifest Configuration<\/h2>\n\n\n\n

    Declaring Multiple Domains<\/h3>\n\n\n\n

    Each domain gets its own <data><\/code> element within the intent filter:<\/p>\n\n\n\n

    <activity\n    android:name=".DeepLinkRouter"\n    android:exported="true">\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" android:host="links.yourapp.com" \/>\n        <data android:scheme="https" android:host="go.yourapp.com" \/>\n        <data android:scheme="https" android:host="newbrand.com" \/>\n    <\/intent-filter>\n<\/activity>\n<\/code><\/pre>\n\n\n\n
    Separate Intent Filters per Domain<\/h3>\n\n\n\n
    If different domains route to different Activities or have different path patterns, use separate intent filters:<\/p>\n\n\n\n
    <!-- Marketing links: go.yourapp.com -->\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    <data android:scheme="https"\n          android:host="go.yourapp.com"\n          android:pathPrefix="\/c\/" \/>\n<\/intent-filter>\n\n<!-- Product links: links.yourapp.com\/products\/* -->\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    <data android:scheme="https"\n          android:host="links.yourapp.com"\n          android:pathPrefix="\/products" \/>\n<\/intent-filter>\n\n<!-- Brand domain: newbrand.com (all paths) -->\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    <data android:scheme="https"\n          android:host="newbrand.com" \/>\n<\/intent-filter>\n<\/code><\/pre>\n\n\n\n
    Digital Asset Links for Each Domain<\/h2>\n\n\n\n
    Every domain must serve its own assetlinks.json<\/code> at \/.well-known\/assetlinks.json<\/code>. The content is identical across all domains (same app, same fingerprint), but the file must be accessible on each one.<\/p>\n\n\n\n
    The File (Same for All Domains)<\/h3>\n\n\n\n
    [{\n  "relation": ["delegate_permission\/common.handle_all_urls"],\n  "target": {\n    "namespace": "android_app",\n    "package_name": "com.example.yourapp",\n    "sha256_cert_fingerprints": [\n      "AB:CD:EF:01:23:45:67:89:AB:CD:EF:01:23:45:67:89:AB:CD:EF:01:23:45:67:89:AB:CD:EF:01:23:45:67:89"\n    ]\n  }\n}]\n<\/code><\/pre>\n\n\n\n
    Hosting Requirements<\/h3>\n\n\n\n
    Each domain must serve this file with:<\/p>\n\n\n\n