Guideline 2.3.7 rejection: App name, subtitle, and keywords
What it means, why it happens, and how developers get through it.
Subject line you may see: Guideline 2.3.7 - Performance - Accurate Metadata
What Apple's guideline says
Choose a unique app name, assign keywords that accurately describe your app, and don't try to pack any of your metadata with trademarked terms, popular app names, pricing information, or other irrelevant phrases just to game the system.
From App Review Guidelines, 2.3.7, as revised October 16, 2026.
Common causes
- Another app's name or a trademark in your keywords or subtitle
- Prices or 'free' claims in the app name, subtitle, or screenshots
- An app name longer than 30 characters, or stuffed with keywords
- A subtitle that references other apps or makes claims you cannot verify
How to fix it
- Remove other apps' names and trademarked terms from every metadata field
- Remove prices from the name, subtitle, screenshots, and previews
- Keep the name unique and within 30 characters
- Make keywords describe what your app does
- Reply listing the fields you changed
What to put in your reply
A sample reply note. Replace the brackets with your facts and remove anything that does not apply.
Hello, Thank you for the review. Regarding Guideline 2.3.7, we removed [term] from the [keywords / subtitle / app name] and removed pricing from [field]. No other metadata references other apps or trademarks. Thank you.
Real cases: others who got 2.3.7
No public cases logged yet.
Questions developers ask about 2.3.7
What does a Guideline 2.3.7 rejection mean?
Your app name, subtitle, keywords, or other metadata include other apps' names, trademarks, prices, or irrelevant terms.
Why do apps get rejected under Guideline 2.3.7?
Common causes, based on Apple's guideline text: another app's name or a trademark in your keywords or subtitle; prices or 'free' claims in the app name, subtitle, or screenshots; an app name longer than 30 characters, or stuffed with keywords; A subtitle that references other apps or makes claims you cannot verify.
How do I fix a Guideline 2.3.7 rejection?
1. Remove other apps' names and trademarked terms from every metadata field. 2. Remove prices from the name, subtitle, screenshots, and previews. 3. Keep the name unique and within 30 characters. 4. Make keywords describe what your app does. 5. Reply listing the fields you changed.
Do I need a new build for Guideline 2.3.7?
Fix the listing, then reply. Metadata issues can often be fixed on the product page without a new build. Change the fields, then reply listing exactly what changed. This is how the guideline is usually resolved, not a prediction for your app.
How should I reply to App Review about Guideline 2.3.7?
Reply in App Store Connect. Thank the reviewer and name Guideline 2.3.7, say exactly what changed and in which version and build, give a numbered path the reviewer can follow, and attach proof such as screenshots or a screen recording.
Stuck on 2.3.7?
Do it yourself, faster
App Store Rejection Rescue Kit: the full decoder, 12 reply templates, Notes for Review templates, and a 60-point preflight checklist.
Get the kit, $12Have it written for you
Send your rejection, get a reply drafted for your exact case. Kit buyers get $10 off.
AI-assisted, built on Apple's App Review Guidelines. Not a guarantee of approval. If we do not deliver within 24 hours, you get a full refund.
Reply service, $29Related rejections
See also: 2.3 accurate metadata · 4.1(a) copycats · 5.2.1 intellectual property
Source: Apple's App Review Guidelines, section 2.3.7, as revised October 16, 2026. Last checked . Always read the current official text. How we write these guides.