# Metadata studio URL: https://storelift.net/features/metadata-studio/ Language: en Updated: 2026-09-18 Store metadata is a packing problem with a hard wall: a title, a subtitle and a hundred characters nobody else can see. Three screens, three different questions — what is covered, what fits where, and what to actually write. ## What the screen shows Every figure on this page is read from a code path, not written by hand — the same discipline the product applies to your own data. ## Three screens, three questions | Screen | The question it answers | What it is | | --- | --- | --- | | Your text | Which of my tracked keywords does my listing already cover? | An audit — term by term, field by field | | Gap to text | Which uncovered term fits into which slot? | A placement — with the remaining character budget per field | | Draft | What do I write in that slot? | A production step, measured terms in hand | Splitting them is deliberate. In one screen it is too easy to start placing words before you have read the audit — and when the budget is a hundred characters, the order of those two steps decides what gets left out. ## How it works 1. Your listing is read from the store, per storefront, in the language that storefront actually serves. 2. Tracked terms are matched against the fields. A term can appear in the title, the subtitle, the description, or nowhere — and "nowhere" is the interesting column. 3. Free characters are counted per field, not in total, because the fields do not pool: what you cannot fit in the subtitle does not move to the title. 4. You draft against the measurement. The draft screen only offers terms that were actually measured, so a proposal is never built on a keyword nobody searches. NOTE: The 100-character keyword field is not readable from outside. Apple does not publish it, so no tool can show you a competitor's — and any tool that claims to is showing you a guess. Yours is the one you type in. ## What you do with it ## What this does not do Nothing here writes to your store listing. The studio produces text; shipping it stays a manual step in App Store Connect or Play Console, which also means there is no way for a bug on our side to change what your customers see. And a covered term is not a ranked term — coverage is a precondition, not a result. ## What each plan includes | | Free | Pro | Studio | | --- | --- | --- | --- | | Coverage audit | Yes | Yes | Yes | | Gap-to-slot placement | Yes | Yes | Yes | | Terms the audit can draw on | 25 | 250 | 500 | | Storefronts audited | 2 | All 128 | All 128 | | AI-assisted drafting | — | — | Yes | Pro is $20/month ($18 billed yearly), Studio $60/month ($54 billed yearly). The audit and the placement screens are on every plan; only the AI-assisted draft is a Studio feature. ## FAQ Q: Can you show me a competitor's keyword field? A: No, and neither can anyone else. Apple does not publish the 100-character field. What we can show you is which words appear in their title, subtitle and description — those are public. Q: Do the title and subtitle share a character budget? A: No. Each field has its own limit and they do not pool, which is why the placement screen counts them separately. Q: Does this publish my metadata for me? A: No. It produces the text; you ship it yourself in App Store Connect or Play Console. Q: Does a word have to appear in my metadata to rank for it? A: Not always — the store also indexes other signals — but coverage is the part you control. That is why the audit starts with what your listing does and does not contain.