App Metadata Optimization: Which Term Goes in Which Store Field

Ledger

One researched term, one best field, per store

Metadata optimization here is occupancy: after [keyword research](/aseo/app-keyword-research/) names queries the binary can match, this page decides which **store field** holds each keeper. It is not a second query hunt and not a title-only treatise.

Apple and Play do not share a form. A term that belongs in Apple’s subtitle may belong in Play’s short description, or it may already be spent in the Play title. The ledger records that difference so we do not paste one spreadsheet into both consoles.

The ASO hub already said metadata is a family in the program. This URL does not reprint Store demand → Metadata → Creatives. It runs the slotting OS.

We will not invent a count of terms as a SKU. Character limits are constraints on occupancy, not a ranking product.

Index map

What Apple can associate versus what Play can associate

On Apple, association leans on the visible title, the subtitle, and the hidden keyword field. Depth of how Connect packs that 100-character field stays on Apple App Store optimization. This page only marks the field as a **slot** in the ledger.

On Play, association leans on the title plus short and full description text. Play listing experiments as a console vehicle stay on Google Play optimization. This page only marks which **indexable strings** already hold a term so copywriters do not double-spend it.

The index map is not copywriting. It does not write the 4,000-character Play essay. That prose sits on app description optimization.

Occupancy

Stuffing versus a readable listing

Repeating a title token inside Apple’s keyword field wastes the field. Repeating the same job phrase in Play short and the first line of Play long is occupancy waste unless the two surfaces serve different readers (browse tile versus expanded listing).

Readable still wins the human scan. A stuffed subtitle that no shopper would say out loud is a conversion defect we will refuse even if the ledger has a leftover term.

Screenshot captions and preview overlays are not occupancy slots. Frame language stays on screenshot optimization.

Lock vs live

Version-locked strings versus live-editable strings

Apple title and some listing elements wait on a version. Promotional text can change without that wait. Play short and full can usually ship without a binary. The OS names the wait so a dual-store engagement does not treat every edit as the same ticket.

Cadence of which change ships with which binary belongs to app store optimization when both consoles are in one engagement. This page only labels the field as locked or live so the calendar is honest.

We will not sell a weekly metadata SKU. Live-editable is a property of the field, not a retainer product.

Localize fields

Field localization is not a screenshot locale set

A storefront you staff gets its own occupancy ledger. Transliteration versus a localized job phrase is a **title** decision on app title optimization. Here we only decide whether the localized term occupies subtitle, keyword field, or Play short.

Phone versus tablet creative sets are not fields. Do not park locale screenshot production on this URL.

Field notes

Allocation notes that cannot live on keyword research, title, or description

Competitor brand tokens in the Apple keyword field are a policy conversation, not a default occupancy.

Category and age-rating honesty fields are not keyword slots. We will not treat them as leftover term dumps.

Custom store listings on Play may need a **second ledger**, not a copy of the default occupancy map. Console mechanics stay on the Play child.

Custom Product Pages on Apple may need a **page-specific occupancy**, not a screenshot storyboard. Connect pages stay on the Apple child.

Review phrasing is research input on the keyword URL. It is not a reason to stuff a one-star complaint into the title slot here.

Web GSC queries are not occupancy evidence. Pasting Search Console into a subtitle is a ledger fail.

SMO display names are not store fields. Align them; do not allocate store terms on SMO.

GBP attributes are Maps objects. They are not Apple subtitle substitutes. Refusal: Google Business Profile.

LLM citation and GEO are not field occupancy. Frozen `/llm-seo/` stays parked.

Paid UA query lists from PPC are not store occupancy. A paid install query still needs the honesty gate on keyword research before it earns a slot.

We will not claim Apple always indexes Play long description. The stores do not share that form.

What’s New is a copy object on the description child. This OS only notes it is not an indexable Apple keyword-field substitute.

Icon filenames and screenshot filenames are not metadata slots.

A rejected Connect string stays in the ledger as a refuse so the next occupancy pass does not retry the same stuffing.

Play feature graphic alt is not a field. It is a Play **asset** on the screenshot child.

This page will not become a title-formula library. Brand-first versus job-first stays on the title URL.

Depth

Field allocation OS as the per-store metadata object

The field allocation OS is the object of this page: which researched term sits in title, subtitle, keyword field, Play short, or Play long, on which store, without stuffing. It is not query discovery. It is not a screenshot storyboard. The field allocation OS is a placement map after app keyword research exists.

Collision rules in the field allocation OS refuse the same token occupying every visible and hidden box. Apple’s App Store Connect keyword field should not repeat the title. Play short should not clone Play long. The field allocation OS names leftovers: terms that have no honest home are dropped, not jammed.

Per-store maps are why the field allocation OS is not a single spreadsheet pretending Play and Apple share fields. Play has no hidden keyword field. Apple does not index Play’s long description. Google Play optimization and Apple App Store optimization host the consoles. Allocation still decides which term each console receives.

The field allocation OS does not write the visible title string. App title optimization composes brand plus job inside the title limit. Allocation only decides whether a given researched term is allowed to live in that title versus another field. Composition of the name stays on the title child.

The field allocation OS does not draft listing copy objects. App description optimization writes Play short/long and Apple promotional text / What’s New. Allocation marks which queries those copy objects must cover. Sentences and scannable structure stay on the description child.

ASO already mapped metadata as a family in the program. The field allocation OS implements placement after that family is in scope. It does not reprint the hub’s store-demand chooser. Coverage philosophy stays on the parent. Placement logic stays here.

The dual-console calendar does not replace the field allocation OS. App store optimization sequences when packages ship. Allocation decides what is inside the package. Shipping an unallocated dump of terms is a calendar failure and an OS failure at once; we still keep the jobs on different URLs.

Stuffing is a field allocation OS finding, not a density product. Character limits may be named as constraints. We will not sell a keyword-count SKU. If a field is full of tokens the binary cannot match, the field allocation OS empties it rather than celebrating completeness.

Screenshot captions are not the field allocation OS. Creatives may echo a job the allocated title named, but overlay text is not a console field. Screenshot optimization owns storyboard assets. We refuse to treat overlay copy on frame one as a metadata slot in the field allocation OS.

Impression-to-install protocol is not the field allocation OS. Tests may later show that an allocated package fails on the product page. App conversion optimization owns when to test. The OS still allocated the terms; the protocol judges the listing as a funnel, not as a field map.

Ratings copy in public replies is not the field allocation OS. App ratings and reviews own prompt APIs, public responses, and the product-fix loop. We will not siphon review replies into hidden keyword packing. The field allocation OS stays store listing fields on Play and Apple.

Growth mix is not the field allocation OS. Mobile app growth orders store-organic against paid UA, web-to-app, and referral as a lever sequence. Paid headlines in ads are not store fields. The field allocation OS does not become a second hub spine or a user-acquisition calendar.

Web title tags are not the field allocation OS. SEO owns HTML documents and the titles those documents show in web search. Store fields are console objects. A web-to-app page should not contradict the allocated store title, but that is a handoff sentence, not an on-page SEO reprint of the field allocation OS.

Change control for the field allocation OS means a term moving from subtitle to keyword field is a recorded reallocation, not a silent edit. Without that log, stuffing returns as folklore. The OS is the noun people can argue about. “Metadata is weak” is not a finding.

The field allocation OS has no invented rank, paid-install floor, or organic-share promise. The deliverable is a per-store map: which researched term lives in which field, which leftovers were refused, and which siblings write the actual strings, frames, and experiments after allocation is done.