Skip to main content
There is no SEO for a native app. Nothing crawls it, robots.txt means nothing, and Open Graph tags never leave the web. What ranks an app is its store listing — a fixed set of short text fields and a set of images, all typed into App Store Connect and Play Console by hand. Vibely builds and submits the app. The listing is yours to write, and it is the half that decides whether anyone sees it.
These fields are not in Vibely. They live in App Store Connect and Play Console, and the Play Developer API cannot create a store listing at all — see Ship → What still happens in Play Console. Do them once, before your first production release.
Store listing fields

​
The fields, and what they weigh

​
App Store (iOS)

Keyword field rules that cost real ranking:
  • Never repeat a word that is already in the name or subtitle. Apple indexes all three together; a repeat spends characters on nothing.
  • Skip plurals and your own brand name. Apple stems, and your brand already ranks.
  • Do not use the words “app”, “free”, or your category name.

​
Google Play (Android)

This is the single biggest difference between the two stores. Play indexes the full description; Apple does not. Do not paste the same text into both — on iOS the description is pure conversion copy, on Play it is conversion copy and your keyword surface.

​
Screenshots

Screenshots are the highest-leverage asset on either store. Most installs are decided in the gallery, before anyone reads a word. Apple requires one 6.7”-class iPhone set (1290×2796 portrait) and scales it down for smaller devices; if the app ships on iPad, that is a separate required set.
Exact accepted pixel dimensions change with each device generation. The upload screen in App Store Connect and Play Console is the authority — it rejects anything it will not take and names the size it wants.
Ordering rules, in both stores:
  1. First screenshot carries the pitch. Caption it. A bare UI screenshot wastes the only one most people see.
  2. One idea per screenshot, in the order a user would meet the features.
  3. Caption in the image, not in the description — the gallery is scrolled, not read.
  4. Localized screenshots outperform translated text over an English UI.
You can build these from the app: ask the agent for a screenshot layout, or run the app and capture the flows you want to sell.

​
What moves the needle, in order

  1. Title and subtitle / short description. Highest weight, 60 characters total on iOS. Rewrite these before anything else.
  2. First two screenshots. The conversion step everything else feeds.
  3. iOS keyword field. 100 characters, all of them earning.
  4. Play full description. Indexed, so it is doing two jobs.
  5. Ratings and reviews. Both stores weight them heavily and neither lets you shortcut them. Prompt for a review after a success moment, never on launch.
  6. Install-to-retention. Play in particular demotes apps users uninstall quickly, so a listing that oversells is a listing that decays.

​
Changing a listing later

  • iOS: the name, subtitle, keywords and screenshots are locked to a version and change only through a review. Promotional text is the exception — it updates instantly. Plan around that.
  • Play: listing text can be edited at any time without a release, though substantial changes may go through a short review.
That asymmetry is worth exploiting: iterate copy on Play, measure, then carry the winner into the next iOS submission.

​
What Vibely does not do

No keyword volume data, no competitor tracking, no rank monitoring, and no automatic listing upload. Vibely builds the binary and drives the submission; the listing is manual on both stores.

Ship

Builds, TestFlight, Play tracks and submission

SEO and AI search

The web equivalent, for a published web app