Social Publisher by Calliope – Auto Post to 10+ Networks vs Auto-Publish to Google Business Profile (GMB Poster)

Social Publisher by Calliope helps WordPress administrators publish from one WordPress dashboard to 10 social networks in Free, with additional destinations available in Pro. Write the message once, choose the connected destinations, prepare an image, generate titles or captions with Gemini when you want help, and publish from WordPress. The plugin keeps each network connection in its own setup screen, shows clear connected/disconnected states, and keeps provider messages available in Logs when something needs attention. What you can do in Free Publish manually from the dedicated Publisher tab in Social Publisher. Publish to multiple connected destinations in one run. Use a clean Publisher screen for title, content, link, hashtags, image, alt text, and destination selection. Use the built-in image workflow with Original, square, portrait, and landscape formats. Connect networks from dedicated setup panels with quick guides, OAuth actions, tests, and disconnect controls. Use the optional Gemini-powered AI composer to generate titles, captions, hashtags, or a complete post. Search WordPress posts, pages, and WooCommerce products to use as AI context. Read, copy, export, and clear sanitized Logs. Use a dedicated History tab with permanent destination-by-destination records, search, network/status filters, WordPress source links, account details, media/AI/source badges, provider results, errors, detail panels, and pagination. Use Settings for AI keys, model/language preferences, UTM tracking, failure-only email alerts, and plugin data cleanup behavior. Free network destinations Social Publisher Free includes connection and publishing support for: Bluesky Mastodon Tumblr Pinterest Threads Instagram LinkedIn personal profiles Blogger Telegram Facebook Pages Support depends on each provider’s account type, API permissions, app review status, and platform rules. LinkedIn publishing in this Free release is limited to personal profiles. Optional Pro destinations Social Publisher Pro adds these destinations to the same publishing workflow: YouTube / Shorts Discord Remote WordPress Custom Webhook Pro availability, account permissions, privacy options, and media support depend on each provider’s API rules. When Social Publisher Pro supplies a Multiple images / Carousel payload, compatible clients publish the full media set where the provider supports it, including Facebook Pages, Bluesky, Instagram, Threads, Blogger, and Telegram albums. AI generation The AI composer is included in the Free plugin. It uses your own Gemini API key, saved locally in your WordPress database. AI runs only when an administrator clicks an AI generation button. You can: Generate a title. Generate post content. Generate hashtags. Generate a complete social post. Add a private prompt for the current publication. Use WordPress content search as factual context. Choose the Gemini model and default generation language in Settings. Gemini is optional. Social Publisher can connect networks, publish posts, and show logs without a Gemini API key. Professional workflow Open Connections and configure one network. Test the connection or complete OAuth when the network provides it. Open Settings and connect AI if you want Gemini generation. Open Publisher, write or generate the content, prepare media, and choose connected destinations. Publish, then review Logs for provider responses and diagnostics. Platform-specific connection tutorials and video guides are maintained on the CalliopeWP website so setup instructions can stay current without waiting for a plugin release. Visit: https://calliopewp.com/calliope-social-publisher/ Privacy and local storage Provider credentials and tokens are stored locally in the WordPress database for the current site. Do not share them. Logs and admin messages are designed not to expose full tokens, secrets, authorization codes, passwords, bearer credentials, or API keys. Social Publisher does not track visitors, does not send telemetry, does not display advertising, does not add automatic credits, does not call provider APIs on normal admin page load, and does not execute remote code. Deleting the plugin preserves saved data by default. If you want WordPress to remove Social Publisher data when the plugin is deleted, enable the cleanup option in Settings before deleting the plugin. External services Social Publisher connects to external services only when a site administrator configures a provider, starts authorization, tests a connection, opens a supported share action, requests AI generation, or publishes content. No data is sent to a provider unless that integration is configured and used. Google Gemini / Google AI Used only when a site administrator saves a Gemini API key and clicks an AI generation button. Endpoint: https://generativelanguage.googleapis.com/ Data may include the selected Gemini model, site name, default generation language, current title, content, link, hashtags, selected WordPress post/page/product context, per-publication AI prompt, and requested generation field. The Gemini API key is stored locally in the WordPress database. Google APIs Terms of Service: https://developers.google.com/terms Google Privacy Policy: https://policies.google.com/privacy Gemini API documentation: https://ai.google.dev/gemini-api/docs Bluesky Used for authentication, media upload, and post creation. Endpoint: https://bsky.social/xrpc/ Data may include the configured handle, app password, post text, link, optional image/media data, and account identifiers. Terms: https://bsky.social/about/support/tos Privacy policy: https://bsky.social/about/support/privacy-policy Mastodon Used for OAuth/app registration, account validation, media upload/status checks, and publishing on the administrator-selected Mastodon instance. Endpoint: the selected public HTTPS Mastodon server. Data may include the instance host, callback details, OAuth app data, authorization code, client credentials, access token, status text, link, visibility, and optional media files. Localhost, private/reserved IPs, ambiguous hosts, and non-HTTPS instance URLs are rejected. Terms and privacy policies are published by each Mastodon instance. Examples: https://mastodon.social/terms https://mastodon.social/privacy-policy Tumblr Used for OAuth, blog validation, and publishing. Endpoints: https://www.tumblr.com/oauth/ https://api.tumblr.com/v2/ Data may include Consumer Key/Secret, OAuth verifier/callback data, token/secret, blog identifier, title/text, link, tags, and optional media data. Terms: https://www.tumblr.com/policy/en/terms-of-service Privacy policy: https://www.tumblr.com/privacy/en Pinterest Used for OAuth, board selection, sandbox or production validation, and Pin publishing. Endpoints: https://api.pinterest.com/v5/ https://api-sandbox.pinterest.com/v5/ Data may include App ID/Secret, callback URL, authorization code, requested scopes, token data, Pin title/description, destination link, selected board, and optional image URL/media data. Terms: https://policy.pinterest.com/en/terms-of-service Developer/API terms: https://developers.pinterest.com/terms/ Privacy policy: https://policy.pinterest.com/en/privacy-policy Threads Used for OAuth, token exchange/refresh, account validation, media containers, status checks, and publishing. Endpoints: https://threads.net/oauth/ https://graph.threads.net/ Data may include App ID/Secret, callback URL, authorization code, scopes, access token data, post text, link, media URL/data, container IDs, and account identifier. Meta Platform Terms: https://developers.facebook.com/terms/dfc_platform_terms/ Threads API documentation: https://developers.facebook.com/docs/threads/ Meta Privacy Policy: https://www.facebook.com/privacy/policy/ Instagram Used for OAuth, token exchange, account validation, media containers, and publishing when permissions allow it. Endpoints: https://www.instagram.com/oauth/ https://api.instagram.com/oauth/ https://graph.instagram.com/ Data may include Client/App ID/Secret, callback URL, authorization code, scopes, token data, caption/text, link when supported, media URL/data, container IDs, and account identifier. Meta Platform Terms: https://developers.facebook.com/terms/dfc_platform_terms/ Meta Privacy Policy: https://www.facebook.com/privacy/policy/ LinkedIn Used for OAuth, personal profile detection, validation, image upload preparation/upload, and publishing to a personal profile. Endpoints: https://www.linkedin.com/oauth/v2/ https://api.linkedin.com/ Data may include Client ID/Secret, callback URL, authorization code, member scopes, token data, personal profile author URN, post text, link, optional image data, upload URL data, and access token. Company pages and organization publishing are not documented as stable Free destinations in this release. User Agreement: https://www.linkedin.com/legal/user-agreement API Terms of Use: https://legal.linkedin.com/api-terms-of-use Privacy policy: https://www.linkedin.com/legal/privacy-policy Blogger / Google Used for OAuth, token refresh, blog selection, tests, and publishing to Blogger. Endpoints: https://accounts.google.com/o/oauth2/v2/auth https://oauth2.googleapis.com/token https://www.googleapis.com/blogger/v3/ Data may include Client ID/Secret, callback URL, authorization code, Blogger scopes, refresh/access token data, blog ID, post title/content, and labels when used. Google APIs Terms of Service: https://developers.google.com/terms Google Terms of Service: https://policies.google.com/terms Google Privacy Policy: https://policies.google.com/privacy Telegram Used for bot/chat validation and publishing. Endpoint: https://api.telegram.org/ Data may include Bot Token, chat ID, optional message thread/topic ID, post title/text, link, hashtags, and optional image URL/media data. Terms: https://telegram.org/tos Bot API documentation: https://core.telegram.org/bots/api Privacy policy: https://telegram.org/privacy Facebook Pages Used for OAuth, Page discovery, Page token resolution, tests, diagnostics, publishing, and the optional public Facebook share action. Endpoints: https://www.facebook.com/v20.0/dialog/oauth https://graph.facebook.com/v20.0/ Data may include App ID/Secret, callback URL, authorization code, scopes, token data, Page identifiers/names, selected Page token, post message, link, optional media data, and the Page URL when using the public share action. Meta Platform Terms: https://developers.facebook.com/terms/dfc_platform_terms/ Meta Privacy Policy: https://www.facebook.com/privacy/policy/

GMB Poster turns your WordPress posts into a steady stream of Google Business Profile (GBP) updates. New posts join a queue, the scheduler picks a slot from your cadence, and at slot time GMB Poster either: Auto-publishes the post directly to your GBP location via the official Google Business Profile API (v2.0+), or Prepares the caption, image and tracked link and hands it off to you for a one-click publish in the GBP web interface (the original semi-manual mode). You pick the mode in Settings. You can switch any time. Auto-publish (recommended, v2.0+) Create a free Google Cloud project, enable the My Business APIs, paste your OAuth Client ID + Secret into GMB Poster Settings. (Step-by-step guide is built into the setup wizard.) Click Connect Google account — Google’s consent screen opens, you pick the Google account that manages your GBP, click Allow. Pick your GBP location from the dropdown. Flip the Auto-publish toggle on. From then on, every time a queued post hits its scheduled slot, GMB Poster posts it directly to your GBP location automatically. Posted items show a green “Posted” pill and the Google post ID. Failed items show a red “Failed” pill with the Google API error and a one-click Retry publish button. Why “per-install” OAuth credentials? GMB Poster never embeds a shared Google client — that would leak the same OAuth secret to every installation of the plugin on WP.org and risk Google revoking it for everyone. Instead, each install uses its own free Google Cloud project; the OAuth Client Secret and the refresh token are stored encrypted-at-rest in your WordPress database using a key derived from your site’s AUTH_KEY constant. Semi-manual mode (original) If you don’t want to set up a Google Cloud project, the original semi-manual handoff still works: New WordPress posts are added to the GMB Poster queue automatically (configurable per post type and category). The scheduler picks a posting slot using either time-of-day slots or a cooldown window. When a slot is due, the next item appears in your Dashboard widget and on the GMB Poster Queue screen. Click Prepare & open GBP. GMB Poster: copies the formatted caption to your clipboard, downloads the featured image to your computer, opens your GBP composer in a new browser tab. In GBP: paste the caption, drop in the image, set the call-to-action, click Publish. Click Mark posted back in WordPress. Features Auto-publish to Google Business Profile via the official Google API (v2.0+), with a built-in setup wizard Per-install OAuth 2.0 credentials — your secret + refresh token are encrypted at rest in your WordPress database Semi-manual mode preserved as a fallback for installs that don’t want a Google Cloud project Custom queue with statuses: Pending → Ready → Prepared → Posted (or Skipped / Failed) Time-of-day slots OR cooldown-hours cadence, with optional weekend skipping Auto-queue on publish, filterable by post type and category Per-post opt-out checkbox in the editor sidebar Dashboard widget showing the next item ready to send “Publish now” / “Retry publish” buttons per row when auto-publish is on UTM-tagged Learn-more links (utm_source / medium / campaign configurable) Featured image → GBP image, title + excerpt → caption, permalink → call-to-action Translation-ready Disclaimer This plugin is not affiliated with, endorsed by, or sponsored by Google LLC. “Google” and “Google Business Profile” are trademarks of Google LLC. External services GMB Poster communicates with the official Google Business Profile API when (and only when) you’ve connected a Google account and turned on Auto-publish: Google OAuth 2.0 (https://accounts.google.com/o/oauth2/v2/auth, https://oauth2.googleapis.com/token, https://oauth2.googleapis.com/revoke) — used to obtain, refresh and revoke the access token GMB Poster uses on your behalf. My Business Account Management API (https://mybusinessaccountmanagement.googleapis.com/) — to list the GBP accounts your Google login can manage. My Business Business Information API (https://mybusinessbusinessinformation.googleapis.com/) — to list the locations under each account so you can pick one. Google My Business API v4 (https://mybusiness.googleapis.com/) — to create local posts on the location you selected. This is the actual “publish” call. When and what is sent: * The OAuth handshake sends nothing about your WordPress posts — only your chosen Google account’s permission to act on its behalf. * For each post we publish on your behalf, we send the caption text, the URL of your featured image, the call-to-action button text + URL, and the post’s language code. We do not send any visitor data, analytics, or anything else. If you do not connect a Google account, GMB Poster never contacts Google. The semi-manual mode opens GBP in your browser as a normal page navigation (your browser, your session — exactly as if you had clicked a regular link). Google’s terms of service: https://policies.google.com/terms Google’s privacy policy: https://policies.google.com/privacy