LinkedIn Share Link Generator

How to Create a Clickable Share Link for LinkedIn

Creating a direct LinkedIn share link makes it straightforward for your audience to distribute your content across their professional networks. Simply paste your target webpage URL into the input field above, configure any campaign tracking tags you need, and copy the generated link or embeddable HTML button. When clicked, it automatically opens the LinkedIn post composer with your page preview attached.

Understanding the LinkedIn Share URL Format

LinkedIn official sharing endpoint uses the following structure: https://www.linkedin.com/sharing/share-offsite/?url=YOUR_ENCODED_URL. Historically, LinkedIn supported legacy parameters like shareArticle?url=YOUR_LINK_HERE, but modern LinkedIn architecture ignores custom title and summary parameters in favor of automated Open Graph crawler tags.

Because the destination URL is appended as a query parameter, it is crucial that the URL is safely encoded with encodeURIComponent(). This ensures special characters like question marks, ampersands, or slashes inside your link do not break LinkedIn routing parser.

Architecture of LinkedIn Offsite Sharing Endpoints

Distributing content through LinkedIn represents one of the most effective organic channels for B2B professionals, thought leaders, technical founders, and enterprise organizations. Understanding the technical mechanics of how LinkedIn generates share dialogs and renders link preview cards is essential for maximizing referral click-through rates.

In previous developer API versions, LinkedIn maintained a query endpoint known as /shareArticle. This legacy endpoint supported parameters such as mini=true, title=Headline, summary=Description, and source=BrandName. Marketers could theoretically define custom headlines and text snippets directly within the share URL query string. However, bad actors frequently exploited this behavior to perform deceptive sharing, generating posts whose preview cards displayed arbitrary titles that bore no resemblance to the actual content hosted on the destination page.

To eliminate phishing, deceptive link cloaking, and misleading social cards, LinkedIn permanently transitioned to the modern share-offsite architecture. Under this model, the endpoint accepts strictly a single parameter: url. When a user clicks your share link, LinkedIn back-end scraper, identifying itself as LinkedInBot/1.0, initiates a server-to-server HTTP GET request directly to the target destination. The scraper inspects the HTML source code, extracts Open Graph meta tags, and dynamically renders the rich card preview inside the user post composer.

Open Graph Metadata Requirements for Rich Cards

Because LinkedIn no longer permits custom text parameters within the share URL, the visual presentation of your shared link depends 100% on the quality and validity of your webpage Open Graph (OG) metadata. To ensure that your shared links display an attractive, high-converting preview card rather than a bare text URL, you must configure the following standard tags within the <head> section of your HTML document:

• og:title: Defines the headline displayed beneath the card image. For optimal mobile and desktop readability, keep the title between 40 and 60 characters. Headlines exceeding 70 characters are truncated with an ellipsis on smaller smartphone displays.
• og:description: Provides a two to three line contextual summary of your article, product announcement, or case study. Aim for 100 to 150 characters. Write concise, informative copy that highlights key insights to entice professional clicks.
• og:image: Specifies the URL of the visual banner displayed above the headline. LinkedIn requires a 1.91:1 aspect ratio with an ideal resolution of 1200 pixels wide by 627 pixels tall. The minimum acceptable image dimension is 200 by 200 pixels, but images below 1200x627 will render as a tiny square thumbnail next to the text rather than a full-width immersive banner. Ensure the image file size is under 5 megabytes and formatted as PNG, JPG, or WebP.
• og:url: The canonical URL of your page. This prevents canonical duplication if your page is accessed via different tracking parameters or subdomain variations.

RFC 3986 URI Encoding and Query String Protection

A frequent bug in custom social share buttons is improper URL encoding. In standard web architecture, a URL query string uses question marks (?), ampersands (&), and equal signs (=) as structural delimiters to separate key-value pairs. For example, in the URL https://example.com/page?ref=twitter&mode=dark, the ampersand informs the browser that mode is a separate parameter from ref.

When you append your destination URL to LinkedIn share endpoint, your link itself becomes a parameter value: https://www.linkedin.com/sharing/share-offsite/?url=YOUR_URL. If your destination URL contains its own query parameters (such as UTM tracking tags) without proper percent-encoding, LinkedIn web server will misinterpret your inner ampersands as top-level parameters of the LinkedIn endpoint. Consequently, everything following the first ampersand is discarded, cutting your link short and corrupting your campaign attribution.

This generator automatically passes your complete destination address through encodeURIComponent() following the RFC 3986 specification. Slashes become %2F, colons become %3A, question marks become %3F, and ampersands become %26. When the LinkedIn share dialog opens, LinkedIn decodes the parameter safely, preserving your complete URL and tracking parameters with zero corruption.

Campaign Attribution and Enterprise UTM Taxonomy

Measuring the business impact of your social sharing initiatives requires clean attribution in analytics suites such as Google Analytics 4 (GA4), Mixpanel, and Adobe Analytics. Incorporating UTM campaign parameters allows growth marketers to differentiate between traffic generated by internal newsletter click-to-share buttons, employee advocacy programs, and spontaneous community shares.

This tool incorporates an integrated UTM Tracking Builder. For consistent data governance across enterprise marketing teams, adhere to the following naming conventions:

• utm_source=linkedin: Always specify the source as lowercase linkedin to maintain unified channel grouping within GA4 default traffic dimensions.
• utm_medium=social: Use social for organic shares and employee advocacy links. Reserve cpc or paidsocial for sponsored content campaigns.
• utm_campaign: Assign a unique, descriptive slug reflecting the campaign topic, content format, or distribution cohort (such as spring_whitepaper_2026, developer_newsletter_q2, or executive_interview). Use lowercase letters and underscores rather than spaces or special characters.

Debugging Previews with the LinkedIn Post Inspector

When you share a link on LinkedIn for the first time, LinkedIn scraper crawls your webpage, fetches your Open Graph metadata, renders the card image, and stores the resulting data in an internal cache. This caching layer accelerates feed rendering for millions of simultaneous platform users. By default, LinkedIn retains cached preview data for up to 7 days.

If you publish an article and subsequently update the featured image, fix a typo in your headline, or change the meta description, LinkedIn will continue to serve the old, outdated preview card from its cache. To resolve this immediately, use the official LinkedIn Post Inspector tool (accessible via the direct button in this utility). Submitting your URL to the Post Inspector flushes the LinkedIn cache, forces an immediate re-scrape of your target webpage, and displays a comprehensive diagnostic report showing any missing tags, SSL handshake warnings, or redirect issues.

LinkedIn Sharing Protocols & Parameter Matrix

Interactive HTML Button Integration and Modal Geometry

Embedding a professional LinkedIn share button into your website or email newsletter significantly increases viral distribution. This generator produces production-ready HTML code styled with LinkedIn official brand colors and accessible attributes:

<a href="https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fexample.com%2Fpost" 
   target="_blank" 
   rel="noopener noreferrer" 
   class="linkedin-share-button">
  Share on LinkedIn
</a>

For custom web applications where you prefer opening the share dialog in a centered popup modal rather than a full browser tab, use the following JavaScript snippet:

function openLinkedInShare(url) {
  const width = 600;
  const height = 600;
  const left = (window.innerWidth - width) / 2 + window.screenX;
  const top = (window.innerHeight - height) / 2 + window.screenY;
  const shareUrl = "https://www.linkedin.com/sharing/share-offsite/?url=" + encodeURIComponent(url);
  window.open(shareUrl, "linkedin_share", `width=${width},height=${height},top=${top},left=${left},toolbar=0,menubar=0`);
}

This dual-monitor centering math guarantees that the popup opens gracefully in the dead center of the user active screen, creating a smooth desktop experience without navigating away from your primary website content.

Client-Side Security and In-Memory Execution

Corporate marketing assets, embargoed press releases, and internal communications strategies demand strict privacy. Many third-party link shorteners and share-link services track your destination URLs, compile user interaction dossiers, and store marketing links in centralized databases.

This tool is engineered with a client-first privacy philosophy. All string manipulation, UTM concatenation, percent-encoding, and live feed preview rendering execute entirely within your local web browser using client-side JavaScript. No links, campaign names, or user data are ever transmitted to an external server or stored in persistent storage. You can generate unlimited corporate share links with complete confidence in your operational privacy.