Jetpack 15.6 is out, and it fixes a bottleneck I have complained about for years: the one-size-fits-all social sharing compromise. The Jetpack Social upgrade stops the lazy habit of blasting one caption at every network and gives you real control over what each audience sees.
Before this, wanting a long professional update on LinkedIn and a punchy, hashtag-heavy line on X (formerly Twitter) meant either doing it by hand or paying for a heavy third-party SaaS tool. The editor sidebar now lets you set the message, the image and the formatting per platform before you publish. That is closer to a refactor of how WordPress talks to the rest of the web than a quality of life tweak.
What per-platform customization changes
Jetpack’s handling of these connections was always efficient underneath. The interface was the weak part. The Jetpack Social upgrade ships a rebuilt preview modal that is accurate, and after years of broken link previews, a reliable render of a Tumblr or Threads post before it goes live is worth a lot on client sites.
Accessibility got attention too. The modal is now shared with Jetpack SEO, so you can audit search and social presence in one view instead of switching between five panels just to confirm a post looks right. That saves real time when you are running sites for other people.
If you are working on mobile publishing, my take on whether the Jetpack mobile app is a serious tool is related reading, because these social features keep moving onto the phone.
Filtering what actually gets shared
One gotcha with automated sharing is that you don’t always want every post type flying out to social media. Even with the new Jetpack Social upgrade features, there are custom post types and conditions where you want sharing switched off in code so the feeds stay clean.
Hoping your editors remember to uncheck the boxes in the sidebar is not a plan. Use the publicize_should_publicize_published_post hook and the decision lives in code where you can see it.
/**
* Filter to prevent specific post types from being shared via Jetpack Social.
* Use this to ensure internal-only post types don't accidentally leak.
*/
add_filter( 'publicize_should_publicize_published_post', 'bbioon_limit_social_sharing', 10, 2 );
function bbioon_limit_social_sharing( $should_publicize, $post ) {
// Only allow sharing for standard 'post' and 'product' types
$allowed_post_types = array( 'post', 'product' );
if ( ! in_array( $post->post_type, $allowed_post_types ) ) {
return false;
}
// Example: Don't share if a specific category is assigned
if ( has_category( 'internal-news', $post->ID ) ) {
return false;
}
return $should_publicize;
}AI image generation and workflow cleanup
Jetpack AI is now wired into the social image picker, so you can generate images from your post’s brand and style without leaving the editor. I am usually skeptical of AI added for its own sake, but a quick generator for a one-off LinkedIn banner, on a project with no designer, is a legitimate efficiency gain.
The new Sharing Activity view merges history and scheduled posts into one screen. When a post fails to reach X, the log is sitting in the dashboard instead of buried in transients or database logs.
If the Jetpack Social work is eating your dev hours, I can take it over. I have been wrestling with WordPress since the 4.x days.
The pragmatic takeaway
The value here is that you stop compromising on content quality to fit one shared caption. Per-platform customization and a real sharing history make Jetpack Social something I can hand to a high-traffic client without caveats. The official Jetpack Developer Resources list the hooks if you are building on top of it.
