---
title: "App store metadata"
description: "A field-by-field definition of app store metadata on both stores, with the index-versus-human weighting that decides how each field should be written."
excerpt: "Every metadata field must answer two questions: which searches am I serving, and which claim am I making to the visitor who reads me?"
source_url: "https://appstorehelper.com/glossary/app-store-metadata"
mirror_url: "https://appstorehelper.com/mirror/glossary/app-store-metadata"
section: "A shared ASO and creative-ops vocabulary"
locale: "en"
published_at: "2026-07-30"
updated_at: "2026-07-30"
reading_time: "4 min read"
tags:
  - "metadata"
  - "glossary"
  - "App Store"
  - "Google Play"
---

## Direct definition

App store metadata is the set of text fields that describe an app inside a store listing: on the App Store, the title (30 characters), subtitle (30), keyword field (100, hidden), description, promotional text (170, updatable without review), and What's New notes; on Google Play, the title (30), short description (80), and full description (4,000). Metadata is distinct from creative assets (icon, screenshots, video) and from operational fields (pricing, categories, age ratings), though all three ship together as a listing. The defining property of metadata is that it is simultaneously read by two audiences — store indexing systems that decide when the app appears, and humans who decide whether to install — and every field weighs those two audiences differently.

## Why it matters

Metadata is the smallest editable surface with the largest leverage in app-store performance: a few hundred characters determine which queries an app can rank for and what promise visitors evaluate. Because fields are indexed differently per store, the same strategy must be placed differently — which is why "copy the App Store text into Play" is a category of error, not a shortcut.

## Field map

| Field | Store | Indexed for search | Primary audience |
| --- | --- | --- | --- |
| Title | Both | Yes, heavily | Both — ranking and first impression |
| Subtitle / short description | App Store / Play | Yes | Both |
| Keyword field | App Store only | Yes, hidden | Index only |
| Full description | Play indexed; App Store effectively not | Differs by store | Humans on App Store; both on Play |
| Promotional text | App Store | No | Humans only |

## Signs metadata is being managed

- Every target keyword has one assigned field, and no word repeats between title and subtitle.
- Claims in every field trace to features in the shipping build.
- Each locale's metadata was researched natively, not translated.
- Changes are versioned, with a recorded reason per change.

## What usually goes wrong

### One text serves two stores

Play's indexed description gets the App Store's conversion-only prose, or the App Store description gets Play's keyword-worked text — each optimized for the wrong reader.

### The hidden field mirrors the visible ones

Keyword-field characters spent on words already in the title or subtitle index nothing new and crowd out terms that would.

### Metadata means everything

When teams use "metadata" loosely for the entire listing, ownership blurs — screenshot problems get filed as metadata tasks and vice versa. Precise vocabulary keeps diagnosis and ownership clean.

## Operating rule

Metadata is managed when every field can answer two questions: which searches am I serving, and which claim am I making to the visitor who reads me? A field that answers neither is spending its characters on nothing.