Choose where the post should appear
Connect the LinkedIn destination before publishing
Set the destination and confirm that its connection can publish before WordPress sends a share.
1
Create the app and connection
Create the LinkedIn Developer App, grant the requested OAuth access, and establish the connection WordPress will use.
2
Select the publishing scope
Choose a personal profile, an organization page, or both. Set the member identity for a personal profile and the organization identity for an organization page.
3
Check target readiness
Confirm a valid token for each selected target. An organization page must be visible to the connection or have permission to share organically; selecting both requires both checks.
What happens at first publish
Let one eligible publish start the share
The plugin waits for the qualifying transition, then hands delivery to WordPress background processing.
1
One qualifying first publish
When an enabled public post type changes to published for the first time, the plugin queues one LinkedIn share. Updates, disabled posts, and already shared posts are skipped.
2
A background handoff
A single WordPress background event carries the work after publication, and saved state shows whether the share is queued or retrying.
3
Bounded overlap and recovery
A five-minute lock reduces duplicate work for one post, while the retry path stops after four attempts.
4
The official delivery
The official LinkedIn Posts API receives the prepared text and image and creates the post for the selected personal profile, organization page, or both.
Choose the visual that travels
Give each LinkedIn share a defined image
One selection order determines which available image accompanies the outgoing share.
1
Featured image first
Use the post’s featured image when one is attached.
2
Then the first content image
If no featured image is available, use the first image in the article content.
3
Advance through the gallery
If both are empty, use the next configured gallery image. The gallery advances one position per post and wraps at the end.
4
Use the final fallbacks
If the gallery has nothing to supply, check the configured fallback and then the site logo.
Shape the outgoing commentary
Choose which post details LinkedIn receives
The configurable template lets the outgoing commentary carry the article’s identifying details.
Post title
Provides the headline field in the outgoing commentary.
Excerpt
Supplies the supporting passage below the headline.
Author name
Adds the credited author line when selected.
Source content limit
Clean source content is limited to about 2700 characters before the title and template are applied.
Read the saved state
Check delivery without changing it
WordPress administrators who can manage site options can use these read-only, non-destructive, idempotent checks.
Overall site status
See the plugin’s overall publishing state.
Status for one WordPress post
View the saved outcome for a single article when you need to inspect one share.
What the publishing path needs
Check the required connections and runtime
The first four dependencies are required for publishing. The final two add optional read-only diagnostics.
5.4 or later
WordPress 5.4 or laterProvides publishing hooks, the media library, settings, scheduled events, and post metadata.
7.4 or later
PHP 7.4 or laterRuns the plugin code.
Required for publishing
LinkedIn Developer AppProvides the application registration, credentials, and OAuth connection used to publish.
Required for publishing
LinkedIn Posts APIReceives the selected post text and image and creates the personal or organization post.
Optional for diagnostics
WordPress Abilities APIAdds the overall status and post-status checks when this native API is present.
Optional for MCP diagnostics
WordPress MCP AdapterExposes the registered read-only diagnostics to MCP clients.
Your next action
Put the publishing path on your WordPress site
Download the stable ZIP to add the WordPress to LinkedIn publishing path. After installation, enable the post types you want, select the target, and complete the OAuth connection so the next eligible first publish can create its share.