Google Play Closed Testing Link Not Working? Fixes
A symptom-by-symptom guide to fixing opt-in links that say “item not found”, “not available” or do nothing at all.
Read the guide →How to Share Your Google Play Closed Testing Link
Quick answer To share your closed testing link, copy it from the Testers tab of your closed track, click Save, and send it to people on your list. Each tester must opt in and install the app.
Finding the closed testing link takes less than a minute. Getting 12 or more people to open it, join with the right Google account and stay in the test for 14 days is the part that takes planning. This guide shows exactly where the link is, what to send with it, what your testers need to do, and a simple tracking system so you always know who has joined.
How do you share the closed testing link?
Google describes the steps on its testing help page. In Play Console:
- Select your appOpen the app in Play Console.
- Open closed testingGo to Testing > Closed testing and click Manage track.
- Open the Testers tabChoose the email lists, Google Groups or organizations that can test.
- Add a feedback channelEnter a feedback URL or email address. It appears on the opt-in page.
- Copy the linkUse the copy button next to the opt-in link.
- SaveClick Save changes. Testers cannot use the link until the track is published and the release is available.
If you have not added any testers yet, start with our guide to adding testers in Play Console. If your list is ready but the link fails, use the link troubleshooting guide.
What the link does
The opt-in link takes a person to a page that explains what being a tester involves and lets them opt in. Google says each tester needs to opt in using the link, and that testers cannot leave public reviews on test versions. They send private feedback instead, using the channel you added. Because closed tests are not searchable, nobody finds your app by accident. That is useful: it means your testers are the people you chose.
If you are comparing options, an open test works differently: anyone with the link, or anyone who finds the app on Google Play, can join. Our guide to closed testing vs open testing explains when each one makes sense.
How to send it
| Channel | Good for | Watch out for |
|---|---|---|
| WhatsApp or Telegram | Friends, family and groups. Fast replies. | Long messages get skipped. Send the link in its own message. |
| Colleagues and clients. | Mail apps sometimes shorten or break long links. Test one first. | |
| Direct message on social media | Online communities. | Never post the link on a public page and lose control of who asks. |
| QR code | People in the same room. | Scanning phones must be signed in to the right account. |
- Send the link as plain text with nothing glued to the end.
- Send it only to people on your list. Others will not get in, and you will spend time answering them.
- Ask the person to reply when they are done.
What must your testers do after getting the link?
Give them these steps. They are short enough to paste into a message.
- Check the Google accountOn the Android phone, make sure the Play Store uses the Google account whose email you gave me.
- Open the linkOpen it in the browser while signed in to that same account.
- Opt inRead the short explanation and choose to opt in to the test.
- Install the appOpen Google Play from the link and install the app.
- Open it every dayUse the app a little each day and tell me if anything looks wrong.
- Stay in the testPlease do not leave the test for 14 days.
Important: Google says testers who opt in, test for fewer than 14 days and then opt out do not count toward the requirement. Say this clearly when you send the link.
Message templates
The first message
Template: Hi [name], I need testers for my new Android app on Google Play. Could you help for 14 days? It takes about 2 minutes. Please use the Google account [their email]. Link: [opt-in link]. Please reply “done” when you have joined and installed it.
Day 3 reminder
Template: Hi [name], thank you for joining! Please open the app today for a minute and try one feature. Please stay in the test until [end date].
Day 10 reminder
Template: Quick reminder: please do not leave the test yet. We have [number] days left. Open the app once this week and tell me if anything feels slow or confusing.
Track who joined
Use a simple sheet with these columns. It takes two minutes to set up and saves you from guessing when your numbers do not match.
| Name | Email on list | Link sent | Joined (reply) | Installed | Still in on day 7 | Still in on day 14 |
|---|---|---|---|---|---|---|
| Example tester | name@gmail.com | Day 1 | Day 1 | Yes | Yes | Yes |
Compare this sheet with the tester count in Play Console. If a person says they joined but is missing from the count, see why testers sometimes do not count.
A 14-day reminder schedule
| Day | Action |
|---|---|
| 1 | Send the link. Ask everyone to reply when joined. |
| 2 | Chase anyone who has not replied. Resend the link if needed. |
| 3 | First reminder: open the app, try one feature. |
| 7 | Check numbers. Replace anyone who left. See what to do if testers leave. |
| 10 | Second reminder: stay in the test. |
| 14 | Confirm that at least 12 testers have been opted in for 14 days in a row. |
Once the 14 days are done, you can apply. Read how to apply for production access and how long production access takes.
Mistakes to avoid
- Sending the link before the release is rolled out. The opt-in link appears only for a published app and can take several hours to work.
- Forgetting to click Save changes after ticking the list.
- Posting the link publicly and then wondering why strangers cannot join. Closed tests only admit people on your list.
- Never asking for a reply. Silence is not confirmation.
- Starting with exactly 12 people. See the 12 testers rule for a buffer plan.
Part of a series: this article is one chapter of Google Play Closed Testing: The Complete Guide. Start there for the full roadmap from setup to production.
Sources
- Google Play Console Help: Set up an open, closed, or internal test
- Google Play Console Help: App testing requirements for new personal developer accounts
Frequently asked questions
Where do I find the opt-in link?
In Play Console open Testing > Closed testing, click Manage track, then the Testers tab. Choose your lists, add a feedback channel, copy the link and click Save changes.
Can I send the link by WhatsApp or email?
Yes. Any message works, as long as the person opens the link with the Google account that is on your tester list. Send it as plain text and ask them to reply when they have joined.
Does the link work for people who are not on my list?
For a closed test they will not be able to join, because testers must be on a list, Google Group or organization you selected. Open tests are the ones anyone with the link can join.
Do I need a feedback channel?
Google asks you to provide a feedback URL or email address. It appears on the tester opt-in page, and testers use it to send private feedback because they cannot leave public reviews on test versions.
How do I know who joined?
Ask each tester to reply when they have installed the app, keep your own tracking sheet, and compare it with the tester numbers on the track in Play Console.
Can I use a QR code instead of a link?
Yes. A QR code is just another way to carry the same link. Make sure the person who scans it is signed in to the right Google account.
