After your 14-day closed test, you don't just click a button for production access — you answer a set of questions about how you tested. Those answers matter as much as the testing itself, and vague ones are a common, avoidable reason for a rejection.
On this page
What Google is trying to learn from your answers
The questionnaire exists to confirm your closed test was real and useful — not just technically compliant. Reviewers are looking for specific, consistent detail: who tested, how they engaged, what came out of it, and what you did about it.
The question areas, and how to answer them well
- Tester recruitment — be honest about how you found testers. "Through a testing service" is a fine, accurate answer; it's not the part that gets scrutinized.
- Engagement — describe the actual usage pattern you observed, in specific terms rather than "testers used the app."
- Feedback — cite something concrete: "3 testers reported a crash on the checkout screen, fixed in the next build" beats "testers gave positive feedback."
- Changes made — list real, specific changes. "We improved the app" reads as filler; "we fixed a login timeout on Android 13" reads as evidence.
Weak-answer patterns that hurt you
- Vague answers with no specifics.
- Claiming perfect testing with zero issues found — this often reads as unconvincing rather than reassuring.
- Generic, templated language that could apply to any app.
- Answers that don't match the activity Google can see from your testing period.
An honest answer framework
State what actually happened, factually. Cite one or two specific examples per question rather than a general summary. Keep every answer consistent with what your 14-day testing period actually reflects — reviewers are comparing your narrative against your testing data.
Want help with the testing itself?
The questionnaire is easier when the testing behind it was genuine and well documented. Our closed testing service for Google Play is built around exactly that.
- A written QA report from your real 14-day test, so every answer can cite specific findings.
- Help drafting your questionnaire answers from what actually happened during testing, with no invented details.
- Direct communication with me from setup through your production application.
Free to start, pay after testers join
Enrollment is free and needs no card. You pay a flat $25, with no hidden fees, and only once 12 testers show as opted in to your closed test. No one can guarantee Google's decision, so we don't.
Frequently asked questions
How did you recruit testers — what should I say?
Answer honestly and specifically — a testing service, a personal network, or a community group are all acceptable. The recruitment channel isn't the scrutinized part; the genuineness of the testing is.
What if my testers found no bugs?
Don't invent issues. Look for smaller, real feedback — onboarding friction, unclear copy, minor UI confusion — and report that specifically rather than claiming a flawless test.
Should I exaggerate engagement in my answers?
No. Answers that don't match your actual testing activity are a weak-answer pattern that can hurt your review, not help it.
Can I collect feedback by email or WhatsApp instead of Play Console?
Yes — how you collect feedback is up to you, as long as you can describe it specifically and honestly when answering the questionnaire.
What if my answers don't perfectly match Google's expectations?
Prioritize accuracy over guessing what Google wants to hear. Specific, honest answers that match your real testing period are more convincing than answers written to sound ideal.
Official sources