WordPress LinkedIn automation
We Built a LinkedIn Auto-Posting Plugin Because the Others Were Terrible
We got tired of buggy, bloated LinkedIn auto-posting plugins. So we built our own - minimal, clean, and actually works.
Stop manually reposting every WordPress article to LinkedIn
Publishing a blog post should not start a second manual publishing routine. Copying the link, opening LinkedIn, writing the update, pasting the URL, and doing it again after every article gets old fast.
We looked for a WordPress plugin to automate that job and found a market full of bloat, brittle login tricks, abandoned code, and plugins that reposted the same article every time a typo was fixed. So we built a smaller tool that does one job: share a post to LinkedIn when it is first published.
The decision is not just whether to automate. It is whether the automation stays clean.
- Will it post once on publish without spamming followers after normal edits?
- Does it use LinkedIn’s official API instead of simulated browser logins that trigger checkpoints?
- Can an editor understand and control it without buying into a bloated plugin stack?
The LinkedIn auto-post plugin problem
Most LinkedIn auto-posting plugins we found fell into one of three categories. Each category creates a different kind of operational pain for a WordPress publisher.
The bloated ones
These plugins bundle dozens of features you do not need, put upsells throughout the workflow, and often make the paid version cost more than the hosting plan that runs the site.
The broken ones
Some tools try to simulate browser logins instead of using proper authorization. LinkedIn detects the behavior, flags the connection as suspicious, and the publisher gets checkpoint or connection errors instead of a shared post.
The abandoned ones
Others look frozen in time: last updated years ago, tested against old WordPress versions, and risky to trust on a current publishing workflow. One plugin we tried reposted articles every time we fixed a typo, which meant followers saw the same article five times.
Introducing Devenia LinkedIn Autoposter
Devenia LinkedIn Autoposter is a WordPress plugin built around one clear promise: automatically share a post to LinkedIn when it is first published.
There is no premium tier, no upsell path, and no attempt to turn a simple publishing task into a complicated marketing suite. The plugin exists because the available options either did not work reliably or came with baggage we did not want.
What the plugin actually does
- Uses the official LinkedIn API with OAuth 2.0, not scraping or simulated browser logins.
- Posts only on first publish, not when an editor updates the article or fixes a typo.
- Gives per-post control so a specific article can be excluded before it is shared.
- Lets you customize the LinkedIn text with {title}, {excerpt}, {url}, and {author} template tags.
- Warns before LinkedIn’s access token expires, so the connection can be renewed before publishing stops.
How setup works
The setup is not hidden behind magic. LinkedIn requires an app connection, so the plugin walks through a practical configuration path: create the LinkedIn app, copy the credentials, add the redirect URL, and authorize WordPress.
- Create the LinkedIn app: Open the LinkedIn Developer Portal, create an app, add the basic details, and enable Share on LinkedIn plus Sign In with LinkedIn using OpenID Connect.
- Configure authentication: In the LinkedIn app’s Auth tab, copy the Client ID and Client Secret, then add the redirect URL shown in the WordPress plugin settings.
- Connect WordPress: Install and activate the plugin, go to Settings -> LinkedIn Autoposter, enter the Client ID and Secret, click Connect to LinkedIn, and authorize the app.
- Expected setup time: The original setup should take about ten minutes if the LinkedIn app details are ready and the redirect URL is copied exactly.
- Publishing behavior: After connection, a newly published WordPress post appears on LinkedIn automatically. Normal edits and typo fixes should not create repeat LinkedIn posts.
The workflow is still LinkedIn-aware, but it removes the repetitive copy-paste step from every article publish.
The honest tradeoff
This plugin keeps the WordPress side intentionally small, but LinkedIn still controls its own security rules. The most important rule is token expiry.
Why it is cleaner than the tools we tried
- It relies on official OAuth 2.0 access instead of login simulation.
- It avoids duplicate social posts when a published article is edited.
- It stays focused on one publishing action instead of adding dashboards, upsells, or unrelated marketing features.
What it cannot pretend away
- LinkedIn intentionally limits access tokens to about 60 days as a security policy.
- Every couple of months, an admin needs to click Reconnect to LinkedIn in the plugin settings.
- The reconnection takes roughly 30 seconds and the plugin warns ahead of expiry, but it is not truly set-and-forget forever.
How to know the plugin is doing its job
A LinkedIn autoposter should be judged by boring, observable behavior. If it works, publishing gets quieter rather than more complicated.
- A new WordPress post creates one LinkedIn share after first publish.
- Editing that same WordPress post later does not repost it to LinkedIn.
- The LinkedIn post uses the configured template fields for title, excerpt, URL, and author.
- A post can be excluded before publish when it should not appear on LinkedIn.
- The admin sees token-expiry warnings early enough to reconnect before the next publish depends on it.
- Source link preserved from the original article: LinkedIn Developer Portal at https://www.linkedin.com/developers/apps.
The plugin succeeds when it makes LinkedIn sharing predictable: one clean share, no accidental repeats, and no suspicious-login failures.
Frequently asked questions
Is this a full social media scheduling suite?
No. It is deliberately narrower. It shares WordPress posts to LinkedIn when they are first published and avoids the bloat that made other tools frustrating.
Does it use a safe LinkedIn connection method?
Yes. The plugin uses LinkedIn’s official API and OAuth 2.0. It does not scrape LinkedIn or pretend to be a browser login session.
Why does LinkedIn need reconnection after about 60 days?
That limit comes from LinkedIn’s token policy. The plugin cannot remove it, so it warns before expiry and makes reconnection a short settings action.
Get the plugin and stop repeating the same LinkedIn step
The plugin is available on GitHub for publishers who want a minimal WordPress-to-LinkedIn workflow without upsells or unnecessary moving parts.
- Download the plugin from GitHub and install it in WordPress.
- Create the LinkedIn app and add the required products and redirect URL.
- Connect the plugin with the Client ID and Client Secret, then authorize LinkedIn.
- Publish a post and confirm that LinkedIn receives exactly one clean share.
Questions or bug reports can go through GitHub issues or a direct message to Devenia.