Google Play metadata policy: fixes and checks

Google expects metadata to explain the app clearly and accurately. Keyword blocks, misleading symbols, inappropriate imagery, and promotional claims can trigger rejection even when the app itself works.

What to check

Keep the title within 30 characters. Review title, icon, and developer name for emojis, repeated special characters, unnecessary capitals, ranking claims, price promotions, and implied Play-program status.

Compare screenshots and descriptions with the submitted build. Remove unrelated keywords and anonymous or unattributed testimonials. Store assets need to suit a general audience, including when the app contains age-restricted or educational material.

How to address the rejection

Write a direct description of what users can do, and use actual app screens. Remove symbols that imply unread messages, downloads, or other behavior the app doesn’t provide.

Check every localization and custom listing, not just the default language. In review notes, identify the changed fields and assets. Adding more keywords to compensate for removed claims risks another metadata violation and makes the listing harder to understand.