Social Snap plugin review and common issues

Social Snap retrieves share counts from platform APIs. Issues: (1) Facebook counts require App credentials — in Social Snap → Settings → Social Profiles → Facebook, enter your App ID and App Secret; (2) Twitter/X no longer provides public share count API — Twitter counts will show as 0 permanently; (3) Pinterest counts may require Pinterest API access; (4) new posts may have legitimate zero counts — the counts are accurate even if disappointing; (5) share count data is cached — clear Social Snap cache to force a fresh API request.

The Content Locker uses JavaScript to detect when a share action completes and then reveals the locked content. Issues: (1) some social network share windows do not return a confirmation callback — the locking system may rely on detecting window closure rather than confirmed sharing; (2) a popup blocker may prevent the share window from opening, blocking the locker from detecting a successful share; (3) the social network selected for locking may not support the JavaScript callback Social Snap uses; (4) clear all caches — a cached page may not have the updated JavaScript for content locking.

Auto-posting in Social Snap Pro requires connected social account credentials. Check: (1) verify social accounts are connected in Social Snap → Settings → Social Profiles with valid credentials; (2) auto-posting must be enabled per post type in Social Snap → Settings → Auto-Post; (3) the post must be a new publication (not an update to an existing post) for auto-posting to trigger; (4) check if WordPress cron is running correctly — auto-posting may be scheduled via cron; (5) some social platforms (Facebook) require page access tokens rather than personal account tokens for posting.

In the WordPress editor, use the Social Snap click-to-tweet shortcode or block. In Gutenberg, search for the “Click to Tweet” block in the block inserter (Social Snap must be active). Add the block and enter the tweetable quote text (keep under 280 characters including the link). The block renders as a styled highlighted quote with a Twitter/X share button. Strategically place click-to-tweet blocks around key insights, statistics, or compelling statements in the post content to create multiple sharing opportunities.

In Social Snap → Settings → Display → Post Types, configure which post types display Social Snap buttons. Uncheck post types where sharing is not desired (e.g., uncheck Pages if sharing buttons are only wanted on blog posts). For custom post types registered by other plugins (WooCommerce products, portfolio items), they appear in this list when properly registered as public post types. Enable WooCommerce products specifically by adding “product” to the enabled post type list.

Social Snap is better for blogs that want content locking, auto-posting, and sharing analytics in one plugin without needing multiple tools. Social Warfare is better for blogs where Pinterest traffic is significant (Social Warfare Pro’s Pinterest image control is uniquely strong), click-to-tweet is the primary growth tactic, or the visual quality of sharing buttons is a priority. Both offer comparable sharing button features at similar price points ($29.95 Social Warfare vs $49.95 Social Snap Pro).

Google’s guidelines caution against cloaking content — showing different content to search engines than to users. The Content Locker shows locked content to visitors but Google’s crawlers see the full content for indexing. This means the content IS indexed and provides SEO value even though visitors must share to view it. Google has not explicitly penalized content lockers, but some SEOs consider them a gray area. Use content lockers for supplementary content (bonus material, templates) rather than core article content.

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.