Key takeaways
- Decide the job first: share buttons, follow icons, a feed, auto-posting, social login, link previews or WooCommerce catalog sync. No single plugin does all of them well.
- Feeds need the most upkeep. Expired tokens, a stalled WP-Cron and JavaScript conflicts cause most blank or stale feeds, and Wake Forest University’s WordPress guide plans for reconnecting roughly every six weeks.
- Free share buttons are easy to find. AddToAny shows 300,000+ active installs on WordPress.org. Facebook no longer reliably gives share counts to third-party buttons, so changing plugins won’t bring them back.
- Link previews come from og:image tags, which your SEO plugin usually sets. A social plugin is rarely the fix for a wrong preview image.
- On a WooCommerce store, Troubleshooting Mode does not put payment gateways into sandbox, so test conflicts on staging.
Search the WordPress.org directory for “social media” and you get share buttons, Instagram galleries, auto-posters, profile icons, login tools and catalog sync, all in one list. These are different products. They connect to different things, they break in different ways, and they cost different amounts to keep running.
So “which social media plugin is best” has no single answer. A better question is which job you need done, and how much upkeep you’re signing up for. The installation itself is the easy part, and our guide to installing a WordPress plugin safely covers it. This article covers the decision that comes before it.
Which social job do you actually need done?
Name the job before you look at any plugin. Practitioner threads are full of mismatched answers. In one, someone asked for Pinterest share buttons and was pointed to a feed plugin, which does the reverse.
| Job | What it does | What it connects to | Ongoing upkeep |
|---|---|---|---|
| Share buttons | Visitors share your page to their own networks | Nothing; buttons open share links | Low |
| Follow icons | Link to your own profiles | Nothing; they are plain links | Very low |
| Social feeds | Show your Instagram, Facebook, YouTube or TikTok posts on your site | The platform’s API, through an access token | High |
| Auto-posting | Publish your new posts to your own social accounts | Each network’s API, one connection per account | Medium to high |
| Social login | Visitors sign in with a social account | Each provider’s OAuth app | Medium, and it touches security |
| Link previews (Open Graph) | Set the image and title shown when someone shares your link | Nothing; these are meta tags in your page | Low, usually handled by your SEO plugin |
| Catalog sync | Push WooCommerce products to Facebook or Instagram shops | Meta’s commerce tools | High |
The upkeep column matters more than the feature list. Anything that holds a token for someone else’s platform will break when that platform changes its rules, and you’ll be the one who notices.
Why share buttons are the easy part
Share buttons need no account and no API key. Each button opens the network’s share dialog with your URL already filled in. That’s why good free options exist. AddToAny, one of the most installed, showed 300,000+ active installs in the WordPress.org directory.
There are three things to know before you add them.
- Share counts are mostly gone. In a Jetpack support thread on WordPress.org, Jetpack’s team explained that Facebook no longer reliably makes share-count data available to third-party sharing buttons. Switching plugins won’t restore the numbers.
- Icon-only buttons need accessible names. W3C’s guidance on functional images says the text alternative should describe what the control does. “Share on Facebook” works. “icon” or “facebook-logo” doesn’t. Check that your plugin outputs a label, and add one if it doesn’t.
- Buttons add some weight. Isolated benchmarks of individual share plugins showed small effects. They used different metrics on different setups, so none of them ranks one plugin above another. Measure your own page before and after, on mobile.
Some practitioners take share buttons off entirely as mobile clutter, and nobody has published usage data that settles the argument. If your analytics show almost no social referrals, removing the buttons is a reasonable choice.
Why feeds need the most maintenance
Feeds bring the most visible value and the most support threads. Smash Balloon’s Instagram feed plugin is the most installed in the category, with 1,000,000+ active installs on WordPress.org. Its own documentation also lists the most failure modes, which tells you what running a feed actually involves.
The token expired or the platform changed its API
This is the most common cause. The plugin reaches Instagram or Facebook with an access token, and tokens expire, get revoked when someone changes a password or admin role, or stop working when Meta retires an API. Smash Balloon’s error reference covers API error 190: Error validating access token. The fix is to remove the source, save, and reconnect.
Update the plugin before you reconnect. When Meta retired the older Instagram connection method, reconnecting through an outdated plugin version didn’t help. Wake Forest University’s WordPress guide expects feed connections to need reconnecting roughly every six weeks and recommends turning on the plugin’s feed-issue email report. That interval is one institution’s experience, not a rule. Still, it’s a sensible calendar reminder.
The feed only updates when you clear the cache
This usually isn’t a broken plugin. Smash Balloon’s doc on this symptom names three causes: WP-Cron or the server cron isn’t running, the page cache lifetime is too long, or the feed’s own cache interval is too long. WP-Cron only runs when someone visits, so a quiet site can go hours without a refresh.
Clearing the cache by hand brings the feed back, and it also hides the cause. Check whether cron is running with a plugin such as WP Crontrol, or ask your host about a real server cron. Then shorten the cache lifetime for the feed page, or exclude that page from the page cache.
The feed is blank or the loader keeps spinning
Open the browser console first. Smash Balloon’s troubleshooting list includes another plugin’s JavaScript error, outdated or duplicate jQuery, lazy-loading conflicts, script combining by an optimization plugin, a wrong shortcode or feed ID (curly quotes pasted from a document break it), and a theme that never calls the hooks plugins rely on:
<?php wp_head(); ?> <!-- inside <head> -->
<?php wp_footer(); ?> <!-- just before </body> -->If you have to edit the theme, do it in a child theme so the next theme update doesn’t undo your fix. Don’t apply site-wide workarounds such as turning off lazy loading everywhere until the console has shown you that’s the cause. Firewalls can also block feeds: support threads point to Cloudflare rules, ModSecurity and Wordfence blocking requests or settings saves. For the wider method, see our guide on fixing plugins that stop working.
Connecting feeds for clients
Agencies don’t need client passwords. Spotlight’s directory listing describes an Access Token Generator that lets the client authorize the connection themselves, and it supports separate accounts and feeds for each site.
Why free auto-posting usually comes with limits
Auto-posting is where “free” most often stops meaning free. Commenters on r/Wordpress keep reporting the same pattern: the free tier covers one or two networks, and Instagram or LinkedIn needs a paid plan or an add-on. Others ended up switching between plugins until one covered the networks they actually used.
The underlying reason sits with the platforms. Self-hosted tools that post to Meta’s networks need an approved developer app, and one Reddit user described waiting months for that approval. Before you install anything, write down the exact networks you post to. Then check that the free tier, or the plan you would buy, covers all of them. Also check whether “posting” means the full post with an image or just a link.
Auto-posters also depend on WP-Cron, the same as feeds. A scheduled share on a low-traffic site can go out late because nobody visited to trigger it.
Why the wrong image shows when your link is shared
Link previews come from Open Graph tags in your page’s head, mainly og:image and og:title. On most sites your SEO plugin writes these tags, not a social plugin. Installing a share plugin to fix a preview usually adds a second set of tags and makes things worse.
Google’s image documentation says its choice of preview image is automated and draws on several sources. og:image is one way to influence it, not a way to control it. Set a relevant image per post in your SEO plugin, give crawlers time to revisit, and never use noindex to “reset” a preview. Image optimization plugins that rewrite image URLs can also change these tags, so check the page source when the preview looks wrong. Our guide to doing SEO on WordPress covers where those settings live.
What to check before you install any social plugin
Spend a few minutes on the directory listing first. It saves more time than any feature comparison.
- Confirm it does your job. Read the description for the one thing you named above. A plugin that bundles login, counters and sharing adds code for jobs you may not need.
- Check maintenance. Look at “Last updated” and “Tested up to”. A feed or posting plugin that hasn’t been updated since the platform’s last API change will fail.
- Check the free tier against your network list. Every network, not just the first one.
- Decide where it loads. A feed belongs on the page it supports, such as a portfolio or a product page, not on every article template.
- Test one workflow. Connect one account and publish one post or one feed. Check the result logged out before you add a second network.
- Keep one plugin per job. Two share plugins or two plugins writing Open Graph tags cause conflicts, and removing the unused one closes off code you no longer need.
Social plugins look finished on the day you set them up, and then they need updates, reconnections and clean-up for as long as they’re installed. If you’d rather not do that yourself, SiteSelf handles plugin updates, settings and removals on request through chat, using its connector plugin for settings work and hosting access for file-level fixes. Reconnecting a social account still needs whoever owns that login.
If you run a WooCommerce store
Catalog sync to Facebook and Instagram shops gets mixed reports. Store owners on r/woocommerce describe one update to the official integration syncing every product, including disabled variations. Others report the integration working nearly out of the box. When you troubleshoot any social plugin on a store, WooCommerce’s documentation warns that Health Check’s Troubleshooting Mode does not switch payment gateways to sandbox, so an order placed during a test can take a real payment. WooCommerce recommends a backup and a staging site for conflict testing.