What you’ll achieve

Android verifies your site↔app relationship by fetching /.well-known/assetlinks.json from your website. This recipe publishes that file.

You’ll need

• The Digital Asset Links JSON for your app. The Play Console generates it: Setup → App signing → Digital Asset Links (it includes your package name and the SHA-256 signing-certificate fingerprint).
• A site served over HTTPS.

Steps

1. Go to Local App Setup → Universal Link.
2. Paste the full JSON into Android Digital Asset Links JSON. The value is validated — invalid JSON is rejected with an error notice and nothing is saved.
3. Click Save. The plugin writes /.well-known/assetlinks.json and adds the application/json content-type rule to .htaccess (managed marker block). A self-check confirms the file is served as JSON and logs an admin_alert to the MAM debug log if not.
4. Verify with Google’s checker: https://digitalassetlinks.googleapis.com/v1/statements:list?source.web.site=https://yoursite.com&relation=delegate_permission/common.handle_all_urls

Troubleshooting

• App still opens the browser — the fingerprint in the JSON must be the Play App Signing certificate (the one Google signs releases with), not your upload key. Re-copy from the Play Console.
• Multiple apps or both debug and release builds — the JSON is an array; paste the complete array with one statement per certificate.

Related articles

• Set up iOS universal links

Metadata