Google Play custom store listings: keywords, URLs and translations

Choose the audience before changing the listing

Custom listings can serve selected search terms, countries or audience segments, as well as visitors arriving through a custom URL. Country targeting and language are different decisions: a country can belong to one country-targeted custom listing at a time. Decide which route you need before adapting screenshots. For an asset comparison, use the separate store listing experiment workflow and its reported results.

Begin your launch record with one supported task and the people who need it. For a fictional hiking journal, recording a walk offline differs from sharing a live location. If live sharing is not released, it should not appear in the listing. Preserve the default assets and the reason for the custom version. A listing aimed at returning users may tell a different story from one aimed at first-time visitors; comparing their rates alone does not isolate the effect of the screenshots.

Select search keywords and review their variations

In the custom listing setup, choose Search keywords, select relevant terms and review the available variations before saving. Google allows selecting known traffic terms or searching for new ones. Record the selected bundle and its variations alongside the intended feature story. Selection is not proof of ranking or demand for a new phrase.

Use customer language to make a candidate list, then check what the current Play Console offers. Reject a variation if its meaning points to an unsupported task. Ask a local reviewer to explain what the wording communicates rather than approving it because it contains the target word. Our keyword research sheet records the phrase, feature and evidence source. Leave demand fields blank when no measured source exists. A clean list of candidates is preparation for the console decision, not a substitute for actual discovery data.

Verify the exact custom listing URL

A URL-targeted listing uses the Play app URL with its package id and a listing parameter, in the form https://play.google.com/store/apps/details?id=[packageName]&listing=[parameter]. Preserve the identifier selected in Play Console when copying the URL. Google requires a unique parameter across your custom listings. Do not treat a modified ordinary app link as evidence that a custom listing exists.

Test the public URL you intend to share after the listing is published. Record the device, account state and observed assets. Follow it from the actual page or document where you placed it, then check whether the parameter survives the journey. If the default screenshots appear, separate a missing parameter from an unpublished or mismatched listing. A URL that opens successfully can still show the wrong feature story. Keep the exact final URL in the launch record so another teammate can repeat the check.

Add translations and check the product journey

Custom store listings do not receive automatic translations. Choose their default language and add the translations the audience needs. Review name and description lengths using Google's current store field limits: 30 characters for the app name, 80 for the short description and 4,000 for the full description. The free metadata checker can count your entered drafts before you validate them in Play Console.

Review screenshots and app behavior in the same language as the listing. A translated promise does not make an untranslated product screen easier to use. On a supported device, attempt the advertised task using harmless sample data and record permission, account and paid boundaries. For the hiking journal example, check whether an offline entry can be found after reopening. Ask the reviewer what they expected, then compare that expectation with the observed result. Record the mismatch and an owner before broadening the audience.

Measure listing intent separately from completed acquisition

Google Play's current listing reports distinguish visitor interactions from completed acquisitions. Listing clicks indicate intent through actions such as Install, Open or Pre-register; the listing click-through rate uses its own visitor scope. Use the report's exact definitions and filters. Keep completed acquisition and later product use as separate outcomes, rather than presenting every listing click as a new installed customer.

Write the listing identifier, report name, period, source and audience filters beside every comparison. If the report lacks enough data for a useful breakdown, record the gap and revisit after the console updates. Do not invent a conversion benchmark to fill it. Our rate calculator can explain a ratio and percentage-point change using matching counts, but it cannot verify attribution or statistical confidence. Private feedback can investigate why someone misunderstood the page. Neither a small feedback round nor a custom listing's before-and-after chart proves an asset caused growth.

Your next steps

• Choose a supported task, audience route and reason for a custom listing.
• Review selected keyword variations and language with the feature promise.
• Verify the published URL, translated assets and advertised first-session action.
• Save report definitions and matching filters; separate listing clicks from completed acquisitions.