Unlisted App Distribution review checklist
Unlisted distribution hides the app from App Store browsing, but it does not make the app private or exempt from review. Anyone with the link can access it.
Use unlisted distribution when the app is not suited to public discovery but still needs App Store delivery through a direct link. Apple says an app must already be on the App Store or ready for final distribution and submitted to App Review before requesting unlisted status. AppReviewReady interpretation: add in-app authorization controls because the link itself is not access control.
Decide whether unlisted is the right distribution model
Unlisted distribution fits partner tools, employee resources, research studies, conference apps, and limited-audience utilities that should not appear in App Store search or charts. It does not fit unfinished betas, secret consumer apps, or software that needs organization-only purchase controls.
If only specific companies or schools should receive the app, private distribution through Apple Business or School Manager may be a better fit. If anyone with a direct link may download but only authorized users can sign in, unlisted can work.
Submit a complete app before requesting unlisted status
- The app should be final-distribution ready, not a beta or prerelease placeholder.
- Review Notes should state that the app is intended for unlisted distribution.
- Metadata should still be truthful and useful to someone who opens the link.
- Support, privacy, account deletion, and login paths must work like any other App Store app.
Do not treat the link as authorization
Apple notes that unlisted apps are available to anyone who has the link. That means the app itself needs a mechanism to prevent unauthorized use if the audience is restricted.
AppReviewReady interpretation: implement account approval, organization codes, invitation checks, SSO, device management, or other in-app controls before distribution. A leaked link should not expose partner data or internal workflows.
Plan link handling and support
- Decide who receives the direct link and where it is published.
- Test any shortened URL and confirm it resolves correctly.
- Prepare support copy for users who find the app but cannot sign in.
- Confirm App Store availability regions match the intended audience.
- Document whether Apple Business or School Manager access is also expected.
Write the unlisted review note
The note should help review understand the distribution plan while still proving the app is complete. Do not imply that unlisted status should excuse missing metadata or broken onboarding.
After approval, monitor where the direct link is shared. If the app starts attracting unintended users, update onboarding and support copy rather than relying on the app's absence from search results.
If the audience changes from limited to public, reassess metadata and conversion paths. Unlisted positioning often leaves screenshots and onboarding too sparse for broader users.
Unlisted distribution intent: Audience: [partners, employees, study participants] Why public discovery is unsuitable: [reason] Access control inside app: [SSO, invite] Review account: [credentials] Link plan: [where direct link will be shared] Support route: [contact]
Primary references checked for this guide
Policy statements above are grounded in the linked Apple documentation. Operational recommendations are AppReviewReady's interpretation and should be tested against your app and the current guideline text.
Check release state
Separate App Review, final distribution readiness, and unlisted request timing.
Open the tool