Google Play Console: a step-by-step guide

If you have an Android app, SEOcondo's Play Store channel reads your public Play page (title, descriptions, rating and reviews) without any setup.

Connecting Play Console goes further. It lets Clara work inside your developer account through Google's official API:

What Clara can do	What it needs in Play Console
Draft replies to new reviews. You approve each one and she posts it.	Reply to reviews
Update your app's title, short description and full description once you approve a change.	Manage store presence
Show your crash rate and freeze rate, and warn you when Google would rank the app lower because of them.	View app information and download bulk reports (read-only)
Show your daily installs, uninstalls, ratings and store-listing visitors.	The same permission, plus your reports address (step 5)

Nothing is posted or changed without your approval. Google asks apps not to send automatic review replies, so even on full autopilot every Play reply waits for you to approve it.

It takes about 10 minutes, it's free, and you only do it once. You need:

• The Google account that owns your app in Play Console, or one with Admin access to it.
• A computer. The Google Cloud pages are hard to use on a phone.

Why a "robot account"?

Google doesn't let outside tools sign in as you. Instead you create a service account, a robot login that belongs to you, and invite it into Play Console with only the permissions you choose. You can remove it at any time, and SEOcondo never sees your own Google password.

---

Step 1: Choose a Google Cloud project

A "project" is a folder in Google Cloud that holds the robot account. It's free. Any project works. It doesn't have to be new, and it doesn't have to belong to the same Google account as Play Console.

Already have a project? Use it, for example the one you made for Search Console, Analytics or your website. Open Google Cloud, pick it in the project list at the top of the page, and go to step 2. Keep that project selected in steps 2 and 3.

No project yet? Make one in 30 seconds:

1. Open Google Cloud: create a project and sign in.
2. Type any name, for example SEOcondo. Leave Location as it is.
3. Click Create and wait until the bell icon in the top-right corner says it's ready.

If Google asks you to accept its Terms of Service, accept them. You do not need to add a card or turn on billing.

Step 2: Switch on two Google APIs

An "API" is the door SEOcondo uses to talk to Google Play. It's closed by default, so you open it.

1. Open the Google Play Android Developer API page.
2. At the very top of the page, check it shows the project you chose in step 1. If it shows another project, click the name and pick yours from the list.
3. Click the blue Enable button.
4. Now open the Google Play Developer Reporting API page and click Enable again. This one is for crash and freeze rates.

If a button says Manage instead of Enable, that API is already on. Move on.

Step 3: Create the robot account and download its key

1. Open Create service account. Check the project at the top is still the one from step 1.
2. In Service account name type seocondo. Google fills in the ID by itself.
3. Click Create and continue.
4. The next two sections ("Grant this service account access…" and "Grant users access…") are optional. Skip them: click Continue, then Done.
5. You're back at the list. Click the new account's email address. It looks like seocondo@seocondo-play-123456.iam.gserviceaccount.com.
6. Open the Keys tab.
7. Click Add key → Create new key, choose JSON, and click Create.
8. A small .json file downloads to your computer, usually into Downloads.

Keep the file private

The key file works like a password for the robot. Don't email it or put it in a shared folder. SEOcondo stores it encrypted and never shows it again. If it ever leaks, delete the key on the same Keys tab and make a new one.

Already have a service account?

If your developer already has a service account invited to Play Console (for example one used to publish releases), you can upload a key for that one instead and skip the invite in step 4, as long as it has the three permissions listed there. A separate one just for SEOcondo is safer, because you can remove it without affecting anything else.

Upload it in SEOcondo: open your brand → Play Store → Connection → Connect Play Console. Step 3 of that window has a box to choose the file. Once it's read, SEOcondo shows the robot's email with a Copy button for the next step.

Step 4: Invite the robot in Play Console

1. Open Play Console: Users and permissions.
2. Click Invite new users.
3. In Email address, paste the robot's email (the one ending in .iam.gserviceaccount.com).
4. Open the Account permissions tab and tick these three boxes:
   • View app information and download bulk reports (read-only): crash rates, installs and visitors.
   • Reply to reviews: so the replies you approve can be posted.
   • Manage store presence: so the title and description changes you approve can be sent.
5. Click Invite user, then confirm with Send invite.

The robot doesn't need to accept anything. It's ready as soon as Google passes the permission on. That is often a few minutes, and can take up to 24 hours.

Only want some of it?

Leave a box unticked and Clara simply won't do that part. The other parts still work. For example, tick only the first box if you just want to see crashes and installs.

You can also give access to a single app on the App permissions tab instead. But Google only allows the install and visitor reports with the account-wide box.

Step 5 (optional): Installs and store visitors

Play Console saves your install, rating and store-visitor numbers as daily report files. SEOcondo reads them from there, so it needs that folder's address:

1. In Play Console's left menu, click Download reports → Statistics.
2. Next to the page title, click Copy Cloud Storage URI. It looks like gs://pubsite_prod_rev_01234567890123456789/stats/installs/.
3. Paste it into step 5 of the Connect Play Console window. You can also paste it later in the Play Console card on the Connection tab.

Google publishes these reports 3 to 7 days late, so the newest days fill in a little later. A brand-new app may have no reports for its first few days.

Step 6: Connect and check

Click Connect and check. SEOcondo proves the key with Google, then tests each part on its own and shows one line per part:

• ✓ green tick: that part works.
• ⚠ warning: that part needs one more click. The message names the exact box to tick, or the API to switch on.

After a fix, click Check again on the Connection tab. You never need to upload the key again.

---

What happens after you connect

• Every morning SEOcondo reads the week's reviews, crash and freeze rates, the latest reports and your live listing.
• Reviews of 1 or 2 stars get a reply drafted by Clara on the Plan tab, written to fit Google's 350-character limit. Approve it and she posts it. You can also reply to any review yourself on the Audience tab with Reply: Clara drafts it, you edit, then Post on Google Play.
• Listing changes Clara proposes (title, short description, full description) are sent to Google when you approve them. Google reviews listing changes before they're public, usually within a few hours. If an earlier change is still being reviewed, Clara waits instead of cancelling it.
• Crash and freeze rates appear on the Overview tab next to Google's limits: 1.09% for crashes and 0.47% for freezes, measured over 28 days. Above the limit, Google shows your app lower in search, so fix this before any listing work.
• Installs, uninstalls and store visitors appear on the Overview and Traffic tabs.

Screenshots, the icon and new releases stay with you in Play Console. Clara can tell you what to change, but she doesn't make images.

Common problems

"That isn't a Google service-account key file." You uploaded a different file. Use the .json file from step 3. It contains "type": "service_account".

"…API is switched off in your Google Cloud project." Go back to step 2 and click Enable on the API the message names. Make sure the project at the top of the page is the one where you created the robot. Wait five minutes, then Check again.

"Not allowed yet… tick …" In Play Console → Users and permissions, click the robot's email, tick the box the message names, and Save changes. Google can take up to 24 hours to pass it on.

"Google Play has no app with this package name in the developer account the robot was invited to." The robot was invited to a different Play Console account, or the Play Store channel is connected to a different app. Check the package name on the Connection tab, for example com.yourcompany.app.

"Google did not accept this key file." The key was deleted in Google Cloud. Make a new key (step 3, items 5–8) and click Replace key in the Play Console card.

"That reports folder wasn't found." Copy the Cloud Storage URI again from Download reports → Statistics. It must start with gs://pubsite_prod_.

Only reviews from the last week show replies. That's a Google limit: the API only returns reviews written or edited in the last 7 days, and only those with text. Older reviews still appear from your public Play page.

I want to stop. Click Disconnect in the Play Console card. To remove the robot completely, delete it in Play Console → Users and permissions, and delete the project in Google Cloud.