Social Publisher
Social Publisher helps site administrators publish WordPress content to supported social networks from the WordPress dashboard.
Connect provider accounts, write a custom message, choose destinations, attach or crop an image, and publish manually. The plugin also includes block editor options for auto-post related workflows.
Supported networks
- Bluesky
- Mastodon
- Tumblr
- Threads
- LinkedIn personal profiles
- Blogger
- Telegram
- Facebook Pages
Support depends on each provider’s account type, app permissions, API access, and review requirements. LinkedIn publishing in this release is limited to personal profiles.
External services
Social Publisher connects to external services only when a site administrator configures a provider, starts authorization, tests a connection, opens a supported public share action, or publishes content.
Provider credentials and tokens are stored locally in the WordPress database for the current site. Do not share them. Logs and UI messages are designed not to show full tokens, secrets, authorization codes, passwords, or bearer credentials.
No data is sent to a provider unless that integration is configured and used.
Bluesky
Uses Bluesky / AT Protocol at https://bsky.social/xrpc/ for authentication, media upload, and post creation. 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
Uses the administrator-selected public Mastodon server over HTTPS for OAuth/app registration, account validation, media upload/status checks, and publishing. 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/privacy: each instance publishes its own policies. Example: https://mastodon.social/terms and https://mastodon.social/privacy-policy
Tumblr
Uses https://www.tumblr.com/oauth/ and https://api.tumblr.com/v2/ for OAuth, blog validation, and publishing. 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
Uses Pinterest OAuth/API v5 at https://www.pinterest.com/oauth/, https://api.pinterest.com/v5/, and https://api-sandbox.pinterest.com/v5/ when sandbox mode is selected. 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
Uses Meta / Threads endpoints at https://threads.net/oauth/ and https://graph.threads.net/ for OAuth, token exchange/refresh, account validation, media containers, status checks, and publishing. 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/
Uses Meta / Instagram endpoints at https://www.instagram.com/oauth/, https://api.instagram.com/oauth/, and https://graph.instagram.com/ for OAuth, token exchange, account validation, media containers, and publishing when permissions allow it. 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/
Uses LinkedIn OAuth/API endpoints at https://www.linkedin.com/oauth/v2/ and https://api.linkedin.com/ for OAuth, personal profile detection, validation, image upload preparation/upload, and publishing to a personal profile. 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, business pages, and organization publishing are not documented as stable supported 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
Uses Google OAuth and Blogger API at https://accounts.google.com/o/oauth2/v2/auth, https://oauth2.googleapis.com/token, and https://www.googleapis.com/blogger/v3/ for OAuth, token refresh, blog selection, tests, and publishing. 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
Uses Telegram Bot API at https://api.telegram.org/ for bot/chat validation and publishing. 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
Uses Meta / Facebook endpoints at https://www.facebook.com/v20.0/dialog/oauth and https://graph.facebook.com/v20.0/ for OAuth, Page discovery, Page token resolution, tests, diagnostics, publishing, and the optional public Facebook share action. 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/