Deep links and Android App Links connect the web, marketing campaigns, and other apps directly to specific screens inside your app, and they are essential for user acquisition, re-engagement, and a seamless experience. But deep links are notoriously fiddly — a broken link sends users to the wrong place, a browser, or nowhere at all — so they must be tested carefully. Like any app published from a new personal account, yours must complete a closed test with at least 12 testers opted in for 14 continuous days before production access. This guide covers deep link testing to run during your window.
The closed-testing process is the same as for any app, but deep link behavior depends on configuration, Android version, and how the link is opened, so real-device testing is essential. Using your window to validate every link path across devices turns the mandatory wait into assurance that your acquisition and re-engagement links actually work.
The requirement and deep links
The closed-testing requirement is tied to your developer account type, so any app on a new personal account must complete a closed test with 12+ testers for 14 continuous days before production access. See the closed testing guide. The window is a natural opportunity to validate your deep links across the real devices and entry points your testers use.
Standard advice applies: recruit committed, device-diverse testers, keep your count above 12, and prepare your listing in parallel. Deep link testing benefits from testers across Android versions, since link handling has evolved.
Deep links vs App Links
It helps to distinguish plain deep links (custom scheme or http links your app can handle) from verified Android App Links, which use a verified association between your domain and app so that http links open directly in your app without a disambiguation dialog. App Links require hosting a Digital Asset Links file on your domain and correct configuration. Getting App Links verified is what makes web links open seamlessly in your app rather than prompting the user or opening a browser. See Google's App Links documentation.
Test that your App Links are properly verified and open your app directly, and that any custom-scheme deep links work from the contexts you use them. Verification problems are common and cause links to open in a browser instead of your app, silently undermining your campaigns. Confirm your Digital Asset Links configuration is correct during your window. See listing and campaign setup.
Testing every link scenario
Deep links must be tested across many scenarios because behavior differs depending on the app's state and how the link is opened. Test links when the app is not installed (should go to Play, then ideally deferred-deep-link to the right screen after install), when installed but not running, and when already running. Test links opened from a browser, from other apps, from notifications, and from your own marketing. Each combination can behave differently, and each is a path a real user might take.
| Deep link scenario | Expected behavior |
|---|---|
| App not installed | Go to Play; ideally resume to target after install |
| App installed, not running | Launch and navigate to target screen |
| App already running | Navigate to target without losing state |
| From browser / other app | Open in app (App Links) not browser |
| From notification | Open correct screen with context |
Real testers opening links from real contexts reveal the paths that fail. See notification deep links.
Navigation and state on deep link
When a deep link opens a specific screen, your app must handle the navigation stack sensibly — the back button should behave correctly, and the user should not be stranded on a screen with no way back to the rest of the app. Test that deep-linking into a detail screen builds a sensible back stack, that state is preserved appropriately, and that the experience feels coherent rather than dropping the user into a dead end. Poor back-stack handling on deep links is a common, disorienting bug.
Also test that parameters in the link are parsed correctly and that invalid or malformed links are handled gracefully rather than crashing. Deep links often carry data (a product ID, a referral code), and mishandling that data is a frequent source of bugs. Have your testers open a variety of links, including edge cases, and report any wrong destinations, broken back behavior, or crashes. Real-world link testing across devices is what makes deep links dependable. See UI testing before publishing.
Setting up your closed-testing track
Once your signed release build is ready, create a closed-testing track in the Play Console and upload it, add testers by email or Google Group, and share the opt-in link each tester must use before installing. Correct configuration matters because the 14-day clock counts only opted-in testers, and a misconfigured track is a common reason developers realize late that their timer never started. Prepare a set of test deep links covering your scenarios, and verify a few on a real device before inviting your full group. See how to create a closed testing track.
Give testers clear onboarding instructions and a list of links to try from different contexts and app states. Every failed opt-in is a tester who does not count toward your 12, so smooth guidance maximizes active testers from day one and gives you coverage of the many link scenarios across devices.
Recruiting and managing the window
You need 12+ committed, device-diverse testers for 14 continuous days, ideally across Android versions for link-handling coverage. Recruit a buffer above 12, keep testers engaged with clear tasks and quick responses, and give them specific links to open from various contexts. Monitor your active count in the Play Console and recruit replacements early if it slips.
If assembling a version- and device-diverse group is your bottleneck, a service that supplies verified real testers solves it quickly. You can submit your app to get started, and read where to find real testers and how to keep testers engaged.
Why real-device testing matters here
Deep link behavior depends on real link resolution, App Links verification, the browser or app the link is opened from, and the Android version — none of which is fully reproducible with a single emulator command. The paths that break are exactly the real-world ones: a link tapped in a specific browser, opened when the app is in a particular state, on a particular Android version. Only real testers opening real links from real contexts reveal these failures before they cost you conversions.
This is why the closed-testing window, built on real opt-in testers, is genuinely valuable for deep-link-dependent flows. Real testers exercising your links across devices and entry points surface the verification, navigation, and parsing bugs that define whether your links work in the field. The window is your structured chance to validate them before launch, and device and version diversity in your tester group makes that validation trustworthy. See pre-production checks.
Making the 14-day window count
Because the requirement forces you to test anyway, use the window to validate every deep link path that matters to your acquisition and re-engagement. Brief testers with specific links and contexts, and treat their reports as a chance to fix the broken paths that would otherwise silently waste your marketing spend. A well-run window turns a mandatory delay into working links that actually drive users where you intend.
Enter production having confirmed your App Links are verified and every scenario navigates correctly across devices, and you protect the campaigns and integrations that depend on deep links. The 14 days are an investment in a feature that is easy to get subtly wrong. See the testing checklist.
Turning tester feedback into fixes
Give testers a frictionless way to report problems and ask specific questions: did the link open your app or a browser, did it land on the right screen, did the back button behave, did anything break with an unusual link? Concrete questions produce the actionable reports that let you fix the deep-link issues most likely to hurt acquisition and re-engagement.
Then close the loop: when you ship a build addressing reported issues, tell testers what changed and ask them to reconfirm the links on their device. This validates fixes across devices and versions and keeps testers engaged. An app that enters production having already fixed its deep links launches with working acquisition and re-engagement paths. See fixing crashes before production.
A realistic timeline and next steps
Plan backward from the 14-day minimum: a few days to finalize your build, verify App Links, and recruit testers, the continuous 14-day window, then production review, for roughly three to four weeks end to end. Front-load recruitment and link verification so nothing blocks you when the window closes. When it completes, request production access with your listing prepared in parallel. See what happens after 14 days and internal vs closed testing.
Making the 14-day window count
Because the requirement forces you to test anyway, use the window to validate every deep link path that matters to your acquisition and re-engagement. Brief testers with specific links and contexts, and treat their reports as a chance to fix the broken paths that would otherwise silently waste your marketing spend. A well-run window turns a mandatory delay into working links that actually drive users where you intend, across the devices and Android versions they use.
Enter production having confirmed your App Links are verified and every scenario navigates correctly, and you protect the campaigns and integrations that depend on deep links. The 14 days are an investment in a feature that is easy to get subtly wrong and expensive to leave broken once campaigns are live. See the testing checklist.
After launch: monitoring link performance
Your closed test is the start of quality assurance, not the end. After launch, keep an eye on how your deep links and App Links perform as you run campaigns, since a verification that lapses or a new link format can break silently and cost conversions. Watch attribution and any drop-offs where links should be landing users in-app, and re-test links whenever you change domains or add new link types. An app that keeps its links working preserves the acquisition and re-engagement value it built; one that lets them break loses it quietly. See post-launch monitoring.
Key takeaways
- The 12-tester, 14-day requirement applies regardless of deep links.
- Verify Android App Links so web links open in your app, not a browser.
- Test every scenario — app not installed, installed, running, from various sources.
- Handle navigation, back stack, and parameters correctly on deep link.
- Test across devices and Android versions with real link contexts.
Frequently asked questions
Do apps with deep links need closed testing?
Yes. On a new personal account, the 12-tester, 14-day requirement applies regardless of features.
What's the difference between deep links and App Links?
App Links are verified http links that open directly in your app via a Digital Asset Links file; plain deep links may prompt or need a custom scheme.
Why do my links open in a browser instead of my app?
Usually an App Links verification problem. Confirm your Digital Asset Links configuration is correct and verified.
What scenarios should I test?
App not installed, installed but closed, and running; links opened from browsers, other apps, and notifications; and malformed links.
How do I test deep links properly?
With real testers opening real links from real contexts across devices and Android versions, checking destination, back stack, and parsing.
What is deferred deep linking?
It routes a user to the intended screen after they install the app from a link, preserving the original destination through the install. Test this path if you rely on it.
Should I use internal testing for deep links first?
Yes. Verify App Links and a few key link paths on the faster internal track before your counted closed-testing window begins, so obvious link bugs do not waste your window.
What happens to a deep link if my App Links verification lapses?
Links may start opening in a browser or prompting the user instead of your app, silently breaking campaigns. Re-check verification after domain or configuration changes.