# A receipt app reviews the whole metadata set

Companion to /learn/ios/keyword-field/

## Outcome
Turn an intent map into a reviewed App Store keyword-field draft and a traceable release.

Fictional example, not a client result.

## Scenario
PaperTrail is a fictional iOS receipt app. Its team has an app-name draft, a subtitle draft and a keyword-field draft produced by three different people. Each person has repeated the same central terms, while a useful receipt-storage intent is missing from the overall research map. The problem is coordination before it is character counting.

## Reasoning
Review the three drafts together against the same market-specific intent map. Check the current Apple instructions before formatting the keyword field. Keep product relevance, rights and accuracy as explicit checks. A field that fits the technical limit can still be poor work if it represents unsupported features or a confused audience.

## Action
Create a single review sheet showing visible metadata beside the keyword-field draft and the reason for each candidate. Check for unnecessary repetition in light of Apple’s guidance, then have a second person inspect the final text copied into the publishing interface. Save the released version and its date. Do not claim that a particular field combination guarantees a particular search placement.

## Trap to avoid
Do not infer a competitor’s hidden keyword field from its visible listing or rankings. You can observe public metadata and search context; you cannot honestly label a guessed private field as verified evidence.

## Advanced considerations
Keep changes interpretable. If the name, subtitle, keyword field, screenshots and acquisition campaign all change together, later movement will be difficult to attribute. Sometimes a coordinated release is necessary; document it rather than inventing single-variable certainty. Review discovery signals alongside relevant listing and product evidence, and use a comparable observation context.

## Exercise
There is room left in the keyword field. A colleague suggests adding a famous competitor brand to fill it. What is the correct next step?

## Suggested answer
Do not treat unused space as permission to add unrelated or unauthorised terms. Review Apple’s rules and the relevance of the proposed phrase. A shorter defensible field is preferable to filler that creates a misleading association.

## Your worksheet

### Locale and current Apple reference
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### App name and subtitle drafts
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Keyword-field draft
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Intent rationale for each candidate
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Formatting, relevance and rights review
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Published version and observation plan
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

## Review a complete metadata set, not an isolated string
PaperTrail is fictional. The draft below assumes receipt scanning, record organisation and export are supported. It demonstrates the review process; the phrases have not been validated for demand or availability as a brand.

Illustrative English metadata only. Character counts describe these exact ASCII strings, not approved store submissions.
Field / review | Illustrative draft | Reason or acceptance check
App name | PaperTrail: Receipt Scanner | 27 characters; readable product description
Subtitle | Organize purchase records | 25 characters; describes the supported outcome
Keyword-field draft | expense,organizer,export,archive | 32 characters; comma-separated research candidates
Excluded intent | payroll,tax filing | Unsupported workflows, regardless of unused space
Final acceptance | Actual locale and published metadata | Confirm product truth, rights, current rules and console validation

### Count the draft, then validate its meaning
A counter can catch an overlong draft but cannot judge relevance or rights. Review each candidate against the product and chosen audience. Check that the visible copy addresses the same need as the field. Do not add filler merely because capacity remains; unused space is preferable to an unsupported promise.

### Keep the research record outside the final field
Retain each candidate’s intent, source, locale and decision in the working sheet. The published string should not become the only surviving record of the research. When a stakeholder asks why a term was omitted, the answer should be a documented product or evidence decision rather than a guess based on the last release.

### Use a two-person release check
Have the publishing owner copy the approved localized draft, then have a reviewer compare the actual console fields with the approved version. Recheck after any last-minute edits. Save the release date, exact strings and concurrent changes. If later discovery moves, that record makes investigation possible without claiming that the keyword field alone caused the result.

## Continue reading
- /learn/keywords/research-process/
- /learn/ios/subtitle/
- /learn/measurement/metadata-change-log/