Free Tool · ASO

App Links Checker

Links on your site don't open your app? Audit your Android App Links (assetlinks.json) and iOS Universal Links (apple-app-site-association) files against the official rules, and see how Google's and Apple's verification services read your file and whether an address will open the app.

If you enter a page address, the tool also tests whether that address opens the app.

Match against your own app (optional)

When you enter an address, the page is requested through the Enar SEO server, just like a browser would (because browsers' security rules prevent reading data from other sites directly). The fetched content and addresses are not stored; the analysis runs in your browser.

What are App Links and Universal Links?

They're the systems that open a page directly in your app instead of the browser when a user taps a link to your site. Android calls them App Links and iOS calls them Universal Links. In both, the phone checks a verification file on your site to confirm that the app really belongs to that domain. If the file is missing, broken or served incorrectly, links quietly open in the browser: the user never switches to the app and web-to-app traffic is lost.

What does the tool check?

  • Android (assetlinks.json): whether the file is served at https://domain/.well-known/assetlinks.json without redirects and with the application/json content type; the delegate_permission/common.handle_all_urls relation, the android_app target, and the format of the package name and SHA-256 fingerprint. The entries that Google's Digital Asset Links API reads from the file are listed too.
  • iOS (apple-app-site-association): whether the file is served without an extension in the .well-known folder, over HTTPS and without redirects; the applinks section, the App ID format (10-character Team ID + Bundle ID) and the path rules. The copy in Apple's associated-domains CDN is compared with the one on your site.
  • Address test: if you enter a page address, the tool shows, with the matching rule, whether the components or legacy paths rules on iOS and the dynamic rules (dynamic_app_link_components) on Android 15 and later open that address in the app.

Frequently asked questions

Why do links open in the browser instead of the app?

The most common causes: the verification file is missing or redirected, the fingerprint is wrong on Android (with Play App Signing you need the fingerprint of the app signing key in Play Console, not your upload key), or on iOS the App ID lacks the Team ID or the path rules don't cover the address. The tool checks each of these causes.

I fixed the file but nothing changed. Why?

iPhones and iPads don't get the file directly from your site but from Apple's associated-domains CDN, which refreshes it periodically. The tool compares the CDN copy with the one on your site. Android devices usually verify when the app is installed or updated, so you may need to reinstall the app after fixing the file.

Does it check the app's own settings too?

No, the tool checks the files on your site and the verification services. The android:autoVerify="true" intent filter in AndroidManifest.xml on Android and the applinks:domain.com line in the Associated Domains entitlement on iOS are defined inside the app; check them in your app's project.

Does each subdomain need its own file?

Yes. On Android every linked domain (www.example.com and example.com count separately) needs its own assetlinks.json file. On iOS, too, every domain the app is associated with must serve its own apple-app-site-association file.

To audit your app's store listing, use the ASO Audit tool.