Back to generator

Metadata

iOS App Metadata Best Practices Before Review

Metadata is where your app becomes understandable to both reviewers and buyers. A strong title names the product clearly, the subtitle explains the main outcome, the promotional text highlights current value, and the long description proves that the app is real, useful, and safe. Treat metadata as a product page, not a keyword stuffing field.

Title and subtitle

Keep the title branded but searchable. The subtitle should contain a plain-language use case, such as receipt scanner, study planner, sleep tracker, or invoice maker. Avoid claims like best, official, or guaranteed unless you can substantiate them.

Description structure

Open with the user problem, list the main workflows, explain premium features honestly, and close with privacy or support notes. Reviewers should understand what the app does without opening a support ticket.

Launch checklist

Use one core keyword in subtitle
Describe real in-app flows
Avoid unsupported claims
Mention support and privacy