The Five-Minute Metadata Checklist: What to Verify Before Every App Store Publish

Why Metadata Determines Whether Your Screenshots Ever Get Seen

Your screenshots may be pixel-perfect, but they only matter if users find your listing. Search drives between 65% and 70% of all app discoveries. If your wiki:metadata isn't optimized, your visual assets sit on a shelf no one visits. The algorithm decides which apps appear in search results based on metadata signals—title, subtitle, keywords, and description—long before anyone swipes through your screenshots.

Think of it as the difference between storefront design and street address. Screenshots are the storefront. Metadata is what puts you on the high-traffic corner instead of a dead-end alley. A beautiful listing buried on page five of search results converts no one.

The advantage: wiki:metadata-optimization is faster than designing screenshots. If your visuals took an hour, your metadata can be locked in five minutes—if you know what to check.

The 10-Item Pre-Publish Metadata Checklist

Run through this list before every publish. Each item takes 30 seconds to verify. Missing even one can cost you rankings or trigger a submission rejection.

1. App Title (30 Characters Maximum)

Your title is the single most heavily weighted ranking factor on both platforms. It must rank for keywords and communicate your brand simultaneously.

Verify:

• Follows "Brand Name — Keyword Descriptor" format (e.g., "Mint — Budget & Finance")
• No special characters that could cause indexing issues
• Not truncated on any device size
• Front-loads keyword if brand is unknown; front-loads brand if established

Tip: "Budget Tracker — MyApp" outranks "MyApp — Track Your Budget" for the keyword "budget tracker." Choose based on brand recognition.

2. Subtitle (iOS) / Short Description (Android)

This is your secondary keyword real estate. It appears directly below your title in search results and is fully indexed.

Verify:

• Under 30 characters (iOS) or 80 characters (Android)
• Contains complementary keywords—not duplicates of title words
• Benefit-focused rather than feature-focused ("Save Money Effortlessly" beats "Expense Logging Tool")
• Reads naturally without keyword stuffing

Tip: On iOS, title and subtitle keywords combine into one indexing pool. Never repeat words between the two. On Android, the short description is shown in search results and heavily weighted—make it persuasive and keyword-rich.

3. Keywords Field (iOS Only — 100 Characters)

This hidden field is unique to the App Store and is one of the most misused metadata fields in ASO. It's a comma-separated list of keywords that Apple indexes but users never see.

Verify:

• Comma-separated with no spaces after commas (spaces waste characters)
• No words duplicated from title or subtitle (Apple already indexes those)
• No plurals if singular form is already covered (Apple handles this automatically)
• No competitor brand names (violates App Store guidelines and risks rejection)
• Includes long-tail and niche variations of primary terms

Tip: Treat this as a 100-character budget. Use single words separated by commas rather than phrases—Apple combines them automatically. "budget,tracker,money,savings,expense" is more efficient than "budget tracker,money savings."

4. Full Description (4,000 Characters)

The two platforms diverge sharply here. On Apple, the description is not indexed for search—it's purely a wiki:conversion-rate-optimization-cro tool. On Google Play, the description is fully indexed, functioning like SEO body copy.

Verify:

• First three lines are compelling (users see this before tapping "more")
• On Google Play: primary keyword appears 3–5 times naturally throughout
• Formatted with line breaks and bullets for scannability
• Includes social proof (download count, rating, press mentions) where applicable

Tip: Write two separate descriptions. App Store description should read like a sales page—all persuasion, no keyword stuffing. Google Play description should be keyword-optimized like a blog post while still reading naturally.

5. Promotional Text (iOS Only — 170 Characters)

Promotional text sits at the top of your App Store description. It can be updated anytime without app review, making it perfect for time-sensitive messaging.

Verify:

• Highlights something timely: new feature, seasonal offer, or limited promotion
• Not generic filler ("Best app ever" wastes the opportunity)

Tip: Use promotional text strategically around holidays, feature launches, or viral moments. "New: AI-powered meal suggestions—try it free this week" is more effective than a static feature list.

6. Release Notes

Release notes are visible to existing users who haven't updated and to new users evaluating your app. Poor release notes ("Bug fixes and improvements") signal a low-effort app.

Verify:

• Specific about what changed ("Redesigned dashboard for faster navigation")

Tip: Great release notes build trust and reduce churn. Users who see active development are more likely to keep the app installed and leave positive reviews.

7. Category Selection

Your primary and secondary categories affect which browse charts you appear in and how the algorithm classifies your app. The wrong category puts you in competition with irrelevant apps or buries you in an oversaturated category.

Verify:

• Primary category accurately reflects core function
• Secondary category (iOS) or additional category (Android) covers secondary use case
• You've reviewed the top 10 apps in your chosen category to confirm competitive landscape is realistic

Tip: A less competitive secondary category can give you chart visibility that's nearly impossible in your primary category. For example, a fitness app might choose "Health & Fitness" as primary and "Lifestyle" as secondary to appear in both charts.

8. Screenshots Uploaded for All Required Device Sizes

Missing screenshots for a specific device size means your app won't appear in search results on that device. This is one of the most common pre-publish oversights.

Verify:

• Screenshots uploaded for every required device size (iPhone 6.7", 6.5", 5.5"; iPad Pro 12.9", iPad Pro 11"; Android phone, tablet, etc.)
• Localized screenshots uploaded for every supported locale
• No placeholder or duplicate screenshots from other device sizes

Tip: Batch export tools make it easy to generate all required sizes from a single design. Make sure you upload them for every locale you support—localized screenshots significantly boost conversion rates.

Both stores now require a valid It's a hard requirement—missing it will block your submission entirely.

Verify:

• - It's accessible without authentication
• URL doesn't return a 404 or redirect to a generic landing page

Tip: If you don't have a But don't use a template blindly—make sure it accurately reflects what data your app collects. Apple and Google reviewers do check, and an inaccurate policy can delay or reject your submission.

10. Age Rating Configured

Your age rating determines who can see and download your app. An incorrect age rating can result in rejection, restricted distribution, or your app being hidden from a large percentage of potential users.

Verify:

• Age rating questionnaire completed accurately in App Store Connect / Google Play Console
• Rating reflects your app's actual content (violence, profanity, user-generated content, etc.)
• If your app includes web browsing, social features, or user-generated content, the rating reflects this

Tip: When in doubt, rate conservatively. A slightly higher age rating won't hurt downloads much, but a rating that's too low can trigger a review rejection and delay your launch.

Why This Checklist Matters More Than Ever

The app stores are more competitive than they were five years ago. In 2020, the average App Store category had roughly 20,000 apps. By 2026, that number has grown to over 35,000 in many categories. The same growth applies to Google Play. More apps means more competition for every keyword, every category chart, and every featured spot.

At the same time, both Apple and Google have tightened review guidelines. Metadata violations that might have slipped through in 2019—keyword stuffing, misleading descriptions, inaccurate age ratings—now trigger rejections or suspensions. The cost of missing a checklist item has gone up.

The good news: most developers still skip this step. They optimize their screenshots, write a quick description, and hit publish. If you run through this checklist, you're already ahead of the majority of new submissions.

The Workflow: From Screenshots to Publish in Under 10 Minutes

Here's the complete pre-publish workflow we recommend:

• Design and export screenshots (30 minutes if using a template-based tool, 2+ hours if designing from scratch)
• Run through this 10-item metadata checklist (5 minutes)
• Upload assets to App Store Connect / Google Play Console (3 minutes)
• Submit for review (1 minute)

Total time from finished screenshots to submission: under 10 minutes. The checklist is the bridge between creative work and publish. Skip it, and you risk rejection, poor rankings, or both.

What Happens If You Skip This Checklist

We've seen the consequences firsthand. Here are the most common outcomes when developers skip pre-publish metadata verification:

• Rejection for guideline violations — Competitor brand names in the keywords field, inaccurate age rating, or missing Each rejection costs 1–3 days of review delay.
• Invisible in search — Missing keywords, duplicated words between title and subtitle, or wrong category selection. The app goes live but never ranks.
• Low conversion rate — Generic release notes, no promotional text, or a description that reads like a feature list instead of a sales pitch. Traffic arrives but doesn't convert.
• Localized listings incomplete — Screenshots uploaded for English but not for other supported languages. The app appears broken in non-English markets.

Every one of these is preventable with a five-minute checklist.

Tools That Automate the Tedious Parts

Running through this checklist manually is straightforward once you know what to check. The harder part is writing the actual metadata—crafting a keyword-rich title, a conversion-focused subtitle, a strategically packed keywords field, and separate descriptions for each platform.

Several tools now automate this process. AI metadata generators analyze your app's category, features, and competitive landscape, then produce optimized metadata for both platforms in under 60 seconds. The workflow looks like this:

• Input your app details (paste your app URL or describe what your app does)
• AI generates optimized title, subtitle, keywords field (iOS), short description (Android), full description (both platforms), and promotional text
• Review and tweak (every field respects character limits and follows ASO best practices)
• Export and publish

The AI doesn't just fill in blanks. It performs keyword research, analyzes competitor metadata, and applies conversion copywriting principles—the same process that takes a human ASO specialist 2–4 hours.

For most developers, this is the natural next step after finishing screenshots. You've already invested in making your listing look great. Now make sure it's findable. Automated metadata generation paired with this checklist means you can go from finished screenshots to submitted app in under 10 minutes—without cutting corners.