Contributors: jaredatch, billerickson
Tags: sharing, share buttons, social buttons, share counts, social, facebook, linkedin, pinterest, twitter
Requires at least: 4.6
Tested up to: 5.2
Stable tag: 1.4.0
Requires PHP: 5.6
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Shared Counts is a WordPress social media share buttons plugin. Sharing buttons increase traffic and engagement by helping readers share your posts and pages to their friends on social media.
Included Buttons
- Facebook Share Button
- Pinterest Pin Button
- Yummly Button
- Twitter Tweet Button (using the third-party Twitcount.com API)
- Email Sharing (with reCAPTCHA support to prevent abuse)
- Share Count Total
- Print Button
- LinkedIn Share Button
Facebook, Pinterest, Yummly, and Twitter buttons support social count display and tracking.
In Settings > Shared Counts you can select where the share buttons can appear automatically (Before Content, After Content, Before & After Content). When editing a post, you can use the checkbox in the "Shared Counts" box in the right column to disable the automatic buttons on this specific post.
You can use the [shared_counts] shortcode to manually display the buttons.
We include many share button styling options, so you can pick the perfect look for you site. Additionally, you can automatically insert the share buttons before and/or after the post content. Want granular or manual control? No problem! You can also use the [shared_counts] shortcode to insert them inside your content as you see fit.
We provide a one-click option to retrieve both HTTP and HTTPS share counts, ensuring you don't lose your share counts when upgrading your website to HTTPS.
Unlike other social sharing tools, this plugin does not use cookies, tracking scripts, or store any user data.
Shared Counts was created with site performance in mind, even at large scale. It is used on several large websites that get tens of millions of page views each month. Our unique and creative caching methods have a minimal affect on site overhead. Leveraging the SharedCount.com API, we can retrieve (almost) all share counts in a single request.
Additionally, Shared Counts was built to be developer friendly! We provide very liberal usage of hooks and filters. Everything is customizable and the possibilities are near limitless. Unlike other plugins all data (counts) are stored and cached in post_meta which makes it easy to access for extending (e.g. fetch top 10 most shared posts on your site). We have extensive documentation on our website and we're also on GitHub.
- Shared Counts - Pinterest Image - Upload a separate image for Pinterest sharing
- Shared Counts - Cache Status - Build and check the status of the Shared Counts cache
For details on this please see the Shared Counts website and our GitHub wiki.
If you find an bug or problem, please let us know by creating an issue.
Contributions are welcome!
- Open an Issue on GitHub.
- Fork Shared Counts on GitHub.
- Create a new branch off of
develop; branch name should beissue/###to reference the issue. - When committing, reference your issue and provide notes/feedback.
- Send us a Pull Request with your bug fixes and/or new features.
- Download the plugin from GitHub. or from WordPress.org.
- Activate plugin.
- Go to Settings > Shared Counts to configure.
We recommend you sign up for a free account at SharedCount.com, which lets you receive share counts from all services (except Twitter) with a single API query. Alternatively, you can select "Native" as the count source and select which services you'd like to query. If you select all 5 native service queries, then you will have 5 separate API queries every time share counts are updated.
If you would like to include Twitter share counts, you can sign up for a free account at twitcount.com.
If you use the Email share button, we recommend you enable Google's reCAPTCHA to prevent spam. Sign up here (free) to get your Site Key and Secret Key.
Master branch is always stable and contains latest releases. Development occurs in the develop branch while large features/changes are contained in dedicated branches. For reporting bugs or contributing, see more additional information below.