How to Set Up Deep Linking in Your Android App—App Links, assetlink.json, & no-code setup (2026 Guide)

If users have to manually search for the right screen and content after being redirected, or your app links are opening in the browser instead of opening in the Android app, your deep linking is incomplete.

Through Deep Linking, it is made possible to open the clicked link exactly to the right screen inside the app. This is configured through Android App Links, a verified connection between your website domain and your app for Android devices. Once configured successfully, it will open any link directly into your Android app.

This guide will walk you through the complete configuration process of deep linking through WebToNative, how to generate an assetlink.json file, and how to publish the file for a successful verification.

So, Let’s Get Started.

What is Deep Linking?

Deep Linking is a technique in which clicking a URL or a link directly takes the user to a specific screen inside the app instead of navigating to the home screen. If the app is not installed on the mobile device, the user is redirected to a fallback URL in the browser. In this case, where the app is not installed, but the user is still taken to the right screen after the app installation, it is called Deferred Deep Linking. It delivers a smooth experience between the link and the user's desire.

For example, when someone clicks on a product link on any platform like Instagram or WhatsApp, the link will open in the desired app inside your Android app. In case you don’t have the app, the link will open in the browser.

How Does Deep Linking Work?

When a user clicks a link on their mobile device, the system checks which app can open the clicked link. If the app is configured to handle that link and your website has a verification file that confirms ownership of the link. Android will skip the browser and open the link directly in the app.

The verification took place through a file named assetlinks.json that is placed on your website. This file indicates that the website and the app belong to the same owner. Without this file, Android app links will not work. Once verified, the entire process is automatic. Every time the user clicks a similar link, your app opens immediately, making the process effortless and professional.

For example, user A on the mobile device searches for Myntra on the browser. He clicks on the link. The link opens in the browser because he doesn’t have the app installed on his mobile device.

User B on the mobile device searches for T-shirts for men on the browser. He clicks on the Myntra link. As he clicks, he is automatically taken to the specific page inside the Myntra app. It is possible because the user has already installed the Myntra app on their mobile device.

Why is Deep Linking Important for Your Android App?

Deep linking directly affects the user experience and engagement with your Android app. When a user is directly taken to the page they were looking for, there are more chances that the user will take an action. It increases the conversion rates and lowers the bounce rates, boosting the user retention.

According to AppsFlyer, users arriving through deep links convert at a higher rate of 2.5x as compared to regular links, with a lift of 148% in Average Revenue Per User (ARPU). Branch.io research confirms that deep linking boosts retention and engagement by taking users to relevant in-app content instead of the home page.

Android deep links make promotional links more impactful for businesses running marketing campaigns. Rather than redirecting users to a generic home screen, you send them straight to the desired page. App links work as a high-quality signal to Google, which helps improve visibility on the Google Play Store. Deep linking strengthens the credibility of your app. As users land exactly where they wanted, increasing the chances of their return and building trust in the app.

Steps to Configure Deep Linking in Your Android App (Via WebToNative)

People who want to configure deep linking without coding on Android, WebToNative offers a no-code setup that handles the complete configuration from the dashboard.

Here is what you have to do:

Step 1: Log In to WebToNative

Navigate to WebToNative and log in to your account. From the dashboard, look for the apps you have built. And click on the app in which you want to configure deep linking. Now, click on the Edit button to edit your Android app.

Step 2: Look for Link Handling

Navigate to the Link Handling section. Click on the link handling.

Step 3: Configure Deep Linking

As you open the Link Handling section. You will see Deep Linking. Click on Configure to start the configuration of the deep linking.

Step 4: Add Your Domain

As you click on "Configure," a pop-up will open to enter the domain of your website. For example, mystore.com is in the field. This will define that whenever a user clicks a link from this domain through a mobile device, open the app instead of redirecting them to the browser.

WebToNative handles the app part of the deep linking. Now, you have to handle a few things at your website level also. However, your website still needs an ownership verification, which is covered below.

Steps to Prepare Your Digital Asset Links JSON File

The Digital Asset Links JSON file, or assetlinks.json, is essential. It is an official document that your website and your Android app belong to the same owner. The Android system uses this file to verify the connection before opening the links in your app.

NOTE: From Android 12, the behavior of deep linking has changed. Non-verified links don’t open inside the app directly. They open in the browser by default. This makes proper assetlinks.json verification even more difficult.

There are two ways to get this file. Both ways are listed below:

METHOD 1: Using Google Play Console

It is the most reliable method, as it pulls the certificate fingerprint directly from Google’s signing system.

Step 1: Log in to Google Play Console. And select your app.

Step 2: Click on Set up from the left sidebar menu. Then select App Signing from the submenu.

Step 3: Scroll down till you find the section named Digital Asset Links. It shows a ready-to-use JSON code block. Copy the entire JSON code.

Step 4: Save the copied JSON code in a file and name it assetlinks.json.

METHOD 2: Deep Links in Google Play Console

In this way, you have to generate the JSON file and register your domain in one place.

Step 1: Log in to Google Play Console and select your app.

Step 2: Go to the Deep Links section from the left sidebar.

Step 3: Click on Add Domain and enter the name of your domain.

Step 4: Play Console will instantly generate a Digital Asset Links JSON code for your domain. Copy the JSON code.

Step 5: Save the copied JSON code in a file and name it assetlinks.json.

Steps to Publish Your assetlinks.json File

Once it assetlinks.json file is ready. You have to upload it to your website at a specific location to make it easily accessible for Android and verify it.

Step 1: Upload the JSON file

Upload the JSON file to your website’s root directory at this location: https://yourdomain.com/.well-known/assetlinks.json. You might need to create a folder called .well-known in your website’s root directory before uploading the JSON file. You must place the assetlinks.json file inside this folder.

Step 2: Confirm The Three Conditions

After uploading the file, verify all three of the following conditions are true:

• The file must be accessible through HTTPS. Open the URL in your browser and confirm it loads successfully without any errors.

• The file must be served with an application or JSON content type. No plain text or HTML inside the file is accepted.

• It should directly respond with the JSON without redirecting to another URL.

Step 3: Publish Your Updated App to the Play Store

This is the step that is ignored by most people. Once deep linking is configured successfully, you must publish it on the Google Play Store with the updated version of your app. Google only verifies the published apps, not your local app builds.

Step 4: Verification Status

Once your app’s updated version is published, you have to wait for 1 to 3 days for the verification confirmation. Then log in to your Google Play Console → navigate to the Deep Links section → view the verification status of your Android app.

If configured successfully, you will see a confirmation that the domain is verified and Android App Links are active. If there are any problems, they will let you know if the problem is with the app's configuration or the assetlinks.json file.

FAQs

1. Do I need any coding or technical skills to configure deep linking through WebToNative?

A. No, you just have to enter your domain in the Link Handling section inside WebToNative’s dashboard.

2. Why are my links still opening in the browser after configuration?

A. The most common reasons can be the assetlinks. json file is saved at the wrong place, it contains another redirection URL, it is not served over HTTPS, or the updated app is not published on the Play Store.

3. How long does the verification process take?

A. Usually, 1 to 3 days after you have published your app on the Google Play Store.

4. What is the assetlinks.json file, and why is it needed?

A. It is an official verification file placed on your website’s root directory that tells Android that your app and website are owned by the same person. Without this JSON file, Android app links will not work correctly.

5. Can I deep-link to multiple pages?

A. Yes, you can deep link multiple pages, including the home page, product pages, payment gateways, and more. The path of the URL defines which screen will appear.

6. Does deep linking work on Samsung Android mobile devices?

A. Yes, deep linking works on Samsung Android mobile devices the same way it works on other Android devices. Although Samsung’s default browser might handle App Links a bit differently. We highly recommend testing your deep links on Samsung devices to ensure they are working properly.

7. Why hasn't the customer installed my app?

A. The link or URL will simply take them to the browser. This is the biggest advantage of HTTPS app links: they smoothly redirect the user to your website.

8. Do I need to configure deep linking separately for iOS?

A. Yes. iOS uses Universal Links, which require a different verification file. WebToNative supports iOS deep linking also.

9. Can I test deep linking before publishing to the Play Store?

A. Yes, you can test deep linking through Android Debug Bridge (ADB) on a development device by running a command that stimulates a link on clicking. The following command:

adb shell am start -W \
-a android.intent.action.VIEW \
-d "https://yourdomain.com/page" \
com.your.package

Conclusion

Deep linking configuration in your Android app is one of the impactful changes you can make for your users and your business. The configuration process is streamlined with WebToNative for a successful configuration. Once done, every link a user shares or clicks will be a direct gateway into your app. It contributes to an effective user experience with high conversions and smarter marketing, all in one configuration.