Social share buttons are on almost every news site, every WordPress blog, and half the company content pages on the internet. They sit there — Facebook, X, LinkedIn, the little envelope for email — quietly consuming layout space, adding JavaScript weight, and creating cookie-consent headaches. And almost no one ever clicks them.
What the Numbers Actually Say
Derek Hanson pulled together three separate datasets, and the convergence is striking.
The UK government's GOV.UK team ran the most rigorous test. They added social sharing buttons and tracked every interaction for ten weeks across 6.8 million pageviews. The buttons were clicked 14,078 times. That's a usage rate of 0.21% — roughly 1 in 476 visitors. The feature had sat in their backlog for ages because zero end users had ever actually requested it. In their own usability testing, people just copied and pasted links.
Moovweb found the same thing when they analyzed 61 million mobile sessions. Only 0.2% of mobile users interacted with social sharing at all. To put that in context: visitors were twelve times more likely to click an advertisement than a share button.
Luke Wroblewski — interaction designer, author, and someone with the kind of audience that would actually use share buttons if anyone would — crowdsourced data from his readers across 18 million pageviews. He landed on 0.25%. Different organization, different audience, same number.
Different organizations, different audiences, same number. At some point, that's not a coincidence — it's the baseline.
Where Sharing Actually Happens
The counterintuitive part: people are still sharing content. They just aren't using your buttons to do it.
In 2012, Alexis Madrigal at The Atlantic noticed a huge chunk of the magazine's web traffic showing up as "direct" in Google Analytics. These weren't bookmarks or typed URLs. They were clicks on links that someone had pasted into a text thread, an email, a Slack channel. Madrigal coined the term "dark social" for this invisible sharing layer — and it turned out to be the dominant sharing mechanism on the web.
That pattern holds today. On this very site, Hanson notes, "Direct/none" is the number one referrer. Not Twitter, not LinkedIn — a private paste into a DM or an email.
Why Teams Build Them Anyway
The GOV.UK case is instructive: the feature stayed in the backlog until someone finally built it, despite no user ever asking for it. That's not a failure of research — it's a very human pattern.
Share buttons feel like a zero-cost win. They're a checkbox item that looks like it adds capability. The effort to ship them is low. But the cost isn't zero: third-party scripts, tracking pixels, cookie consent dialogs, maintenance overhead, and layout clutter all accumulate. The feature just isn't visible enough for anyone to question whether it's pulling its weight.
The more useful intervention is making the URL itself share-worthy: short, readable, canonical. Give people something worth copying, and they'll copy it — whether you build a button for it or not.