App Store / Google Play · 清单验收 · 不承诺过审Telegram @hagee66

上架通

GOEE LISTING LEDGER

№ ENgoee.cc
账号归你 · 邀请协作


2026-02-12

How to fix metadata rejections: screenshots, description, and features

When screenshots show features the app lacks, copy overpromises, or locales disagree—map the letter and fix in order. Telegram @hagee66.

This guide · Guide library · Apple listing · Google listing · Dual-store · Telegram @hagee66

Metadata rejections boil down to one line: what the store page promises must be reachable in the review build; core in-app capabilities must not be hidden on the store page. Buttons on screenshots, “one-tap AI” in promo copy, paywalls in preview video, or conflicting descriptions across languages often land under Guideline 2.3 and related metadata rules. Changing only the subtitle while leaving screenshots, or updating English copy but not Chinese screenshots, is the most common empty loop.

Goee (goee.cc) folds metadata rejections into rejection remediation: freeze the store page as it was at rejection, then decide whether to change art / copy / build. Field lengths and preview specs follow App Store Connect and Play Console as currently documented. No approval guarantee.

What this guide fixes

  • Screenshots use design mocks for “coming soon” features not in the review build.
  • App Preview shows a logged-in dashboard; reviewers only see guest flow.
  • Chinese description says “free, no ads” while English mentions subscription, or the reverse.
  • Promotional text still shows expired sale price; screenshots keep old discount art.
  • Custom product pages conflict with the default page; review lands on the inconsistent one.
  • Title or keywords include competitor names—trademark risk plus metadata issues.
  • Team treats it as “marketing flourish”; review treats it as misleading.

Who should read

  • Design and marketing: visuals, descriptions, locales.
  • Product: ship the feature or lower the promise.
  • Listing ops: align all locales and build numbers.
  • Teams rejected for “Misleading”: align facts before appealing—see appeals.

Core approach

1. Archive the store page at rejection

Save: all screenshots, preview video, titles and descriptions per language, promotional text, keywords, rating, and build number. Store in the same folder as rejection remediation archive. Without a frozen copy you cannot prove what you fixed.

2. Classify the rejection

Type Typical letter meaning Fix first
Screenshot shows missing UI UI in image does not exist New screenshots or ship feature
Exaggerated copy Absolutes, medical/financial claims Copy ± build
Misleading preview Edited flows not shipped Re-cut or remove preview
Locale conflict Different promises per language One story everywhere
Rating vs content Adult/gambling hints in art Art or questionnaire
Price mismatch Screenshot price ≠ IAP Art + IAP disclosure

Cross-reference common rejection codes.

3. Recommended fix order

  1. Fact check: can reviewers reproduce store claims on this build?
  2. Feature missing: lower promise in screenshots/video/copy first; if strategy requires the feature, schedule dev then resubmit.
  3. Feature exists but buried: improve entry or pick a reachable screen; sync login notes.
  4. Locale sweep: changing one language requires scanning all live localization locales.
  5. New build: Connect-only art changes sometimes need no binary; if behavior is cited, you need a new build.
  6. Resubmit note: list “reason → change → how to verify” with new screenshot thumbs.

4. Screenshots vs ASO

Metadata repair is not an ASO lab. While fixing rejection:

5. Preview video and promotional text

Previews must show real UI in the current version; transitions cannot imply unshipped effects. Promotional text can change quickly but must match screenshots and IAP prices—see promotional text strategy.

6. Play vs Apple

Play Feature Graphic and long description; Apple previews and custom product pages. Do not paste the same wrong assets to both stores.

7. Combined payment + metadata letters

If price and screenshots are both cited, fix IAP path then screenshot pricing, and explain both in one resubmit.

8. Case: copy fixed, screenshot three still leaks

A utility app gets “Misleading”; team removes “cloud OCR” from description but keeps a screenshot with a cloud progress bar. Second rejection. Correct order: list every image and sentence the letter quotes, check off whether capability remains; batch-replace exports. Have a third person read only the store page (no install) and restate real features—if they mention removed capability, keep changing art.

Often no appeal yet—saves a queue round. If the feature exists deep in Settings, either pick a reachable screen or document path in notes with iOS metadata checklist.

9. Age rating and questionnaire

Bloody UI, gambling, undeclared UGC in screenshots can trigger both questionnaire and metadata. After art changes, update age rating—do not swap screenshots only. Adult art on kids listings—see kids category rules.

Copyable template

【Metadata rejection worksheet】
Rejection date:
Clause ref (verbatim):
Build at rejection:
Frozen screenshot filenames:
One-line reason:
Named UI element in art:
Exists in build: Y / N
Decision: art / copy / build / combo
All locales synced: Y / N
New screenshot export date:
Preview re-cut: Y / N
Promotional text updated: Y / N
New build (if needed):
Verifier (walked review path):
Resubmit note draft done: Y / N

Resubmit snippet

Regarding Guideline [x] metadata:
We removed [feature claim] from screenshots [lang] and updated descriptions to match build [n].
Review path: [steps to see the feature that remains in screenshots].
Attached: before/after screenshot list in Review Notes.

Common mistakes

  1. English only; Chinese store still says “free forever.”
  2. Figma mocks instead of device screenshots.
  3. Custom product page forgotten; review hits old page.
  4. Copy toned down but corner badge still says “No.1”.
  5. No new build when letter cites hidden tab.
  6. Appeal without changing art—see appeals.
  7. Stuffing competitor keywords while “fixing”.

Q&A

Metadata-only change—wait for review?
Art/copy changes usually still review; whether a new binary is required depends on the letter and console prompt.

Pixel-perfect screenshots?
Must be reproducible; skin tone OK, “button in image, not in app” not OK.

2.3 and 4.2 together?
Fix metadata and minimum functionality separately; 4.2 see Guideline 4.2.

Sale ended—change art?
Yes; expired promo visuals are misleading risk.

Agency edits Connect directly?
Within handoff checklist authorization—deliver change list to client.

Next steps

Related reading

Return to guide library · Telegram @hagee66