diff --git a/README.md b/README.md
index bd79d039..284a55dc 100644
--- a/README.md
+++ b/README.md
@@ -43,9 +43,12 @@ Get Clementine Android-Remote:
 
 <a href="https://f-droid.org/packages/de.qspool.clementineremote/" target="_blank">
 <img src="https://f-droid.org/badge/get-it-on.png" alt="Get it on F-Droid" height="80"/></a>
-<a href="https://play.google.com/store/apps/details?id=de.qspool.clementineremote" target="_blank">
+<a href="https://play.google.com/apps/testing/org.clementine_player.remote" target="_blank">
 <img src="https://play.google.com/intl/en_us/badges/images/generic/en-play-badge.png" alt="Get it on Google Play" height="80"/></a>
 
+On Google Play, the app is in open testing for now: the link lets you join it, and install
+the app.
+
 This application is licensed under the GNU GPLv3.
 
 If you have questions, suggestions etc. please write an e-mail.
diff --git a/RELEASING.md b/RELEASING.md
index 9405f1f3..2a1cabe2 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -72,7 +72,9 @@ Play refused the upload, say), run it with that tag to publish it again.
    Closed testing*), and set up open testing (*Testing → Open testing*: the countries it's
    available in). The service account's *Release apps to testing tracks* permission covers
    both; releasing to production needs *Release to production* too, and `PLAY_RELEASE_TRACK`
-   set to include `production`.
+   set to include `production`. Then point README.md's Google Play badge at the store page,
+   `https://play.google.com/store/apps/details?id=org.clementine_player.remote`, instead of
+   open testing's.
 4. If `v*` tags get a repository ruleset, let GitHub Actions bypass it: the workflow pushes
    the tags.