Social Auto Poster (WPEka) is the publish-time social automation: every new post, page, or custom post type automatically shares to your connected networks — Facebook, X, LinkedIn, Instagram, Pinterest, Tumblr, Reddit, Telegram, and more — with per-network message templates, image posting, and scheduling options including delayed and recurring re-shares. The self-hosted model means no monthly SaaS fee for what is ultimately API calls, and the per-network filter controls decide which content types post where. Against archive-recycling tools like content recycling, SAP’s focus is new-content distribution; against planning suites like CoSchedule, it’s the zero-effort automation layer rather than an editorial process.
The scheduling depth is the differentiator within auto-posters: posts can share immediately, on delay, at optimal times, or on recurring schedules — and re-sharing old content runs on its own recurring rules. Multi-account support per network covers agencies managing client properties from one WordPress install.
Competitive Features
- Broad network coverage — Facebook, X, LinkedIn, Instagram, Pinterest, Tumblr, Reddit, Telegram, and more
- Flexible scheduling — immediate, delayed, optimal-time, and recurring re-share rules
- Per-network templates — message formats customized per platform
- Multi-account support — several accounts per network from one site
- Content type filters — which post types share to which networks
- Image posting — featured images attach per network requirements
- Self-hosted economics — license pricing, no SaaS fees
Key Features
- WordPress cron integration — scheduled shares run reliably
- URL shortening — bit.ly and others for trackable links
- UTM tracking — social traffic attribution per network
- Logs — share history per post per network
- Gutenberg and classic support — works with both editors
- Import/export settings — configuration portability
- WooCommerce support — products share automatically
Comparison with Competitors
Social Auto Poster Pro vs Revive Old Posts
| Aspect | Social Auto Poster Pro | Revive Old Posts |
|---|---|---|
| Trigger | On publish (plus scheduled) | Archive recycling schedule |
| New content | Core strength | Supported |
| Old content resurfacing | Via recurring rules | Core feature |
| Network set | Broader | Focused major networks |
| Shared goal | Automated distribution | Automated distribution |
Bottom line: Overlapping automation tools with different centers of gravity. SAP covers new-post distribution across a broader network set; ROP specializes in keeping archives alive. Content-heavy sites run both — publish-time plus recycling.
Social Auto Poster Pro vs Monarch
| Aspect | Social Auto Poster Pro | Monarch |
|---|---|---|
| Direction | Outbound auto-posting | On-site sharing UI |
| Trigger | Publishing schedule | Visitor action |
| Share counts | No | Yes |
| Complementary | Yes | Yes |
Bottom line: Monarch makes visitor sharing frictionless; SAP pushes content out automatically. Complete social strategy uses both directions — reach plus shareability.
Recommended Stack — social traffic lands on conversion pages: pair SAP with popup capture for social traffic so the traffic auto-posting generates hits targeted opt-ins.
Official Changelog
Version 5.5.5
Release Date: August 20, 2026
- Feature release: network integration and scheduling refinements.
Version 5.5.4
Release Date: July 12, 2026
- Feature release: template and filter improvements.
Version 5.5.3
Release Date: June 8, 2026
- Maintenance release: stability and compatibility fixes.
Frequently Asked Questions
Which networks does it support?
Facebook (pages and groups), X, LinkedIn, Instagram, Pinterest, Tumblr, Reddit, Telegram, Blogger, and more — the broadest set among self-hosted auto-posters, with per-network configuration.
Can it re-share old content?
Yes — recurring schedule rules re-share archive content on intervals, though dedicated recycling tools like Revive Old Posts offer deeper old-content filtering. SAP’s core is new-post distribution.
Does it post images?
Yes — featured images attach to shares per each network’s format requirements, with per-network image toggles.
Do I need API developer accounts?
Yes — each network requires its own API credentials (app registration), set up once per network. The plugin documents the process per platform.
How is it different from Buffer-style SaaS tools?
Self-hosted automation at license pricing versus subscription SaaS. SAP runs from your WordPress install via cron — no monthly fees, no third-party dependency, with multi-account support included.
Leave a Reply