Publishing a Blogger blog on Google Play

Content policies for a publication

A blog app inherits Play's content policies for everything it displays:

• Your posts must meet Play's restricted-content rules (no hate speech, sexual content, dangerous products, etc.) — the same rules Blogger already applies, roughly, but Play enforces them on the app.
• Comments are user-generated content. Play's UGC policy requires a way to report and block, and moderation. Blogger's comment moderation and its report link satisfy this if you moderate; if you don't want the obligation, disable comments in the app-visible template.
• Content rating: answer the IARC questionnaire for the blog's actual content, including comments. A cooking blog is "Everyone"; a true-crime blog is not. The rating guide walks through it.

Is your blog a "news app"?

Play's News policy applies to apps that describe themselves as news or are primarily news, and requires them to disclose ownership, provide contact details, and not primarily republish others' content. A personal or niche blog that doesn't call itself news is outside it. If your blog covers current events and you'd label it news, comply: an About page naming the owner, a contact page, original reporting or clearly attributed sources.

Ads: AdSense on the pages, AdMob in the app — not both

Most Blogger sites run AdSense. Those ads render inside the app because the app shows the live pages. Google's policies prohibit displaying AdSense and AdMob on the same screen and AdSense's program policies restrict serving inside apps except through approved integration; in practice:

• Simplest compliant setup: keep AdSense on the pages, leave AdMob off in the builder, declare "contains ads".
• Alternative: hide AdSense units when the visitor is your app (the builder's WebView sends an identifiable user-agent string you can check in the template) and run AdMob banners from the app shell.
• Never stack both, and never place a banner where the back gesture or a menu tap lands on it — accidental clicks are an AdMob policy violation.

Push for new posts

Enable OneSignal in the builder. In OneSignal, create an RSS-to-push automation on https://yourblog.blogspot.com/feeds/posts/default (or your custom domain's feed). Every publish becomes a notification, deep-linked to the post. Keep the frequency to what you publish; a daily blog should batch to a digest.

Data safety for a Blogger site

• Blogger stats / Google Analytics → App activity, identifiers.
• AdSense → Advertising identifiers, collected by Google.
• Comments → Name, email (Google account), content.
• Follow-by-email / newsletter widgets → Email.
• OneSignal push → Device identifier.

Blogger doesn't give you a privacy policy page; add one as a static page and link it in the listing and the app's About screen. The guide has the sections Play looks for.

Blogger inside a WebView

• Mobile template: Blogger serves a mobile view by default (?m=1). Make sure your theme is responsive or the mobile template is enabled; the app always renders at phone width.
• Navbar: Blogger's top navbar (search, follow) looks out of place in an app; hide it in the template's layout settings.
• Custom domain: prefer one. The package name, listing and screenshots all reference the domain, and a blogspot.com address ties the app to Google's hosting forever.