Deep Linking

Before you start

• HTTPS control of the website domain
• Final package or bundle identifier
• Android signing SHA-256 fingerprint
• Apple Team ID for iOS

Configure and verify

1. Enter scheme and host

   Use https and the exact browser-visible host, including www when the site redirects there. Do not include paths or protocol in the host field.

2. Save final signing identity

   Android assetlinks.json must contain the package name and SHA-256 of the certificate that signs the installed app. Play App Signing may use a different certificate from direct APK tests.

3. Download the validation file

   Use the dashboard to prepare assetlinks.json for Android or apple-app-site-association for iOS.

4. Publish under .well-known

   Serve the file at https://yourdomain/.well-known/assetlinks.json or /.well-known/apple-app-site-association without authentication or redirects.

5. Build and test

   Install the signed app, tap a verified HTTPS link from another app, and confirm the target opens inside the app. Also test the website fallback when the app is absent.

Host matching

Validation paths

Android

https://host/.well-known/assetlinks.json

iOS

https://host/.well-known/apple-app-site-association

iOS status

iOS association metadata can be prepared, but a signed iOS app still requires the future macOS/Xcode worker.

Test before release

• Validation URL returns 200 without redirect
• JSON content type is acceptable
• Fingerprint matches the installed certificate
• Link opens the intended page
• Browser fallback works