How to Write a Google Play Store Listing from Product Facts
Play listings invent 4.9 stars. Title and short copy from facts only. Not App Store fields.
The matching generator is the Google Play Store Listing from Product Facts (No Invented Ratings) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).
Honor title and short caps
Write a Google Play Store listing and short description from product facts only. No invented ratings, install counts, or awards. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.
Paste these fields before you hit run:
Product facts (name, features, OS, price model): [Facts]
Title character cap I lock: [TitleCap or 50]
Short description cap: [ShortCap or 80]
Full description cap: [FullCap or 4000]
Keywords I may use (or derive only from Facts): [Keywords]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Content rating I may state (or UNKNOWN): [Age]
That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.
Keywords only from the allowlist
Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.
Walk the Generate list in order:
- Honesty ledger: Facts nouns, caps, Keywords, Age, Lang. Forbidden: star ratings, install counts, Editors Choice.
- Title: from Facts only, under TitleCap. Print count.
- Short description: under ShortCap. Features only from Facts.
- Full description: paragraphs from Facts under FullCap. No invented testimonials.
- Keywords: only Keywords or tokens from Facts. Max 5 unless Facts say otherwise.
- Age: if UNKNOWN, write CONTENT RATING UNKNOWN.
- Refuse: App Store subtitle fields, Microsoft Store keyword fields, fake 4.9 stars, 1M+ installs invent.
- Compliance pass: quote Banned and Never. Print counts. Format as Format.
If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.
Leave content rating UNKNOWN if blank
Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.
Honor the constraints as hard stops, not vibes:
- Google Play listing from Facts only. Not Apple App Store and not Microsoft Store.
- Never invent ratings, installs, or awards.
- Honor character caps.
- No emojis.
When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.
Refuse fake ratings and install counts
Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.
Tags on the card (google play store listing, play console from product facts, no invented play ratings) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.
Fill the card, then run
Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.