Social Warfare

Social Warfare renders share buttons without loading the networks' scripts. That is the technical point of it, and it matters more than any feature on the list: a share button can be a plain link with an icon, or it can be a third-party embed that pulls in a tracking script.

The wider question — whether share buttons still deserve the space — is worth answering before choosing which plugin renders them.

What it does

• Share buttons for the major networks, placed before or after content, floating, or both.
• Control over which networks appear and in what order.
• Per-post control over the title, description and image used when a link is shared.
• Open Graph and card metadata, which overlaps with what an SEO plugin already does.
• Optional click-to-tweet blocks and pin-specific images.

The per-post share metadata is the genuinely useful part for content sites: the headline that works on your page is often not the headline that works in a feed, and being able to set them separately is worth something.

The overlap with your SEO plugin

Both Social Warfare and every SEO plugin generate Open Graph and Twitter card tags. Two plugins emitting them means duplicate tags, and networks then pick one unpredictably.

Decide which one owns social metadata and turn the feature off in the other. This is the same rule as never running two SEO plugins — see Yoast SEO and the WordPress SEO checklist.

The share-count problem

Share counts were the original reason plugins in this category cost money: displaying "4,200 shares" is social proof.

Most major networks removed their public count endpoints years ago. What that means practically:

• Counts are unavailable for most networks, whatever a plugin promises.
• Where counts are shown, they usually come from a paid third-party service that has been tracking shares over time.
• A recovery feature exists in some plugins to preserve counts across a URL change, which only matters if you had counts to preserve.

If share counts are your reason for buying a share plugin, verify which networks actually provide them now before spending anything.

Performance and privacy

This is where the choice of plugin genuinely matters.

Network-provided buttons — the official embeds — load third-party JavaScript on every page. That costs requests, blocks rendering, and sets third-party cookies, which is a consent question in several jurisdictions.

Self-rendered buttons are links with an icon and a share URL. No third-party script, no cookie, negligible weight.

Social Warfare is in the second category, which is the main reason to use a plugin like it rather than the networks' own code. Two things to still check:

• Whether it loads its assets site-wide or only where buttons appear. On a site with buttons only on posts, that difference is measurable — how to speed up a WordPress site.
• Whether any count service it uses introduces an external request of its own.

The consent implications of third-party embeds generally are covered in cookie consent plugins.

Do you need share buttons at all?

The uncomfortable question, and worth asking honestly.

Where they get used: recipes, news, long-form guides, anything people forward. On these, sharing is a real behaviour and the buttons remove friction.

Where they do not: business brochure sites, service pages, most B2B content, product pages. The buttons occupy prominent space, appear on every page, and are clicked almost never.

Check before deciding. Your analytics can record share clicks as events — analytics plugins covers the setup. Run it for a month. If the number is negligible, you have reclaimed screen space and a dependency for nothing.

A floating share bar on mobile is worth particular scrutiny: it covers content on the smallest screens, which is where most of your readers are.

Where to place them

If you keep them:

• After the content for long-form, where someone who has finished reading is the person likely to share.
• Before and after for content people share without reading fully, such as recipes.
• Not floating over mobile content, or at least not covering text.
• Three or four networks, not eleven. A wall of icons reads as clutter and dilutes the ones that matter.
• Not on every page type. Posts, usually; service pages, rarely.

Common mistakes

• Duplicate Open Graph tags from this plugin and an SEO plugin.
• Buying for share counts that the networks no longer provide.
• Eleven networks displayed, because they were available.
• A floating bar covering mobile content.
• Buttons on every page type including the contact page.
• Never measuring whether anyone clicks them.

Deciding

If you publish content people genuinely share, a self-rendering share plugin is a reasonable, light addition, and per-post social metadata is a real benefit. If your analytics show almost no share clicks, the right answer is to remove the buttons entirely — which is faster, cleaner, and costs nothing to maintain.