Publishing a Webflow site on Google Play
Webflow sites are usually marketing sites and CMS-driven publications — the category Google Play scrutinises hardest for "is this just a website?". This page is about clearing that bar honestly, plus the Webflow-specific declarations, and when a Trusted Web Activity is the better vehicle.
The minimum-functionality problem, specifically for marketing sites
Google's policy refuses apps whose "primary purpose is to drive affiliate traffic or that provide a webview of a website without offering additional functionality". A company homepage, a SaaS landing page, an agency portfolio: wrapped as-is, these are rejected, and rightly — nobody needs an app to read a pricing page once. What changes the answer is a recurring reason to open it plus app-only capability:
- A CMS blog or resource library people return to, with push notifications on publish (OneSignal RSS automation on the Webflow CMS RSS feed).
- A customer portal, docs or status page users check regularly.
- Offline access to reference content (the builder's offline screen plus the WebView's cache handles recently viewed pages).
- Native navigation to the sections that matter, pull to refresh, exit confirmation.
If your Webflow site is a single-purpose landing page and none of the above applies, the honest advice is not to list it; the comparison covers what to do instead. The policy guide quotes the rule and the successful patterns.
Payments: Webflow Ecommerce
| You sell | In a Play-listed app |
|---|---|
| Physical products | Webflow checkout (Stripe/PayPal) allowed |
| Services delivered outside the app | Allowed |
| Digital downloads, paid content viewed in the app, Memberships to gated content | Play Billing required — exclude from the app |
Data safety on Webflow
- Webflow site analytics (if enabled) and any Google Analytics / GTM in custom code → App activity, identifiers.
- Webflow Forms → Name, email, message; shared with the email recipient and any connected tool (Zapier, Make, HubSpot).
- Webflow Logic / Memberships (Users) → Name, email, credentials.
- Ecommerce → Name, address, phone, purchases; financial info via Stripe/PayPal.
- Chat/marketing scripts in custom code (Intercom, HubSpot, Meta pixel) → declare each.
- OneSignal push → Device identifier.
Webflow does not generate a privacy policy; you write one as a CMS page. The privacy policy guide gives a structure that satisfies Play.
Webflow inside a WebView
- Interactions and Lottie animations run fine but cost battery and data; consider reduced-motion variants for the app.
- Locales: Webflow Localization serves by path or subdomain; set the app's start URL to the default locale and let the site switch.
- Cookie consent (Finsweet, Cookiebot) appears on first launch.
- Custom domains with www: make the start URL the canonical one to avoid a redirect on launch.
The TWA alternative for Webflow
Because Webflow allows head code and (with a small proxy) root files, a Webflow site can be a proper progressive web app and be listed as a Trusted Web Activity — Google's designed route for web apps, which tends to be reviewed more favourably than a WebView. It is more setup and it requires the site to be a valid PWA. The sister site FreeWebToApp covers the Webflow PWA setup; the Play forms are identical and covered here.
Frequently asked questions
Will my Webflow marketing site be approved?
As a plain wrapper, probably not — it is the pattern the minimum-functionality policy targets. With a CMS section people return to, push notifications, offline handling and native navigation, marketing-led sites are approved regularly.
Do Webflow Forms create Data safety obligations?
Yes. A contact form collects name, email and message content and typically shares them with a third-party tool. Declare it.
WebView app or Trusted Web Activity for Webflow?
If you can host a manifest and service worker (Webflow allows it with a proxy), a TWA is the lower-risk listing. If you want the simplest path today, the WebView app with features enabled works.