Shared Counts plugin review and common issues

Shared Counts retrieves counts from platform APIs and caches them. If counts show as 0: (1) the initial API request may not have occurred — counts are retrieved on first page visit after publication; (2) clear the Shared Counts count cache in the plugin settings (or clear WordPress transients) to force a fresh API request; (3) Facebook count retrieval now requires App credentials — add your Facebook App ID in Shared Counts settings; (4) Twitter/X removed public share count API access — Twitter counts will always show 0; (5) verify the URL being counted exactly matches the canonical URL of the post.

In Settings → Shared Counts → Display, select the button style from the available options (flat, flat-large, gray, official, rounded, etc.). Save settings and clear all caches. If buttons appear unstyled even after selecting a style: (1) a caching plugin may serve the page with old CSS; (2) the Shared Counts CSS file may be blocked by a performance plugin’s CSS exclusion rules — add Shared Counts to the CSS exclusion list; (3) a theme CSS rule may override Shared Counts button styles — use browser DevTools to check for competing styles.

Shared Counts floating bar can be controlled via CSS. Add to your theme’s custom CSS: @media (max-width: 768px) { .shared-counts-float { display: none !important; } } This hides the floating bar on mobile devices while keeping it visible on desktop. The above/below content buttons still display on mobile for sharing access. For a cleaner approach, use the Shared Counts shortcode [shared_counts] to manually position buttons within the content where they work well on all screen sizes.

Shared Counts does not have built-in category-level display conditions. Use a filter in your theme’s functions.php: add_filter(“shared_counts_display”, function($display) { if (is_category(“news”) || in_category(“news”)) { return false; } return $display; }); This example hides buttons for posts in the “news” category. Replace “news” with your category slug or ID. For other condition types (post format, user role, page type), use the appropriate WordPress conditional functions.

Use the Shared Counts shortcode [shared_counts] in a custom WooCommerce product description section or use a WordPress action hook. Add to functions.php: add_action(“woocommerce_after_single_product_summary”, function() { echo do_shortcode(“[shared_counts]”); }, 15); This adds Shared Counts buttons below the product summary. Adjust the priority number (15) to position the buttons before or after other WooCommerce content sections.

Yes — Shared Counts is generally faster than Social Warfare. Shared Counts loads minimal JavaScript and CSS from the local server, while Social Warfare loads more JavaScript for its feature-rich button system. For sites where page speed scores and Core Web Vitals are a priority, Shared Counts’s minimal footprint is measurably better. The trade-off is Social Warfare’s richer features (click-to-tweet, Pinterest image control, per-post OG settings) that justify its additional load for content-focused sites where sharing is a primary traffic channel.

Shared Counts does not have specific AMP support built in. For AMP pages (using the AMP plugin), standard JavaScript-based sharing buttons are not compatible with AMP’s strict validation requirements. AMP pages typically use AMP-specific social sharing components. AddToAny Share Buttons is the recommended plugin for sites that require AMP compatibility, as it includes built-in AMP support.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.