How to Review App Metadata Accurately as a Tester
Most testers focus entirely on the app itself. But the store listing, screenshots, and description are also tested in review. Here is how to check metadata accurately and write findings that save developers from rejection.
Why metadata matters: Apple guideline 2.3 and Google Play's metadata policy both cover store listing accuracy. Misleading screenshots, inaccurate descriptions, or broken privacy policy links are common rejection triggers that a human tester can catch in minutes.
Metadata elements to check
App name
Does the app name shown on the home screen match the store listing name?
Is the name truncated in the store listing? (App Store allows 30 chars, Google Play 50)
Does the name contain any special characters that look unusual on the device home screen?
App description
Does the app actually do what the description claims? Test all listed features.
Are any claimed features missing, broken, or behind a paywall not mentioned in the description?
Is the description free of superlatives like 'best', '#1', 'most popular' without supporting evidence? (App Store guideline violation)
Does the description mention other platforms or competitor brand names? (May cause rejection)
Screenshots and preview video
Do the screenshots show the actual current UI, or do they look like an older version?
Does the preview video show real app behaviour, or does it show features that are not in the current build?
Are screenshots in the correct orientation for the device type claimed?
If screenshots show 'iPad-optimised', does the app actually run well on tablet layout?
Category and keywords
Is the app category appropriate? A meditation app in the Games category is a mismatch that may cause rejection.
Does the app match its stated age rating? Test for content that seems inconsistent with the age rating shown.
High-impact accuracy gaps to look for
Feature exists in screenshots but not in app
HighThis is a direct cause of Apple rejection under guideline 2.3.3 (misleading screenshots). Document with a side-by-side of the screenshot and your recording of the actual screen.
Free app description but IAP required for basic features
HighIf core features described without pricing context require a purchase, document which features, what they cost, and where this is not disclosed in the description.
App icon on device does not match store listing icon
MediumIcon mismatch between home screen and store listing is a metadata consistency issue. Common after version updates where the store listing was not updated.
Localized content is incorrect
MediumIf you are testing a localized version, note any UI text that is clearly untranslated, machine-translated poorly, or uses the wrong regional variant (e.g., American English spellings in a UK-targeted app).
Privacy policy link in store listing is broken
HighBoth App Store and Google Play require a functional privacy policy link in the store listing. Test the link directly from the store page if possible, or from within the app.
How to write a metadata finding
Metadata findings need to be specific and evidence-based. The developer needs to know exactly what is wrong so they can fix the listing or the app.
Finding title
Screenshot 3 shows a dark mode UI — the app does not have dark mode
Evidence
Attach: the store listing screenshot showing dark mode, and a screen recording of the app showing no dark mode setting
Where I checked
App Store listing on iPhone 15 Pro, iOS 18.2. Settings > Display does not show any theme toggle.
Guideline reference
Apple guideline 2.3.3: apps that use misleading screenshots will be rejected. This screenshot shows UI that does not exist in the current build.
Fix suggestion
Replace screenshot 3 with an accurate screenshot of the current app UI, or implement the dark mode shown in the screenshot.
Testing metadata on both platforms
App Store (iOS)
30-character app name limit
Screenshots must match the device size claimed
No promotional pricing language in description
Age rating must match content you observe
Google Play (Android)
50-character app name limit
No keyword stuffing in title or short description
Feature graphic must be present for store front visibility
Data Safety section must match actual permissions requested
Become an AppTester.co tester
Test real apps on your own device. Metadata review, UX testing, security checks. Structured briefs. Payment per accepted report.