Closed testing link not working: "the requested URL was not found"

Here the problem is the link itself. Your tester taps it and lands on a Google error page that ends with "the requested URL was not found on this server", or on a blank page, or on something that isn't your test. Or you can't even find an opt-in link in Play Console.

Two related problems have their own pages. If the opt-in page loads but says "App not available", see "App not available" on the opt-in page. If the tester opted in and the Play Store app says "Item not found", see Item not found.

The error text comes from Google's servers and follows the visitor's language. Your testers may see a different wording.

One quick test first

Open the link yourself in a private browser window. Then:

• It fails for you too: the link or the publishing status is the problem. Start with causes 1 to 4.
• It works for you, fails for some testers: the link is fine. Check cause 5, then the "App not available" page.

Causes and fixes, in the order to try them

1. You copied the wrong link

There are several links in Play Console and they look alike. The one testers need is the opt-in URL. Google gives its format: https://play.google.com/apps/testing/ followed by your package name, for example https://play.google.com/apps/testing/your.new.app. You find it on Closed testing > Testers (Play Console Help).

Common mix-ups:

Fix: go to Test and release > Testing > Closed testing > Manage track > Testers and use the shareable link Google shows there.

2. The package name in the link is wrong

A link can be the right type and still point nowhere. It happens when people type the link by hand, edit it, or paste it into a chat app that adds a period or a parenthesis at the end.

Fix: compare the end of the link, character by character, with the package name shown under your app's name in Play Console. Send the link alone on its own line, with nothing after it.

3. The app isn't published to the track yet

Google is clear: "The opt-in link displays only when an app status is 'Published'. Apps in 'Draft' or 'Pending publication' status do not display an opt-in link." And after the first publish of a test, "the test link can take several hours to become available to testers" (Play Console Help).

So if you can't find a link, or the link returns "not found" in the first hours, the test probably isn't live yet.

Fix: check the status under your app's name (publishing statuses). If it's published, wait a few hours and retry. Don't send the link to your whole list before you've opened it successfully yourself.

4. Your release was never sent, or it was rejected

Two traps sit on the Publishing overview page:

• Changes aren't sent automatically. Google says your changes "are not sent for review until you click Send for review". After a rejection, you have to click it yourself again (Play Console Help).
• A rejected first release keeps the app in Draft. Google's status table says a Draft app "has no presence on Google Play", either because it isn't published yet "or it was rejected during the review process" (Play Console Help).

Fix: open Publishing overview. Send pending changes for review. If there's a rejection, read the reason in your Play Console inbox, fix it, and resubmit. If the release is stuck in review, there's nothing to fix on the link side yet: wait for Google's decision.

5. The link opens in an in-app browser

When a tester taps your link inside a chat app, it often opens in that app's built-in browser. That browser usually isn't signed in to their Google account, so Google can't let them in.

Fix: ask testers to long-press the link and open it in Chrome, or copy it into their usual browser where they're signed in with the address you added.

6. Google removed or suspended the app

Rare, but check it if nothing else fits. The app statuses "Removed by Google" and "Suspended by Google" mean the app isn't discoverable on Google Play (Play Console Help). You'll also have an email and a message in Play Console explaining why.

A clean way to share the link

1. Open the link yourself in a private window. Confirm you see the tester page.
2. Send it as plain text on its own line, in a message that also says which Google account to use.
3. Ask testers to open it in their regular browser, then switch the Play Store app to that same account.

The tester-side steps are in how testers join a closed test if you want to forward them.

When to contact Google

Use the Contact us link in Play Console Help if the closed track has shown "Published" for more than a day, the link you copied from the Testers tab still returns "not found" in a private window, and the package name matches. Include the package name, the exact link and a screenshot.

For the whole requirement end to end, see the Google Play closed testing guide.