Strategy · Research note
Six Decision Points Between a Search Result and an App Screen
Between a search result and an app screen there are six decision points, and only some are yours. Search engines decide what they index, the browser and operating system decide whether a tap opens the app, the store decides where the app exists, and your site decides whether every branch ends on a useful page.
Scope and limits
This note maps the route from platform documentation. It does not report tests of any operator's app or measure how often each branch happens.
The route, step by step
| Step | Decision | Who decides | Governing document |
|---|---|---|---|
| 1. Index | Is the page in the index, and which version was read? | Search engine | Google's mobile-first indexing best practices |
| 2. Result tap | The visitor opens a web page | Visitor and browser | None specific; the page must stand alone |
| 3. Offer | Does the page offer the app, and how? | Your site | Google's interstitial guidance; Apple's Smart App Banners |
| 4. Link tap | Does the tap open the app or stay in the browser? | Operating system and browser | Android App Links verification; Apple universal links and TN3155 |
| 5. Install branch | Is the app offered here, and does the person install it? | Store and visitor | Google Play country allowances; App Store guideline 5.3.4 |
| 6. First launch | Does the app open the intended screen? | Your app | Install Referrer (Android); no person-level equivalent on iOS ads |
Step 1: what the index holds
Search engines index web pages. Google reads "the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." App screens that have no web page are not part of that picture, which is why the page behind every app route matters as much as the app screen. The note on canonical web pages develops this point.
Step 3: the offer on the page
The page decides whether and how to offer the app. A small banner keeps the content readable; a full-screen prompt is a promotional interstitial in Google's terms. Some taps stay in the browser by design; why a link opens the browser instead of the app lists them.
Step 4: the tap
This is the branch most teams think of as deep linking. On Android, a verified App Link opens the app directly; an unverified web link on Android 12 and later is "likely to be handled by the user's web browser by default." On iOS, a correctly set up universal link opens the app when the app is installed and the domain is associated, and otherwise "the system opens the URL in their default web browser." The cases where the browser keeps the link by design are listed in the note on links that open the browser.
Steps 5 and 6: install and first launch
For a casino or sportsbook brand, the install branch exists only in licensed locations. Each store allows different gambling products in each market, as the guide to Google Play and App Store rules for gambling apps sets out. Where the app is offered and installed, opening the original screen on first launch depends on data carried through the install, which is never guaranteed. Design the page so the person can continue on the web if the install branch ends early. The guide to web-to-app fallbacks covers each landing case.
What to take from the map
- Every branch ends on a web page unless several conditions line up, so the web page is the default outcome, not the exception.
- The decisions you control are the page content, the offer, the association files and the fallback.
- Test the branches separately; a fault in one does not show in another.
Questions
Which decision points does the site control?
The content of the web page, the banner or button that offers the app, the association files and intent filters, and where each fallback lands. The operating system, the browser, the store and the visitor's own settings decide the rest.
Does installing the app from a link guarantee the person reaches the original screen?
No. Carrying a destination through an install needs extra data, such as the Play Install Referrer on Android, and the store may not even offer the app in the visitor's location. The note on routing and attribution explains the limits.
Sources
- Google Search Central, Mobile-first Indexing Best Practices, last updated December 10, 2025.
- Apple Developer, Allowing apps and websites to link to your content, no date shown.
- Android Developers, Create deep links, last updated October 23, 2026.
- Google Play Console Help, Country/region allowances for gambling apps, no date shown.
- Apple Developer, TN3155: Debugging universal links, latest revision May 15, 2025.
How we choose and date sources: data sources.