How to Fix Missing Social Share Links on Blog Articles
This check flags article and blog pages that have no social share links, meaning readers who want to pass a post along must copy the URL by hand. By the end of this guide, every article template on your site will output lightweight, plain-HTML share links that load no third-party scripts, and you will have confirmed they appear in the page source.

Why it matters
Share links are not a ranking factor, which is why this check is low impact. They make it easier for readers to send your articles to X, LinkedIn, Reddit, email or messaging apps, and those shares can lead to visits, mentions and links. Using plain anchor links instead of third-party share widgets also avoids extra JavaScript, tracking pixels and cookie-consent issues.
The old widget approach often slowed pages and hurt Core Web Vitals.
What you need
Step-by-step fix
Identify which template renders your articles
Open two or three of the flagged URLs and work out which template produces them. Look for the single post template, the blog article section or the CMS collection page. Fixing the template once fixes every article that uses it.
If you have more than one article layout, such as news, guides and case studies, note each one.
Pick a short list of share destinations
Choose 3 to 5 networks your audience actually uses, because long rows of icons get fewer clicks. The share endpoints below work without an SDK or API key:
- X:
https://x.com/intent/post?url=URL&text=TITLE - LinkedIn:
https://www.linkedin.com/sharing/share-offsite/?url=URL - Facebook:
https://www.facebook.com/sharer/sharer.php?u=URL - Reddit:
https://www.reddit.com/submit?url=URL&title=TITLE - WhatsApp:
https://wa.me/?text=URL - Bluesky:
https://bsky.app/intent/compose?text=TITLE%20URL - Email:
mailto:?subject=TITLE&body=URL
Add plain HTML share links to the template
Place the markup below the article title or after the article body. Replace the placeholder URL and title with your template variables. Both values must be URL-encoded.
Use real <a href> elements rendered on the server, not buttons that build the URL in JavaScript, so crawlers and users with JS disabled both see them.
<nav class="share" aria-label="Share this article"> <span>Share:</span> <a href="https://x.com/intent/post?url=https%3A%2F%2Fexample.com%2Fblog%2Fspring-guide&text=Spring%20Guide%20from%20Example%20Co" target="_blank" rel="noopener noreferrer">X</a> <a href="https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fexample.com%2Fblog%2Fspring-guide" target="_blank" rel="noopener noreferrer">LinkedIn</a> <a href="https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fexample.com%2Fblog%2Fspring-guide" target="_blank" rel="noopener noreferrer">Facebook</a> <a href="mailto:?subject=Spring%20Guide%20from%20Example%20Co&body=https%3A%2F%2Fexample.com%2Fblog%2Fspring-guide">Email</a> </nav>
Generate the URLs dynamically (WordPress example)
Hard-coded URLs only work for one page, so build them from the post data. In a classic WordPress theme, add this to single.php, or to a template part it includes, inside the loop. Use rawurlencode() on both the permalink and the title.
<?php $share_url = rawurlencode( get_permalink() ); $share_title = rawurlencode( wp_strip_all_tags( get_the_title() ) ); ?> <nav class="share" aria-label="Share this article"> <a href="https://x.com/intent/post?url=<?php echo $share_url; ?>&text=<?php echo $share_title; ?>" target="_blank" rel="noopener noreferrer">Share on X</a> <a href="https://www.linkedin.com/sharing/share-offsite/?url=<?php echo $share_url; ?>" target="_blank" rel="noopener noreferrer">Share on LinkedIn</a> <a href="https://www.facebook.com/sharer/sharer.php?u=<?php echo $share_url; ?>" target="_blank" rel="noopener noreferrer">Share on Facebook</a> <a href="mailto:?subject=<?php echo $share_title; ?>&body=<?php echo $share_url; ?>">Email</a> </nav>
Optionally add a native share button on mobile
The Web Share API opens the device's own share sheet, which includes Messages, Slack, WhatsApp and more. Add it as an extra button alongside the anchor links, not instead of them. It only appears in supporting browsers, and crawlers do not see it.
<button type="button" class="share-native" hidden>Share…</button>
<script>
const btn = document.querySelector('.share-native');
if (navigator.share) {
btn.hidden = false;
btn.addEventListener('click', () => navigator.share({ title: document.title, url: location.href }).catch(() => {}));
}
</script>Check Open Graph tags so shares look good
Share links only send the URL. The network then reads your meta tags to build the preview card. Make sure each article outputs og:title, og:description, og:image (at least 1200x630) and og:url.
Without these tags, shared posts often show a blank or wrong image.
<meta property="og:title" content="Spring Guide from Example Co"> <meta property="og:description" content="A practical checklist for spring maintenance."> <meta property="og:image" content="https://example.com/images/spring-guide-1200x630.jpg"> <meta property="og:url" content="https://example.com/blog/spring-guide"> <meta name="twitter:card" content="summary_large_image">
Deploy and verify on the flagged articles
Publish the template change and clear any page or CDN cache. Open a flagged article and use View Source (Ctrl+U or Cmd+Option+U). Search for sharer, share-offsite or intent/post to confirm the links are in the raw HTML, then click each link to make sure the right URL and title prefill.
Finally, re-run the audit.
curl -s https://example.com/blog/spring-guide | grep -Eo 'href="https://(x\.com/intent|www\.linkedin\.com/sharing|www\.facebook\.com/sharer)[^"]*"'
Platform-specific notes
WordPress
**Block themes:** go to Appearance > Editor > Templates > Single Posts and add the Jetpack "Sharing Buttons" block, or a Custom HTML block containing your links. **Classic themes:** edit single.php in a child theme as shown above, or enable Jetpack > Settings > Sharing. Avoid plugins that load each network's JavaScript SDK.
Shopify
Many themes, including Dawn-based ones, include a Share block. Go to Online Store > Themes > Customize, switch the template selector to Blog posts, choose Add block > Share and save. For custom markup, edit sections/main-article.liquid and build URLs with {{ shop.url | append: article.url | url_encode }} and {{ article.title | url_encode }}.
Wix
Wix Blog posts include a share bar that can be toggled off. In the Editor, open the Blog Post page, select the post widget, click Settings > Display and switch Share buttons on, then publish. You cannot edit the raw template, so the built-in option is the supported route.
Webflow
Open the Blog Posts CMS Collection template page and add an Embed element. In its code, insert the Slug and Name fields with the "+ Add Field" button, and prefix the full domain, for example https://example.com/blog/{slug}. Webflow does not URL-encode field values, so keep titles free of & and # characters or omit the text parameter.
Next.js
Create a ShareLinks server component that takes the canonical URL and title as props. Build each href with encodeURIComponent() and render it in the article layout (for example app/blog/[slug]/page.tsx). Rendering on the server ensures the links are in the initial HTML rather than added after hydration.
Check that it worked
✅ How to verify
- View the page source of a flagged article and confirm the share anchors (x.com/intent, linkedin.com/sharing, facebook.com/sharer or mailto:) appear in the raw HTML, not only after JavaScript runs.
- Click each share link and check that the correct article URL and title prefill on the network's compose screen.
- Paste an article URL into LinkedIn Post Inspector (linkedin.com/post-inspector) and the Facebook Sharing Debugger to confirm the preview card shows the right title and image.
- Re-run the audit and confirm the number of articles without share links drops to zero.
⚠️ Common mistakes
- Loading heavy third-party share widgets (AddThis-style scripts or network SDKs) that add hundreds of KB, set tracking cookies and only inject links after JavaScript runs.
- Forgetting to URL-encode the page URL and title, which breaks links when a title contains &, # or ? characters.
- Adding share links to only one article layout while other post types or older posts use a different template.
- Hard-coding a single article's URL into a shared template, so every post shares the same page.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
Do social share buttons help SEO?
Not directly. Search engines do not rank pages higher for having share buttons or share counts. The benefit is indirect: easier sharing can bring more visitors, and that visibility can lead to mentions and backlinks.
What is the current share URL for X (Twitter)?
Use https://x.com/intent/post?url=ENCODED_URL&text=ENCODED_TEXT. The older https://twitter.com/intent/tweet endpoint still redirects, but the x.com intent is the current form.
Should share links open in a new tab?
It is common to use target="_blank" with rel="noopener noreferrer" so readers keep the article open. Email (mailto:) links should not use target="_blank".
Are share buttons GDPR-compliant?
Plain anchor links send no data to the social network until the user clicks, so they usually need no consent. Embedded widgets that load scripts from the network on page load can set cookies and typically require consent under GDPR and ePrivacy rules.
How to Fix a Missing Title Tag on Your Web Pages
How to Fix Key Content Hidden Inside Iframes
How to Fix Page Titles to Hit 50–60 Characters
How to Fix Intrusive Interstitials and Mobile Pop-ups
How to Fix Duplicate Title Tags Across Your Website
How to Fix Small Font Size on Mobile (16px Base Text)