Social sharing buttons show up everywhere. You see them at the top of blog posts. They float beside long articles. They even sit in the footer on product pages. Still, many site owners wonder the same thing. Do people click those icons at all?
In most cases, people do not click social sharing buttons. Usage data from large sites often shows share-button clicks well under 1% of page views.1
What the Data Shows
One of the clearest public datasets came from the UK government’s GOV.UK site. The team added social sharing buttons and reviewed the first 10 weeks, from December 3, 2013 to February 17, 2014. They logged 14,078 shares from 6.8 million page views. That works out to about 0.21%.1
This is not a rounding error. It is what happened on a huge, useful site when the team added share buttons and watched the results.
Share buttons are often added because internal stakeholders request them, not because users ask for them.
In an earlier update on the experiment, the GOV.UK team noted that the feature sat in the queue for a long time because “zero end users” had requested it. In testing, people simply shared content by copying and pasting links.2
On mobile, several write-ups of Moovweb’s research point to the same pattern. A WARC news item from August 26, 2015 summed up the findings like this: “only 0.2% of mobile users do any social sharing.” The estimate came from analysis of more than 61 million mobile sessions.3
The same summary also flags a key problem. People often need to log in before sharing, and that adds a big barrier on a phone.3
Why visitors ignore social sharing buttons even when they like your content
Share buttons underperform for a few reasons. Some are about habits. Others are technical. Some come down to trust.
1) The share buttons are in the wrong spot
Many pages place share buttons at the top, before anyone reads a word. At that point, the visitor has not decided the page is worth sharing.
Other pages push buttons to the bottom. By then, the visitor often feels done and moves on.
In real life, the decision to share often happens mid-read. It can happen after a strong line. It can happen once someone forms an opinion. It can also happen when a specific person comes to mind.
2) People send links from apps, not the browser
Today, a lot of discovery and sharing happens inside social apps, group chats, newsletters, and messaging tools. Even when someone starts on your site, the share often happens later. They copy the link, switch apps, then send it.
This is why “share button clicks” can mislead. The sharing can still happen, just not through your icons.
3) Login prompts and permissions add friction
On mobile, friction hits harder. If a tap sends someone to a login screen, most people drop off.
The WARC summary of the Moovweb research points to this exact issue. Needing to log in first turns sharing into a chore, while other actions take one tap.3
4) Privacy expectations
Many social widgets used to include tracking. That damaged trust. It also created technical issues once browsers started blocking cross-site tracking.
Mozilla’s documentation on Enhanced Tracking Protection explains that social media trackers show up across the web. It also notes that Firefox blocks many common social media trackers. Like and share buttons can enable tracking even when nobody clicks them.4
Even with a privacy-friendly setup, many visitors now see these widgets as tracking tools. That gut reaction makes clicks even less likely.
5) Share buttons can be a performance tax
Share buttons often load through third-party JavaScript. Even small bundles add requests and run time. They also add more points of failure.
Google’s web.dev documentation lists social sharing buttons as a common use of third-party JavaScript. It also explains why third-party scripts often hurt performance.5
So you pay a cost in speed, complexity, privacy review, and maintenance. In return, many sites get a fraction of a percent of clicks.
People still share. They just do it “manually” and analytics often labels it differently
Share buttons get few clicks, but people still share content.
Most sharing happens when someone copies the URL and sends it where they already talk. They text it. They drop it into Slack. They forward it in email.
Sharing also happens inside apps where your site never sees a button click. This creates a tracking gap. Shares in private channels often look like “direct” traffic. They can also show up with missing referrer data.
Chartbeat’s documentation describes this problem. It uses an “Email, Apps, Messages” bucket for “Dark Social.” This label covers visits with no referrer data even though a share likely drove them, such as email, messages, or apps over secure connections.6
So your site can benefit from sharing even while the share buttons sit unused.
When social sharing buttons can still be worth keeping
Some sites still have good reasons to keep a sharing UI. The key is to stay realistic about what it can do.
Your content is highly time-sensitive or culturally shareable
On GOV.UK, some news items had much higher sharing rates than the site average. The report shows that share rates change a lot by topic and timing, even with the same button design.1
Breaking news, event recaps, and timely stories can drive more button use. It still may not be huge. But it can be meaningful.
Your audience wants to copy the link
The BBC’s Global Experience Language documentation for “Share tools” cites research showing as little as 0.25% of visitors use social media buttons. It also recommends including a “Copy this link” option. That matches how people share today.7
A “copy link” button can be much more useful than a row of social media logos.
You treat share buttons like a convenience feature, not a growth strategy
Adding buttons will not create a wave of free distribution. Treat them as a small convenience for the few visitors who want them. With that mindset, they can be a low-drama feature.
What to do instead or how to build share buttons people might use
Focus on fast, low-friction sharing that works everywhere. Also cut the baggage that comes with third-party widgets.
Practical ways to support sharing without relying on platform icons
- Make the page look good when it’s shared. Add clear metadata so link previews look great. This helps sharing through buttons, copy and paste, or native share sheets.
- Add a “Copy link” action near the content. This matches how people share in chats and email. It is often faster than picking a platform icon.
- Use the native share buttons when possible. The Web Share API opens the device’s built-in sharing menu. The user picks the app. It works for links and text.8
- Keep the UI minimal and contextual. Avoid adding share buttons to every template by default. Put them on pages with real sharing intent, like standout posts, key resources, or a thank-you page.
- Audit the performance cost of third-party scripts. Measure how much external JavaScript affects speed. Third-party scripts can slow pages down, and share buttons are a common example.5
- Decide what you are optimizing for. For more distribution, headlines, preview images, and email capture often beat more share icons.
Keeping share buttons can also work with a privacy-first setup. WIRED described an approach where buttons start disabled. Visitors are not tracked unless they choose to turn the controls on and use them.9
This adds an extra click, so it may reduce button use. Still, it is honest and matches what many users prefer.
Make a decision based on your own numbers
Handle social sharing buttons like any other product choice. Measure them. Then decide if they deserve space.
Track button clicks as events. Compare clicks to page views. Break the results down by device and content type.
Finding 0.1% usage does not mean something is broken. Many large sites see the same pattern.1
From there, choose the best next step. You can remove the clutter. You can keep a small “copy link” option. You can replace icons with a native share flow.
Assume people will not click social sharing buttons, and make your content worth sharing anyway.
References
- Francis, G., & Chohan, A. (2014, February 20). GOV.UK social sharing buttons: The first 10 weeks. Inside GOV.UK. https://insidegovuk.blog.gov.uk/2014/02/20/gov-uk-social-sharing-buttons-the-first-10-weeks/
- Williams, N. (2013, December 2). A time for sharing (government content on Facebook and Twitter). Inside GOV.UK. https://insidegovuk.blog.gov.uk/2013/12/02/a-time-for-sharing-government-content-on-facebook-and-twitter/
- WARC. (2015, August 26). Mobile users prefer ads to sharing. https://www.warc.com/newsandopinion/news/mobile-users-prefer-ads-to-sharing/en-gb/35293
- Mozilla. (2025, February 22). Trackers and scripts Firefox blocks in Enhanced Tracking Protection. Firefox Help. https://support.mozilla.org/en-US/kb/trackers-and-scripts-firefox-blocks-enhanced-track
- Mihajlija, M. (2019, August 13). Third-party JavaScript performance. web.dev. https://web.dev/articles/third-party-javascript
- Chartbeat. (2023, March 30). Real-Time metrics glossary. Chartbeat Help & FAQ. https://help.chartbeat.com/hc/en-us/articles/208982958-Real-Time-metrics-glossary
- British Broadcasting Corporation. (n.d.). Share tools. BBC GEL. https://bbc.github.io/gel/components/share-tools/
- MDN contributors. (2025, March 13). Web Share API. MDN Web Docs. https://developer.mozilla.org/en-US/docs/Web/API/Web_Share_API
- Gilbertson, S. (2013, March 26). Social sharing buttons that respect your visitors’ privacy. WIRED. https://www.wired.com/2013/03/social-sharing-buttons-that-respect-your-visitors-privacy/
