Publishing a Squarespace site on Google Play
Squarespace sites are visually strong, which helps a listing, and Squarespace's paid features — Commerce, Member Areas, Scheduling — each interact with Google Play's rules in a specific way. Here is the map.
Payments
| Squarespace feature | In a Play-listed app |
|---|---|
| Commerce — physical products | Squarespace checkout allowed |
| Commerce — services and gift cards for physical goods | Allowed |
| Acuity Scheduling — appointments delivered in person or by video outside the app | Allowed |
| Member Areas / Digital Products — paid access to content viewed in the app (videos, courses, downloads) | Play Billing required — exclude from the app or don't list |
| Donations (Donation block) to a registered non-profit | Allowed |
| Restaurant menus with ordering via a third party (e.g. Toast link) | Allowed; opens externally or in-app |
Member Areas selling digital content is the one that catches Squarespace publishers. A photography site selling prints: fine. The same site selling a paid members-only tutorial library viewed in the app: Play Billing territory. Details in the payments guide.
Data safety on Squarespace
- Squarespace Analytics (always on) → App activity, device identifiers.
- Commerce checkout → Name, email, address, phone, purchases; financial info via Stripe/PayPal/Square.
- Member Areas → Name, email, login credentials.
- Forms and Newsletter blocks → Name, email, message content; shared with Mailchimp/Google Sheets if connected.
- Acuity → Name, email, phone, appointment details.
- Third-party code injection (Meta pixel, Hotjar, chat widgets) → whatever those collect; declare each.
- OneSignal push → Device identifier.
Squarespace provides a cookie banner and a privacy-policy page template. Extend the policy to name the Android app and push notifications; link it in the listing and the builder's About screen.
Passing minimum functionality
Squarespace portfolios and brochure sites are the hardest case: beautiful, static, and by default indistinguishable from a bookmark. What convinces a reviewer:
- Push notifications for new blog posts, appointment reminders (Acuity can trigger them via Zapier → OneSignal) or product drops.
- Offline screen — and, if your site is mostly images, make sure the offline state is not a blank white page.
- Native menu mirroring your navigation; pull to refresh; exit confirmation.
- A listing that explains why the app exists: "book, reschedule and get reminders" beats "our website as an app".
If the site genuinely has no recurring reason to open it, a Play listing may not be worth the review risk; the comparison discusses when a home-screen web app is the better answer.
Squarespace inside a WebView
- Announcement bar is sticky and expensive on a 360 px screen; hide it for mobile with CSS if it isn't essential.
- Video backgrounds often don't autoplay in WebViews and consume data; use a poster image on mobile.
- Cookie banner on first launch — fine, expected.
- Member login is separate from the phone's browser; users sign in once.
- Password-protected pages or a site-wide password during redesign: remove before submitting, or provide the password in the review notes under App access.
Listing assets
Squarespace sites photograph well: capture the home page, a gallery, a product or booking page, the menu, and a notification from the installed app. Export in the screenshot tool; the 1024×500 feature graphic can reuse your hero image's colours.
Frequently asked questions
Can I sell Squarespace digital products in a Play app?
Not through Squarespace checkout — Play Billing is required for digital content consumed in the app. Physical products, services and gift cards for physical goods are fine.
Will Acuity Scheduling work inside the app?
Yes; it is a web flow and the booking is for a service delivered outside the app, which the payments policy permits.
My site is a portfolio with no shop. Will it pass review?
Only with genuine app behaviour added — push for new work, offline state, native navigation — and a listing that explains the purpose. A static portfolio with none of that is the textbook minimum-functionality rejection.