Google Play policy Coverage policy: fixes and checks

By The Draftbit team · Updated
Sources checked

This guide is for App content, linked content, advertising, developer identity, and third-party experiences.

Google’s policies extend beyond the code you wrote. They apply to content your app displays or links to, ads, user-generated material, and publicly displayed developer-account content.

What to check

Review linked websites, embedded experiences, mini-apps, remote feeds, and the developer website shown on your listing. Check how third-party content changes after your original submission.

The coverage policy restricts apps that let users install other apps. If your feature relies on a permission-specific permitted use case, check that requirement directly rather than treating general access to a package installer as authorization.

How to address the rejection

Remove or correct the violating content wherever users can reach it. For third-party experiences available without installation, verify that their content also meets Play policies and provide review access.

Inspect the wider catalog for the same issue, particularly shared SDKs, templates, or feeds. Google’s review can consider patterns of harmful behavior and abuse risk. In your response, identify the source and the control you changed; saying the material belongs to a third party doesn’t resolve its presence in your app.

Messages this guide can help with

Policy Coverage; Policy Coverage policy violation; Policy Coverage rejection; Policy Coverage denied

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Your next stepSubmit a Google Play release with working review access