App Store Screenshot SEO: Does Caption Text Rank?

App Store screenshot SEO is the practice of writing your real keywords into screenshot captions so they reinforce the rest of your metadata. The honest 2026 status: in mid-2025 practitioners reported that Apple started reading caption text as a secondary keyword input [1], but Apple has not confirmed it, and a controlled test found weak evidence [2]. Align your captions anyway. The cost is near zero and aligned captions convert better regardless.

That gap between a loud claim and thin proof is the whole story here. This guide separates what is actually known from what is inferred, then gives you a strategy that pays off whether or not the ranking signal is real, so you are not betting your visibility on an unconfirmed change.

TL;DR:

• The claim: in mid-2025 Appfigures reported Apple began reading screenshot caption text and treating it as keyword metadata, separate from your title, subtitle, and keyword field [1].
• The counter-evidence: ConsultMyApp tested 64 screenshot phrases across 8 apps. 36 did not rank, 27 were explained by existing metadata, and just 1 was an unexplained anomaly. Their verdict: "no strong evidence" [2].
• Apple's position: no confirmation that screenshot text is a ranking factor. Treat it as a probable but secondary and unconfirmed signal.
• Why align captions anyway: the first one to three screenshots appear in search results [3], so caption text earns its keyword alignment on conversion grounds alone, with any ranking lift as a bonus.
• What you can write: feature phrases that match real search terms, not prices or "% off" (guideline 2.3.7 keeps those out of screenshots) [4], and not stuffed keyword lists.
• Where your bets belong: title, subtitle, and keyword field stay the load-bearing fields. Captions reinforce them, they do not replace them.

Table of Contents

• Does Apple actually rank the text in your screenshots?
• What does the mixed evidence mean for your strategy?
• What words can you put in a screenshot caption?
• Where do captions fit in the rest of your metadata?
• How do you find the keywords worth putting in captions?
• How do you make caption text readable to people and parsers?
• How do you test whether caption keywords moved your rank?
• Align captions, bet on the confirmed fields

Does Apple actually rank the text in your screenshots?

Probably, weakly, and unconfirmed. In June 2025 Appfigures reported that "Apple is now extracting text from your app's screenshot captions and treating that text as part of your keyword metadata" [1]. The same analysis labels part of its own reasoning as speculation, Apple has never confirmed the behavior, and an independent test found almost no ranking effect [2].

Here is the evidence laid side by side, because most posts quote only the half that sells the headline.

On the claim side, Appfigures argued that screenshot keywords "don't compete with keywords from the name, subtitle, or keyword list" [1], meaning a caption term would be additive rather than redundant. That is the optimistic reading, and the author is candid that it is an inference, not a confirmed mechanism.

On the skeptical side, ConsultMyApp ran the closest thing to a controlled test: 64 screenshot-derived phrases across 8 leading apps. Of those, 36 did not rank at all, 27 were already explained by the app's existing title, subtitle, or keyword field, and exactly 1 was an unexplained anomaly. Their conclusion was blunt: "there is no strong evidence Apple is broadly indexing screenshot titles" [2]. Something did shift in the App Store around mid-2025, but the caption-text explanation for it is inferred and, when tested, faint.

What does the mixed evidence mean for your strategy?

Align your screenshot captions with real keywords, then keep your actual ASO effort on the fields Apple confirms it ranks. Caption alignment is low-cost insurance: if the signal is real you gain a little, and if it is not you have lost nothing, because keyword-aligned captions also convert better with human readers.

The logic is an asymmetry. The cost of writing a caption as "Track Marathon Training" instead of "Reach Your Goals" is zero, you were going to write a caption either way. The potential upside is a secondary ranking nudge plus a clearer message to the human who is deciding whether to tap Get. The downside of getting it wrong is also zero. When a bet is free on the cost side and positive on the upside, you take it, you just do not reallocate budget to it.

Where this turns genuinely additive is net-new terms. Because Appfigures reports screenshot keywords sit separate from the keyword field [1], a caption can carry a phrase you could not fit into the 100-character keyword field. That is the one play worth a small, measured experiment: park a candidate term in a caption that lives nowhere else in your metadata, then watch whether it ranks. For the full picture of where screenshots sit among everything Apple weights, the App Store ranking factors guide ranks the signals by real impact.

What words can you put in a screenshot caption?

Short feature phrases that match how users actually search, written in natural language. Apple guideline 2.3.7 keeps prices, discounts, and terms "not specific to the metadata type" out of screenshots [4], and a keyword-stuffed comma list reads as spam to both a human and any text parser. The working rule: one clear phrase per frame.

A few concrete do-and-don't pairs:

• Do: "Track Your Marathon Training." Don't: "Run, Jog, Sprint, Cardio, Marathon." The list looks spammy and dilutes the message.
• Do: "Plan Every Meal for the Week." Don't: "The Best Meal App." Adjectives like "best" and "easy" carry no search volume and waste the most valuable pixels on the page.
• Do: match the caption to the subtitle. If your subtitle is "Daily Hydration Tracker," frame 1 can read "Track Daily Water Intake," reinforcing the same intent for the reader.

Whatever you write, keep the offer out of it. Holiday discounts, trial pricing, and "sale ends Sunday" belong in promotional text or an in-app event, not in the screenshot itself, per the same guideline [4].

Where do captions fit in the rest of your metadata?

Underneath the fields that definitely rank. Your app name, subtitle, and keyword field are the confirmed inputs, and captions are reinforcement on top of them. Because screenshot keywords appear to sit separate from the keyword field [1], a caption can hold one net-new term you could not otherwise fit, which is the only genuinely additive role.

Think of it as a hierarchy of confidence. The name and subtitle are indexed and visible. The keyword field is indexed and hidden. The caption is, at best, a weak and unconfirmed extra surface. You build from the bottom of that confidence stack up: get the confirmed fields right first, then let captions echo your strongest terms and carry one experiment. The free App Store indexed fields map we maintain lays out which fields Apple indexes and how much each holds, so you can see exactly where a caption term adds something the keyword field cannot.

How do you find the keywords worth putting in captions?

Run a real keyword research pass: pull candidate terms, score them by search volume and relevance, and assign one per frame. The short version is to start from phrases users actually type, never from adjectives. That research has its own dedicated workflow rather than living in this overview.

The full process, from seeding candidates to scoring and mapping them onto frames, is in the 6-step screenshot keyword research workflow. For the tooling, the free ASO keyword researcher surfaces high-volume targets, and the free screenshot copy generator drafts caption lines from a keyword list so you are not staring at a blank frame.

How do you make caption text readable to people and parsers?

Whatever reads the text, a person scanning the search results or Apple's text recognition, needs clean letterforms: high contrast, a legible size, and no heavy shadows or glow effects laid over busy UI. The honest test still holds: if a human has to squint, a parser will miss it too.

That is the short version, because the mechanism has its own deep-dive. How Apple's text recognition extracts caption text, which areas of the frame it appears to read, and the exact contrast and sizing choices that survive extraction are covered in how Apple reads the text in your screenshots. Design for that legibility once and both audiences, human and machine, benefit.

How do you test whether caption keywords moved your rank?

Pick a term you added only to a caption, record its current rank, ship the change, then watch that specific keyword over the next few weeks. If it does not move, the signal was weak for your app, which is exactly what the mixed evidence predicts for most terms [2]. Measure per keyword, not in aggregate, or you will never see the effect.

Treat each caption keyword as a small experiment rather than a guaranteed win. Run the check on your normal refresh cadence so you are not constantly resubmitting, and keep the term in only if it earns its place. Because the first one to three screenshots already appear in search results [3], the caption is doing conversion work the whole time regardless of whether the ranking needle moves, so a flat ranking result is not a failed change.

Align captions, bet on the confirmed fields

The defensible 2026 position on App Store screenshot SEO is the boring one: align your captions with real keywords because it is free and it helps conversion, treat any ranking lift as an unconfirmed bonus, and keep your real optimization effort on the title, subtitle, and keyword field. The loud version of this advice oversells a change Apple never confirmed and one controlled test could barely find.

From there it is an iteration loop. Draft and refine caption copy in the screenshot builder, research the terms with the 6-step keyword workflow, check legibility against how Apple reads screenshot text, and place it all in context with the ranking factors guide.