Yes, you can turn a Google Sites page into an Android app by wrapping its published URL in a WebView app. The site must be published as Public, because a Restricted site needs Google sign-in, and Google blocks that sign-in inside Android WebView. Edits you republish in Google Sites show up in the app without a new build.
How a Google Sites Android app works
A Google Sites Android app is a small Android package that opens your published site full-screen in a WebView, the browser component apps use to show web pages. Google Sites itself has no “export as app” option, so the app is a wrapper around the live page, not a copy of it.
Two things follow from that:
- Content stays live. You edit in Google Sites, click Publish, and the app shows the new version on its next load.
- No connection, no content. Nothing from your site ships in the package, so a user on a plane gets an error page. If you need pages that work offline, read what happens to a WebView app without internet.
Generic “website to app” guides mostly work here. They skip the three places a Google Site differs from a normal website: sharing settings, sign-in and domain control.
Step 1: Publish the site as Public
The app can only show a site that loads without a Google sign-in. In the Google Sites publishing help, you set this when sharing: next to “Published site”, pick Restricted or Public from the drop-down list.
Pick Public. Then open the published URL in a private browser window. If it asks for an account, the app will too.
To keep the site out of Google search, tick the option that asks search engines not to list it. Google’s help page calls this a request, not a guarantee.
Why Restricted Google Sites fail inside an app
A Restricted Google Site fails in an Android app because viewers must sign in to a Google Account, and Google refuses sign-in from embedded WebViews. The Google Developers Blog says embedded webviews that implement or extend Android WebView don’t comply with its secure browser policy. Those requests get a disallowed_useragent error.
Here’s how it usually goes. A teacher builds a class site on a school Google Workspace account, limits it to the school domain and wraps it as an app. Students tap the icon and get a “disallowed_useragent” error page. The same limit applies to sites set so that specific people can view when published.
No wrapper setting fixes this. For sign-in on Android, Google recommends Custom Tabs, which open a real Chrome tab. The full background is in why Google sign-in fails in a WebView and the disallowed_useragent error explained.
Embedded Google content is a separate problem. The AppSheet help page says apps that need sign-in can only be embedded in a Google Sites site and need third-party cookies enabled. Inside a wrapped app, assume any embed that asks for an account will not load.
Step 2: Decide on the URL (sites.google.com or a custom domain)
Use whichever published address works in a private browser window. Both the default sites.google.com address and a custom domain work in a WebView app.
A custom domain looks better in the app’s About screen and listing. Per the Google Sites custom domain help, only the site owner can connect one: Settings, Custom domains, Start setup, then add a TXT record from Google Search Console to your DNS and verify it. Changes can take up to 48 hours.
The same help page warns that features that depend on Google Account sign-in may break on a custom domain, and embedded Google Groups won’t render properly. A Public site of plain pages, text and images rarely hits either. Test the custom domain in a browser first, because changing the app’s start URL later means a new build.
Step 3: Build the APK and AAB
Any WebView wrapper takes three inputs: the start URL, an app name and an icon. With a browser-based builder:
- Paste the full HTTPS address of the published site.
- Set the app name, package name (for example
com.yourschool.classsite) and icon. - Build a signed APK and install it on a phone to test.
- On the phone, tap every menu item, embedded form and link.
- Build an AAB when you’re ready for Google Play.
WebToAPK Free does this in the browser with no account or watermark. It needs a complete HTTPS address, and generated apps require Android 8.0 or newer. The website to APK guide has the same steps. It can’t promise a site behaves as it does in Chrome: sign-in, downloads and permissions can differ in a WebView.
Back up the signing key. Every update to the app must be signed with it.
Why a Trusted Web Activity isn’t an option
A Trusted Web Activity, or TWA, shows a site in Chrome without the address bar, and it often feels closer to the browser than a WebView. It needs domain proof. The Chrome docs on Trusted Web Activities say each origin must be validated with Digital Asset Links at /.well-known/assetlinks.json on that domain. Without it, the user sees Custom Tab UI with a browser bar.
You can’t put files on sites.google.com, so that route is closed for the default address. A WebView wrapper has no such check. See what a Trusted Web Activity is if you later move to your own hosting.
Will Google Play accept a Google Sites app?
A Google Sites app can be published on Google Play, but approval isn’t automatic. An app that only repeats a simple website can be rejected for minimum functionality, so give it a reason to exist: a timetable, forms, or pages people check often. More on that in why Google Play rejects WebView apps.
My take: for a class, club or small team, skip the Play Store at first. Share the signed APK or a home-screen shortcut, and publish only once people actually use it.
The limit: you’re still running Google Sites, with Google’s layouts, its page speed and its embed rules. If you need sign-in, push notifications or offline pages, a wrapper won’t add them.
FAQ
Is there an official Google Sites Android app?
Google offers no button that exports a Google Sites page as an Android app. You build the app yourself by loading the published site’s URL in a WebView wrapper.
Can my Google Sites app be private to my school or company?
Not reliably. A Restricted site asks visitors to sign in with a Google Account, and Google blocks its sign-in page inside Android WebView with a disallowed_useragent error. Keep the app’s site Public, or share the site link instead of an app.
Do I need to rebuild the app when I edit my Google Site?
No. The app loads the live published site, so page edits appear after you republish in Google Sites. You only rebuild when the app name, icon or navigation changes.
Can I use a custom domain in the app?
Yes. Connect the domain in Google Sites settings, wait for it to work in a browser, then use the custom domain URL in the app. Google warns that features depending on Google Account sign-in may break on a custom domain.
Can I make a Trusted Web Activity from a Google Site?
Usually not. A Trusted Web Activity needs a Digital Asset Links file at /.well-known/assetlinks.json on the site’s domain, and you don’t control files on sites.google.com.
Sources
- Publish & share your site - Google Sites Help
- Use a custom domain for your site - Google Sites Help
- Publish sites to a specific audience in the new Google Sites - Workspace Updates
- Upcoming security changes to Google’s OAuth 2.0 authorization endpoint in embedded webviews - Google Developers Blog
- Multi-Origin Trusted Web Activities - Chrome for Developers
- Run an app in an iframe on a web site - AppSheet Help