Skip to content
WebViewGold Vibe Coding to App Store
English
Get WebViewGold

Google Play rejection

Google Play Metadata policy rejection: how to fix your app title, icon and screenshots

A Metadata rejection is about your store listing, not your code. Google checks the title, icon, developer name, descriptions and graphics against a short list of formatting and wording rules, and AI-written listings tend to break several of them at once. Most fixes take minutes and need no new build.

From $109 one-time per platform, or let our team do it all from $698.

  • Approval guarantee – or money back within 14 days
  • No coding needed
  • One-time payment, free updates
  • 24/7 human support
  • Made in Germany since 2014 · ISO 27001

What the Metadata policy actually checks

The Metadata policy is Google's rulebook for everything that surrounds your app in the store: the app name, the developer name, the icon, the short and full description, the feature graphic and the screenshots. Its rules are formal and easy to check, which is why many of these rejections come out of automated review within hours. In plain words:

  • The app title may be at most 30 characters long.
  • Title, icon and developer name must not contain emojis, emoticons or repeated special characters, and should not be written in ALL CAPS unless that is how your brand is written.
  • Title, icon and developer name must not refer to store performance or ranking (such as "#1", "App of the year", "Popular" or award badges), to price or promotions (such as "10% off" or "free for a limited time"), or to Google Play programs (such as "Editor's Choice" or "New").
  • Icons must not use misleading symbols, for example an unread-message dot when there is no message, or a download arrow on an app that has nothing to do with downloads.
  • Descriptions must be clear and relevant. Keyword lists, heavy repetition, excessive formatting and unattributed testimonials count as violations.
  • Screenshots and videos must show the real experience of the app.

Accuracy problems, such as features that do not exist or "official" wording, are handled by different policies. If your notice mentions those, the misleading claims guide is the better starting point.

How the rejection notice reads

The email and the Policy status page in Play Console usually name the Metadata policy and point at the element that failed: the app title, the short description, the full description, the icon, the screenshots or the feature graphic. Often the notice also says in which listing language the problem was found. Some notices quote the offending text; others only say that the element contains prohibited content and leave the search to you.

If the notice names a language you never edited, look at your translated listings. Machine translation is a classic source of extra capital letters and added superlatives. As long as the problem is only in the new listing text, the version that is already live usually stays available while you fix it.

Element by element: limits and what gets flagged

ElementLimit or specTypical flag in AI-written listings
App nameMax 30 characters; no emojis, emoticons or repeated symbols; ALL CAPS only if it is your brandA fire emoji plus "HABIT TRACKER #1 Free AI Planner", or a chain of keywords separated by commas
Short descriptionMax 80 charactersPrice promises, a bare list of keywords, a claim you cannot show in the app
Full descriptionMax 4,000 charactersA keyword block at the end, the same phrase in every paragraph, anonymous "user reviews", "best app 2026"
Developer nameSame rules as the title"Best Apps Studio", emojis, or a name that sounds like another company
App icon512 x 512 px, 32-bit PNG with alpha, max 1024 KBRibbons such as "NEW", "FREE" or "-50%", star ratings, a red notification dot, a download arrow
Feature graphic1024 x 500 px, JPEG or 24-bit PNG without alpha"App of the year", Google Play badges, price stickers
ScreenshotsAt least 2 to publish, up to 8 per device type; JPEG or 24-bit PNG; sides between 320 and 3840 px, long side at most twice the short sideDesktop browser captures, design mockups, "Download now" or "Free" banners, captions that cover most of the image

Great way of converting your web app to a native app! Fast turn-around, and a great way to get your apps into the app stores without the need to develop a full native app!

Kevin Joling · FlightConnections & TrainConnections · Trustpilot

Why vibe-coded listings break these rules

The AI wrote an ad, not a listing

Ask a chatbot for a "catchy, SEO-optimized app name" and you get emojis, superlatives and five keywords in 50 characters. Google wants the name of your app plus, at most, a short and plain descriptor.

Icons from image generators

AI icon generators love glossy stars, badges and tiny "NEW" ribbons. Anything that looks like a status indicator, a rating or a price tag is treated as misleading.

Screenshots from the preview pane

A capture of the Lovable or Bolt preview, a browser window or a Figma frame is not the app. Reviewers compare your screenshots with the installed build.

Auto-translated listings

Play Console can translate your listing for you. Translations are reviewed too, and they sometimes turn a calm title into capital letters or slip in words like "best".

Fix the listing in one pass

Text and graphics are listing changes; only a new launcher icon needs a new build.

  1. Rewrite the title

    Use your brand name, optionally followed by a short descriptor: "Acme: Habit Tracker" has 19 characters. Leave out emojis, "#1", "Free", "Pro 2026" and any ALL CAPS that is not part of your brand. Keywords belong in the short and full description; the ASO guide for vibe-coded apps shows how to place them.

  2. Clean up both descriptions

    Short description: one sentence that says what the app does for the user, under 80 characters. Full description: short paragraphs and a few bullet points. Delete keyword blocks, repeated phrases, anonymous quotes and price promises. Saying in the description that the app is free to download is generally fine if it is true; in the title, icon or developer name it is not.

  3. Check the developer name

    It follows the same rules as the title. Use your company or personal name, not "Top Apps" and not a name with emojis or symbols.

  4. Redraw the icon without badges

    Upload a clean 512 x 512 PNG to the store listing and replace the launcher icons in the mipmap folders of your WebViewGold project so both match; the Android app icon guide lists the files. A changed launcher icon needs a new build with a higher version code.

  5. Retake the screenshots inside the app

    Install the build from internal testing, open four to six real screens with realistic demo data and take device screenshots. Hide notifications and the carrier name in the status bar, keep any caption to roughly a fifth of the image, and avoid words like "Best", "Free" or "Download now". Fill in the alt text that Play Console asks for. The screenshot and listing specs guide has a fast workflow.

  6. Check every listing version, then send for review

    Go through all translations, any custom store listings and the feature graphic. Then send the changes for review from the Publishing overview page.

Prompt: generate a compliant title and descriptions

Fill in the brackets first. The rules in the prompt mirror the Metadata policy, so the output is a draft you can paste after a quick read.

Paste into ChatGPT, Claude or your builder's chat
Write a Google Play store listing for my app that complies with the Google Play Metadata policy.
App or brand name: [name]
What the app does today (only real, working features): [list]
Audience: [who it is for]
Rules:
- App title: max 30 characters, brand name first, optionally a short plain descriptor after a colon. No emojis, emoticons, repeated symbols or ALL CAPS words.
- No ranking, award or performance words (best, #1, top, popular, app of the year) and no price or promotion wording (free, sale, % off, limited time) in the title.
- Short description: one plain sentence, max 80 characters.
- Full description: max 4000 characters, short paragraphs, at most 6 bullet points, no keyword lists, no repeated phrases, no testimonials, nothing that is not in my feature list.
- Do not mention other companies, apps or AI models by name.
Output: the title with its character count, the short description with its character count, then the full description.

Metadata checklist before you resubmit

  • App title has 30 characters or fewer and contains no emoji, symbol chain or ALL CAPS word that is not your brand.
  • No ranking, award, price or "New" wording in the title, icon, developer name or feature graphic.
  • Short description under 80 characters; full description free of keyword blocks and anonymous testimonials.
  • Store icon and launcher icon match and contain no badges, dots or arrows.
  • Screenshots captured from the installed app on a phone, with no mockups and no browser frame.
  • Translations and custom store listings checked line by line.
  • Web app checked with the Play Store readiness check, so the screenshots show a polished app.

Frequently asked questions

Can I write "Free" in my Google Play app title?

No. Price and promotional wording is not allowed in the title, the icon or the developer name. You can say in the description that the app is free to download, as long as that is accurate and any paid features are declared.

Are emojis allowed in the Google Play description?

The explicit emoji ban covers the title, the icon and the developer name. In the description, a few emojis are usually tolerated, but excessive or decorative formatting can still be judged as a violation, so use them sparingly or not at all.

My brand is written in capital letters. Is that a problem?

No. ALL CAPS is fine when it is how your brand is actually written. Do not capitalize additional words around the brand name.

Do I need a new build to fix a metadata rejection?

Only if the problem is part of the bundle, typically the launcher icon. Text, screenshots, the feature graphic and the store icon are listing changes that you can send for review without uploading a new version.

Can I put "AI" in my app name?

Yes, as a plain descriptor if the app really uses AI, for example "Acme: AI Meal Planner". Using the brand name of an AI provider such as ChatGPT or Gemini in the title is a different problem and falls under the impersonation rules.

Three ways to get your app into the stores

Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.

Do it yourself

$109 per platform, one-time

The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.

See plans on the main page

Cloud Builder

$349 per license, one-time add-on

No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.

How the Cloud Builder works Try the free demo

Full Service

$698 per platform $798

Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.

Full Service details Powered by WeSetupYourWebViewApp

Winter Sale prices valid until December 31, 2026.

Ready to ship your app?

App Store & Google Play approval guarantee – or your money back within 14 days

Rather hand it over? Full Service: we configure, build and deliver within 72 hours, from $698 per platform. Questions? Chat with us 24/7.

Refunds are granted under the conditions listed in our FAQ: a non-content rejection by Apple and/or Google, claimed within 14 days after purchase.