How to Add a LinkedIn Feed to Your Website Without a Plugin

It's a reasonable thing to want to avoid, especially for something as specific as displaying a LinkedIn feed. The good news is you don't need a plugin to embed a professional, auto-updating LinkedIn feed on your website. You need one snippet, pasted once.

Before you start: LinkedIn is not live yet on CollectSocials. LinkedIn is reviewing our access to their Community Management API, and until that clears, company pages connect only for accounts LinkedIn has authorised on our app. The steps below are the flow every source follows, and they work today for Instagram, Facebook, Google Reviews, YouTube, TikTok and the rest.

This guide explains how to add a LinkedIn feed to your website without installing a single plugin, using an approach that works on WordPress, Webflow, Squarespace, Wix, or any custom-built site. One warning up front, because most guides on this subject get it wrong: the snippet is not the same on every host. On WordPress, Webflow, React and hand-built sites it is a script tag. On Wix and Squarespace it is a self-resizing iframe, because both of those builders sandbox or strip custom scripts. You pick the host in the embed dialog and the dashboard hands you the right one, which is a single copy-and-paste either way, but "one script tag works everywhere" is not a true sentence and pasting the wrong payload fails quietly.

Why People Want to Avoid Plugins for LinkedIn Feeds

The desire to go plugin-free isn't just preference, it's practical risk management. Let's look at what actually happens when you install a social media plugin:

Plugin conflicts: Social media plugins often load their own versions of jQuery, Font Awesome, or other libraries. When another plugin on your site loads a different version of the same library, things break.

Performance overhead: Many social media plugins make API calls on page load, run their own cron jobs, and write to your database, all of which slow down your site.

Maintenance dependency: You're now dependent on the plugin developer keeping it updated. Many LinkedIn-specific plugins on WordPress haven't been meaningfully maintained because LinkedIn's API is restrictive and keeps changing.

Scope creep: Most social media plugins are built for multiple platforms and include code for features you don't use, adding unnecessary weight to your site.

A pasted embed avoids all of these issues. There's nothing to install, update, or maintain at the WordPress level. The functionality lives entirely in a third-party service and loads from the snippet you paste once. For Webflow-specific implementation, see our Webflow embedding guide, and for Squarespace and Wix, the Squarespace guide and the Wix guide both walk the iframe snippet those two builders take.

One honest caveat, since this article is an argument against plugins and we publish one: CollectSocials has a WordPress plugin in the official directory, and on WordPress it is the better of the two routes for a reason that has nothing to do with convenience. The plugin copies your posts and your published design into your own WordPress database and renders them from your own domain, so once a feed has synced, a visitor loading that page makes no request to us at all and those page views are not metered on any plan, including free. The no-plugin path below is the right one if you are on Webflow, Squarespace, Wix or a hand-built site, or if you have a standing rule against adding plugins. It is a real choice rather than a fallback, and it is worth knowing which trade you are making.

How a Script Tag Embed Works (and Why It's Cleaner Than a Plugin)

When you install a WordPress plugin, it hooks into your site's PHP execution, makes database calls, and loads assets, all on your server. When you embed a third-party widget by pasting a snippet, the entire process happens on the client side, in the visitor's browser, after your page has already loaded.

On the hosts that take the script tag, the CollectSocials script is deferred, so it doesn't block your page from rendering: the LinkedIn feed appears after the main content, without holding anything up. It is one file that injects no further scripts, and it renders inside a Shadow DOM, so its CSS is isolated from your site and yours cannot leak into it. On Wix and Squarespace you get an iframe instead, and the isolation there is stronger rather than weaker, because a frame is a hard boundary in both directions.

For users who've dealt with plugin-induced site slowdowns, style conflicts, or white screen errors, this approach feels refreshingly clean.

Step by Step: Adding a LinkedIn Feed Without a Plugin

Step 1: Create Your CollectSocials Account

Sign up at CollectSocials for free, with no credit card. Free is a permanent plan rather than a countdown: one connected source and 2,000 page views a month, three sources through the 7-day trial, seven layouts, all sixteen themes, the theme builder, custom colours and custom fonts. A 7-day trial of the paid features runs alongside it, and when the trial ends your feed stays up on the free plan.

Step 2: Set Up Your Feed

Create a new feed in your dashboard. Name it something meaningful, such as your site name or "LinkedIn Feed".

Step 3: Connect Your LinkedIn Company Page

Add LinkedIn as a source. You authorise CollectSocials on LinkedIn's own consent screen and then pick your page from the list of company pages you administer, so there is no URL to paste and no API key to create: the authorisation is the connection. Company pages are the only LinkedIn source type, and every plan includes one LinkedIn source. CollectSocials imports your recent posts and keeps syncing new ones going forward, and the token behind that connection is refreshed for you.

Step 4: Curate Your Posts

In the Collect view you review the imported posts, and there are two ways to run it. The default is curation by exception: everything imported is live on the site, and rejecting a post is what takes it down. Turn on Pre-approve posts and the widget serves only what you have approved, so nothing reaches the page until you have looked at it. The second mode is off unless you switch it on, so decide which one you want before the snippet goes on a live page.

Either mode gives you the same editorial control in the end: filter out off-brand content, outdated posts, or anything that doesn't represent your company well in a website context. The difference is only what happens to a new post in the window before you have looked at it.

Step 5: Design the Widget

In the Design Studio, choose a layout and theme that fits your site. If you're replacing a plugin that had limited customization options, this is where CollectSocials provides a meaningful upgrade: forty layouts and sixteen themes, with toggle controls for dates, avatars, platform badges, and post text length. Every theme, the theme builder, custom colours and custom fonts are open on the free plan, so the plan decides how many of the forty layouts you can serve, not how well you can design them.

Step 6: Copy the Snippet for Your Platform

Make your feed public, then open the embed dialog and set "Where are you installing your widget?" to your platform before you copy anything. The dialog hands you the snippet that host can actually run: on WordPress, Webflow, React and hand-built sites that is a script tag, one line plus its container; on Shopify it is the same script wrapped in a page-width container so a theme's flex rules can't compress it; on Wix and Squarespace it is a self-resizing iframe; and on Notion or Google Sites it is a plain URL to embed. It is one copy and one paste in every case.

Step 7: Paste It Into Your Site, No Plugin Required

Where the snippet goes, and which one you get, by platform:

On WordPress (no plugin needed):

In the block editor, add a Custom HTML block wherever you want the feed to appear. Paste the script tag and update the page. That's the entire WordPress integration. No plugin installation, no database queries, no settings pages. (If you would rather have the plugin after all, it is in the official WordPress directory, and it is the route that takes your page views out of the meter once a feed has synced.)

If you want the feed to appear across multiple pages, paste the script tag into your theme's footer.php before the closing </body> tag, or use a theme that lets you add custom code globally (many modern themes and page builders offer this).

On Webflow:

Drag an Embed element onto your page canvas, paste the script tag inside, and publish. The widget appears wherever you placed the element. For global placement, use the Custom Code section in your Webflow project settings.

On Squarespace (iframe, not script):

Pick Squarespace in the embed dialog, add a Code Block to any page section, and paste the iframe snippet it gives you. Lower Squarespace plans strip custom <script> tags out of a Code Block, so the script embed works on some Squarespace accounts and renders nothing at all on others, with no error to tell you which one you are on. The iframe works on every plan and resizes itself to its content.

On Wix (iframe, not script):

Pick Wix in the embed dialog, add the Embed HTML element (Add, then Embed Code, then Embed HTML), and paste the iframe snippet into the Enter Code panel. Wix runs all custom code inside a sandboxed frame of its own, so a pasted script tag is not executing in your page's document and cannot mount the widget there. Our Wix guide walks the whole flow.

On Custom-Built Sites:

Paste the script tag into any HTML file, anywhere in the body. The widget renders into the container div that ships in the snippet beside it.

What About Performance?

Performance is often the primary reason people want to avoid plugins, and it's a legitimate concern. Here is what can honestly be said about the embed, which is architecture rather than a score:

The embed is one file: a single script that injects no further scripts, so the feed adds one request rather than a chain of them. It is deferred, so it does not block parsing and the feed renders after your main content. And it sets no cookies and no client-side storage, which keeps it outside the scope of your consent banner. You can confirm all three in your browser's DevTools in about a minute: filter the Network panel by JS, then check the Application panel before and after the feed loads.

What we will not do is publish a Lighthouse number for it. We measured the same page at anywhere from 79 to 100 in August 2026, and the only thing that changed between runs was whether a feed image happened to win Largest Contentful Paint above the fold. A score produced on our test page tells you nothing reliable about yours. If the feed sits below the fold, as it usually should, it is not competing for LCP at all.

Who This Approach Is Particularly Suited For

WordPress Sites With Many Plugins

If your WordPress site already runs twenty or more plugins, adding another social media plugin is a meaningful risk. Each additional plugin is another potential source of conflicts, slowdowns, and update headaches. A pasted snippet adds no plugin to that stack.

Webflow Sites

Webflow doesn't have a plugin ecosystem at all. Webflow sites extend functionality through embed elements and custom code, so a script tag is the native Webflow way to add third-party functionality and it integrates exactly as intended.

Sites on a Builder That Sandboxes Custom Code

Wix and Squarespace both restrict what pasted code may do, which is precisely why neither has a useful plugin story for a LinkedIn feed and why a hosted widget with an iframe snippet is the practical route on both. You are not working around the restriction; you are being handed the payload that respects it.

Sites Managed to a Performance Budget

If your site is held to a performance budget, the useful question is not which approach scores better on a test page, it is what each one adds. The snippet adds one deferred script file and no cookies. A plugin adds server-side execution, database queries and another dependency to keep updated. On WordPress specifically there is a third option worth weighing: our own plugin puts the posts in your database and serves them from your domain, so the visitor makes no third-party request for the feed at all.

Sites Managed by Non-Developers

A pasted embed is simpler to explain and implement than a plugin for non-developers. "Paste this here" is easier to follow than "install this plugin, activate it, configure the settings, authenticate your LinkedIn account, choose a widget, and embed the shortcode." If the person pasting it isn't the person reading this, the embed dialog has Copy instructions and Email this to your web person buttons that package the snippet together with where it goes, so what you forward is not a naked line of code.

Keeping It Running

Once embedded, the feed requires no maintenance at the site level. You review new LinkedIn posts in CollectSocials as they're imported, and a quick weekly check is typically sufficient. Your website keeps displaying the posts you have left in place. No plugin updates, no re-authentication, no compatibility issues.

If you ever want to change the layout or theme, update it in CollectSocials' Design Studio and the change reaches your website without a code change on your side. That is the part worth remembering: the snippet you pasted carries a feed id, not a design, so nothing you redesign later needs re-pasting.