Section 02 of 06
Social share counters: how the numbers work
A share counter shows numbers your site never measured: each network reports how often it has seen your address shared, and a plugin adds those reports up. When a network changes its API or removes counts, the number breaks, and nothing on your site has changed.
This section explains where counts come from, how to get Facebook's figure with the right token, what to do when counts stop updating, and how to measure sharing yourself with analytics events instead of relying on network numbers.
Every other section is listed guide by guide in the full handbook index.
The guides in this section
- How share counts work, and why most networks stoppedHow Facebook and other networks calculate share counts, why X, LinkedIn and others removed them, what a share counter really shows, and how plugins fetch it.6 min read
- Facebook share count: getting it from the Graph APIHow to get the Facebook share count for a URL from the Graph API, why the old REST API stopped working, rate limits, and how plugins should cache the result.6 min read
- Share count not updating or not accurate: a fix listShare counts stuck at zero or wrong? Work through tokens, caches, cron, URL variants and rate limits in order, and why you should never add fake shares.6 min read
- How to create a Facebook access tokenCreate the right Facebook access token for share counts and plugins: user, page and app tokens compared, how long each lasts, and how to keep the token safe.6 min read
- How to create a Facebook app IDCreate a Facebook app ID for share counts, the fb:app_id tag and sharing plugins: the dashboard steps, the settings that matter, and vanishing like buttons.5 min read
- Tracking shares and pageviews in analyticsTrack share button clicks as analytics events, tag shared links with campaign parameters, and read shared traffic in referrer reports without cookies.5 min read
Why this topic lives here
Share counts were the most linked subject on this domain's old knowledge base: access tokens, app IDs, counts not updating, and the deprecated Facebook REST API. The guides below rewrite that material for how the networks behave now.
Where to start, by situation
The counter shows zero, or the same number for weeks. Begin with share count not updating or not accurate: a fix list; the cause is a token, a schedule or a cache in most cases. You are setting up Facebook counts for the first time. Create the app in how to create a Facebook app ID, then the token in choosing and creating a Facebook access token, then read Facebook share count: getting it from the Graph API to see what the number includes. You want to know what sharing actually does for the site. Skip the network numbers and send your own events, as in tracking shares and pageviews in analytics; if you need the background first, how share counts work explains why most networks stopped publishing counts.
How this section connects to provenance
A share count is sometimes read as a sign that a page is trustworthy: many people shared it, so someone must have checked it. The number does not support that reading. Counts can be inflated by settings (the plugin this domain once sold had a field labelled Fake Share Count that added a number to every post's total), merged across http and https variants, bought from services that sell shares, or frozen at a value from years ago. A high count says an address circulated. It says nothing about who wrote the page, whether a person did, or whether the image is what it claims to be. The provenance section treats counts as one weak signal among many; the publisher guide to AI content in feeds explains what stronger signals a publisher can add, and spotting AI images in your feed shows why a widely shared image still needs checking.
What the networks still report
The situation as of the cited developer pages: Facebook returns a count for an address through its Graph API when the request carries a valid app token, and the number can be shares alone or shares plus comments depending on the field you ask for. X removed its public count endpoint in 2015 and LinkedIn removed its share count in 2018, so any plugin still showing numbers for those two is showing a cached value or an estimate. Pinterest and Reddit expose counts through interfaces that are undocumented or rate limited, and the guides say so where they apply. This is why the section spends one guide on the Graph API itself, two on the app ID and token it needs, and one on doing without network numbers altogether. If a replacement plugin promises counts for every network, ask where each number comes from before trusting the total; the replacement guide lists that question first.
Questions
Why do share counters show zero?
The network stopped reporting counts, the access token is invalid, scheduled refreshes are not running, or a cache is serving an old page.
Which networks still provide share counts?
Facebook through its Graph API with a token, and a few others unofficially. X and LinkedIn removed public counts.
Are share counts accurate?
Rarely exactly. URL variants, cache age and different definitions of a share all make totals drift.
Can I show share counts without a plugin?
Yes, with a small script that asks the Graph API for your address with an app token, caches the reply in a transient, and prints the number in the template. The Facebook share count guide shows the request.
Hannah Voss, Editor. Checks every guide against a working WordPress install and the networks' current documentation. Last reviewed September 2026.