OOmnistu

Blog / Monetization

Monetization

Google Play beyond the app: merchandising your catalog across search, web and Gemini

Google's 16 November 2026 post details Play Console's Merchandising and optimization workflow: featured products in search, cart-abandonment reminders, web store sales, purchase-flow recommendations, exclusion groups and Play Billing Lab simulation - with Google's own figures labeled.

OOmnistu
Reviewed 2026-11-19 · 5 min read

Google Play's pitch to developers has quietly changed shape. The store used to be the place users went to find your app; everything commercial happened inside it, at the paywall. A 16 November 2026 post on the Android Developers Blog describes the replacement: a catalog you configure once in Play Console, which Google then merchandises across search results, web pages, checkout flows and - in early pilots - Gemini conversations. Here is what Google actually announced, with its claims labeled as its claims.

The control panel: Merchandising and optimization

The operational center is the Merchandising and optimization page in Play Console, which pulls product selection, surface placement and eligibility rules into a single workflow - the pitch being that growth teams configure multi-surface exposure in minutes instead of coordinating separate tools. Google says more than 7,700 developers already use it, and offers one partner spotlight: MYBO Games saw a 60% increase in user spend outside their game through the new flow. Both numbers are Google's own, published in its blog post, and the screenshots in the post are marked as simulated. Treat them as directional evidence that the feature is live and in use, not as benchmarks for your app.

Where the catalog can appear

The post enumerates the surfaces, and the list is the substance:

Google frames the split as acquisition for apps (introductory offers and trials on discovery surfaces, before the paywall) and re-engagement for games (promotional bundles, lapsed-player drops, web-exclusive packs). That is the vendor's framing, but it matches how the surfaces are shaped.

The guardrails are the interesting part

Putting your catalog on surfaces you do not control raises the obvious question - what stops discount cannibalization and grey-market resale - and the post answers it with platform-level controls, all configured in the same workflow:

Testing before exposure

Play Billing Lab now simulates the out-of-app purchase journeys: how featured products and abandonment reminders render on different screens, whether exclusion rules shield the right cohorts, and whether the entitlement is actually delivered. Given that these surfaces put prices and offers in front of users before any of your own code runs, simulating the journey before enabling a surface is close to mandatory.

What this means for a small team

The honest summary

Play is becoming a merchandising layer that follows your catalog across surfaces instead of a storefront users visit. The machinery - one Play Console workflow, named surfaces, real guardrails, a simulator - is documented and live; the headline numbers are vendor figures, and the Gemini piece is a pilot. The sensible response is small: pick one surface, set your exclusion rules first, simulate it, and read your own reports.

Sources

Prepared with AI assistance and reviewed before publication. Surfaces, controls and testing capabilities are drawn from the Android Developers Blog post above, checked on 19 November 2026; adoption and case-study figures in that post are Google's own and are attributed as such.