Guide · 7 min read
Google Play Web Search Deep Links 2026: Drive Installs From Google After Firebase App Indexing Ended
Google still indexes Android apps in mobile search results and shows Play Store install prompts to users who haven't downloaded your app yet — but the Firebase App Indexing path that most guides describe was deprecated, and Firebase Dynamic Links stopped working entirely on August 25, 2025. The current mechanism is Android App Links verified through Digital Asset Links. Here's the actual setup that works now.
Firebase App Indexing is gone — Android App Links is the current standard
Firebase App Indexing and Firebase Dynamic Links were deprecated at different times and for different reasons, but the net effect is the same: neither is the right path for getting your Android app into Google Search results today. Firebase Dynamic Links — the short-link redirects that opened your app when a user tapped a link on their phone — stopped working entirely on August 25, 2025. All redirects on both page.link subdomains and custom domain configurations went dead on that date. If your deep link strategy still relies on them, your links are broken.
Firebase App Indexing, the layer that surfaced app content inside Google Search results, was separately deprecated and is no longer the recommended approach according to Google's own documentation. The replacement is Android App Links: a standards-based verification mechanism that ties your app's URL patterns to your domain via a JSON file and signals to Google Search that your app is an authoritative handler for URLs on that domain. The setup requires no Firebase SDK, no third-party dependency, and runs entirely through the Android manifest and your web server.
iOS developers building the equivalent integration should look at Universal Links and Smart App Banners, which are Apple's implementation of the same concept — web-to-app routing via verified domain ownership. The Android and iOS mechanisms are independent, but both feed into Google Search results on their respective platforms.
Android App Links: 3 components that connect your app to Google Search
Android App Links require three things, all of which must be in place simultaneously before Google Search starts surfacing your app: intent filters in your AndroidManifest.xml, a Digital Asset Links JSON file on your domain, and a website-app association verified in Google Search Console. Miss any one of these and the system either ignores your app or fails verification silently.
The intent filter is the declaration inside your Android app that says this activity handles URLs matching this pattern. It needs android:autoVerify="true" on the intent-filter element, an action of android.intent.action.VIEW, and data elements specifying android:scheme="https" plus the host and path pattern. HTTP URLs do not qualify — HTTPS is required. An intent filter that handles example.com/recipes/* will only be verified if your app requests and passes the ownership check for that domain and path.
The Digital Asset Links file lives at /.well-known/assetlinks.json on your HTTPS domain. It declares a relationship between your domain and your app's signing certificate, identified by the SHA-256 fingerprint of your release signing key. The structure is a JSON array with one object containing your package name, the SHA-256 fingerprint, and a delegate_permission statement. Google fetches this file at verification time — if the fingerprint mismatches, the whole chain fails. The website-app association in Search Console then completes the triangle, telling Google Search to treat your app and your website as representing the same content.
What users see in Google Search: install prompts for new users, direct in-app opens for existing ones
Once your App Links are verified and Google Search has indexed your content, users on Android see one of two experiences depending on whether your app is installed. Users who already have your app see an 'Open in [App Name]' affordance alongside the standard web result — tapping it bypasses the browser and opens the specific in-app screen that corresponds to that URL. This works for articles, product pages, recipes, trip listings, and any in-app screen that has a web-equivalent URL you've mapped.
Users who don't have your app installed see a different result: a Play Store install prompt appears inline, surfaced directly in the search result without requiring them to navigate to the Play Store separately. This is the overlooked install driver. These are users who already expressed intent by searching for the content your app contains — they convert at substantially better rates because the query intent and the app's value proposition are already aligned. When they install and open your app from this prompt, your app can deep link directly to the content that matched their query.
The practical implication: your highest-traffic web content is an install funnel. A recipe site that ranks for 'crispy tofu recipe' is not just a web traffic asset — it's a Play Store acquisition surface for every Android user who doesn't already have the app. This is the same principle that makes maintaining a strong web presence for your app worthwhile: web rankings and app distribution are no longer separate channels.
What to deep link — matching web content to in-app screens
Google only surfaces App Links in search results when the in-app destination contains the same content as the matching web page — this is a stated requirement in Google's Search documentation, not an optional design choice. This means that apps without web-equivalent content see limited benefit from App Links, and that apps with rich indexed web content have the most to gain. Recipe apps, news apps, e-commerce apps, travel apps, and any app that surfaces browsable content that also exists on the web are ideal candidates. Apps that are pure utilities with no content-equivalent web presence don't have URL patterns worth mapping.
Within an app that does qualify, prioritize deep links for your highest-traffic web pages first. A content site with 200,000 monthly visitors concentrated on 50 high-performing articles should configure App Links for those article URLs before attempting to cover the full site. The long tail of low-traffic URLs adds complexity without meaningful install volume. Start with the pages that already rank for queries your target users search, then expand coverage as the initial setup proves out.
One constraint worth planning around: mapping URL patterns too broadly — for instance, mapping your entire domain rather than specific content paths — may prevent Google from surfacing the install prompt for queries where the in-app content doesn't clearly match. When users tap through to your Play Store listing, the listing quality closes the install. Making sure your Play Store feature graphic and screenshots are ready before you drive this traffic means the first thing a web-referred user sees is a listing that earns the install.
Test links with Play Console's deep link emulator before you ship
Play Console added a built-in deep link emulator in October 2026 that lets you preview and test App Links without a physical device — a significant improvement over the previous workflow that required adb commands and a connected phone to debug link resolution. The tool is accessible from your app's Play Console dashboard under a dedicated deep link validation section.
The emulator takes a URL as input and shows you which Activity in your app would handle it, whether the intent filter matched the autoVerify requirement, and whether the assetlinks.json lookup returned a valid association. It surfaces the same resolution logic that Android uses on-device, so a link that passes the emulator will open correctly on users' phones. Use it during initial setup to confirm the manifest and JSON are configured correctly, and again after any release that modifies intent filters.
The emulator is particularly useful for diagnosing path-pattern specificity errors. Android path patterns use a limited syntax — pathPrefix, pathPattern, and path — and an intent filter that handles /guides/* won't automatically handle /guides/category/post without explicit nesting. Testing the full range of your URL structure before shipping catches these gaps without requiring a physical device or a staged rollout.
Measuring web-to-app traffic in Google Search Console
Google Search Console's Performance report shows impressions and clicks for your app's deep links surfaced in mobile Google Search — filtering to 'App' (instead of 'Web') shows only the app-linked results. This is the primary data source for understanding whether your App Links setup is driving installs, and it's the first place to check if traffic from web search hasn't materialized after several weeks of setup.
The Queries tab inside the app-filtered Performance view shows which search terms are triggering app deep link results. What matters more than raw click-through rate is the absolute click count: even modest click volume from Google Search represents high-intent users who are worth acquiring. Impressions with zero clicks usually indicate that the matched URL doesn't resolve correctly to an in-app screen, which the Play Console emulator will confirm.
For a broader view of how your web presence converts to app installs across surfaces, combine the Search Console app view with Play Console's install source breakdown, which separates Google Search-driven installs from Play Store organic, direct, and paid channels. The web-to-app visibility strategy and the deep link setup together determine what this channel yields — the web ranking brings users to the result, the App Links convert them into installs.
Gemini and the next phase: deep links as an AI discovery channel
Google is integrating Play Store install prompts and app deep linking into Gemini — the same App Links infrastructure used for Google Search will power discovery inside Gemini chats. The October 2026 Android Developers Blog post on discovery tools describes Play in Gemini as an upcoming surface where users can find and install apps through Gemini-powered recommendations, with direct deep linking to in-app content for apps that are already installed. Setting up App Links now means your app will be ready for this surface without requiring a separate implementation step.
The pattern is consistent with how Ask Play's conversational search works — natural language queries surface app results that match the semantic intent of the question, rather than requiring exact keyword matches. Apps whose metadata and deep link targets accurately reflect their in-app content are the ones that surface in both. The underlying requirement in every case is the same: verified domain ownership, correct intent filters, and in-app screens that deliver what the deep link promises.
The broader trajectory is that app discovery is moving away from the Play Store browse experience and toward AI-mediated recommendations across surfaces — Gemini, Google Search, Perplexity, and similar tools. The developers who structure their app's discoverability signals for AI surfaces today are building compounding advantages as these channels mature. Android App Links are a foundational piece of that stack, not a one-off technical task.
The install channel hiding inside your web traffic
Firebase Dynamic Links are gone and Firebase App Indexing is deprecated — the developers still following those guides are running a broken setup. Android App Links via Digital Asset Links is the current standard, it requires no third-party dependency, and it turns your existing web rankings into a Play Store install funnel. The users arriving from Google Search already know what they want; your App Links just need to give them a one-tap path to your app.
Once that traffic arrives on your Play Store listing, the listing quality closes the install. Build and preview your Play Store screenshots, feature graphic, and icon using the AppsTemple editor — so the first thing a web-referred user sees is a listing that earns the install.
Preview your Play Store assets in the editor →
Frequently asked questions
is firebase app indexing still supported in 2026?
No. Firebase App Indexing is deprecated and is no longer the recommended mechanism for surfacing Android app content in Google Search. Firebase Dynamic Links — the complementary short-link product — stopped working entirely on August 25, 2025, with all redirects on page.link subdomains and custom domain configurations going dead on that date. The current path is Android App Links, configured through intent filters in your AndroidManifest.xml and a Digital Asset Links JSON file on your HTTPS domain.
what is the assetlinks.json file and where does it go?
The assetlinks.json file is a Digital Asset Links declaration that proves your app and your domain are owned by the same entity. It goes at https://yourdomain.com/.well-known/assetlinks.json — served over HTTPS with a content type of application/json. The file contains your app's package name and the SHA-256 fingerprint of your release signing certificate. Google fetches this file when verifying Android App Links. If the fingerprint doesn't match your release key, verification fails and your deep links won't be treated as App Links in Google Search.
does google show my play store listing to users who don't have my app installed?
Yes — this is one of the most valuable aspects of Android App Links. When a user searches on Android for content your app handles, and they don't have your app installed, Google Search can surface a Play Store install prompt directly in search results. The user doesn't need to navigate to the Play Store separately; they can install your app directly from the search result page. This converts users who already expressed intent through their search query, making them higher quality than typical discovery installs.
how do i test android app links without a physical device?
Play Console added a built-in deep link emulator in October 2026 that lets you test App Links without a physical device. Access it from your app's Play Console dashboard. Enter a URL and the tool shows you which Activity would handle it and whether the intent filter and assetlinks.json verification passed. For pre-launch testing, the adb shell am start command with the -W flag and your URL also validates intent filter resolution on a connected device or Android emulator.
where can i see how much traffic my android app is getting from google search?
Google Search Console's Performance report shows impressions and clicks for your app's deep links in mobile Google Search — filter the report to 'App' (not 'Web') to see only app link results. The Queries tab shows which search terms triggered app results. Play Console's install source breakdown separately shows how many installs were attributed to Google Search, which you can correlate with Search Console click data to understand the web-to-install conversion rate for each query group.