Connection prerequisites
Make the connection ready
Choose the account scope, then give each selected target the authorization it needs.
1
Start with authorization
Create the LinkedIn Developer App in LinkedIn’s developer console and grant the requested OAuth access.
2
Set the member identity
For a personal profile, select the member identity that should appear as the author and confirm the connection has a valid token.
3
Authorize the organization destination
For an organization page, select its identity and confirm that the connection can see it or has permission to share organically. Selecting both targets requires both checks.
When a post goes live
When the queue may begin
Use these rules to predict what enters delivery.
1
The first qualifying transition
A first publish of an enabled public post type queues one LinkedIn share. Updates, disabled posts, and already shared posts do not create another queue entry.
2
Outside the publish request
A single WordPress background event carries the work after publication. The stored state reports queued or retrying while the handoff continues.
3
Protection against overlap
A five-minute lock reduces simultaneous work for one post. The retry path stops after four attempts.
4
Send the prepared material
The official LinkedIn Posts API receives the prepared text and image, then creates the publication for the chosen target or targets.
The visual sent with the share
Choose the LinkedIn visual
One configured selection order determines which image travels with each LinkedIn share.
1
Use the featured image
Start with the visual attached as the post’s featured media.
2
Fall back to article media
If no featured media is available, use the first content image instead.
3
Advance the gallery
When the earlier choices are empty, take the next item from the configured gallery. Rotation moves one position per post and wraps at the end.
4
Use the final fallback
If the gallery has nothing to supply, check the configured backup and then the site logo.
Post composition
Shape the LinkedIn commentary from your post
Three source fields can shape the commentary, with a separate limit on imported text.
Post title
Feeds 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.
Optional diagnostics
Optional status visibility
WordPress administrators with the manage options permission can use these optional checks. They are read-only, non-destructive, and idempotent.
Overall site status (linkedin-autoposter/get-status)
See the plugin’s overall publishing state.
One WordPress post (linkedin-autoposter/get-post-status)
View the saved outcome for a single article.
What publishing requires
Dependencies
The first four dependencies are required for publishing. The final two are optional and support 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 AppSupplies the application registration used by the LinkedIn connection.
Required for publishing
LinkedIn Posts APIProvides the remote endpoint for delivery.
Optional for diagnostics
WordPress Abilities APIAdds the 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 step
Download the plugin when your target is ready
Use the stable download to add an automatic publishing path to WordPress. After installation, enable the post types you want in that path, then connect the target you selected.