How to Add a LinkedIn Feed to Your Website

Adding an Instagram or YouTube feed to a website is a solved problem. Both platforms expect it, and the tooling has existed for years. LinkedIn is not like that, and if you have been searching for a way to put your company page posts on your site, you have probably noticed that the advice is either vague, out of date, or quietly describes something LinkedIn does not permit.

The reason is worth stating plainly at the start. LinkedIn does not publish a feed you can read, and its API is a gated developer programme rather than an open door. Those two facts remove most of the options that exist elsewhere, and everything practical follows from working within what is left.

The good news is that the remaining routes are perfectly serviceable, and one of them tends to produce a better section than a fully automatic feed would have. This guide covers what LinkedIn permits, the four ways to get its content onto a page of yours, how to set the section up, and how to judge whether it deserves the space.

Why There Is No LinkedIn Feed to Point At

Feed output was once common across social platforms and has been withdrawn almost everywhere, LinkedIn included. The withdrawal was not an oversight. A feed lets content leave a platform with no authentication, no analytics and no way to bring the reader back, which is the opposite of what a platform whose value is its audience wants.

What this means for you is concrete. There is no URL you can paste into a feed reader, no address on your company page that returns XML, and no supported trick that resurrects one. If you find a service offering to hand you a LinkedIn feed URL, it is doing one of three things: using the official API with your authorisation, collecting the page automatically in a way LinkedIn does not sanction, or rendering content you supplied it.

The first is legitimate but limited. The second is worth avoiding, both because it breaches the user agreement and because it fails without warning. The third is honest and is what most sites end up using, once the alternatives have been examined.

What the API Actually Permits

LinkedIn does have APIs, and it is worth knowing where the boundaries sit before you spend a week on an integration that was never going to be approved.

• Access is granted, not assumed. You create an application and request access to specific API products. Approval is a review process, and the reviewer is looking for a genuine business case rather than a website that would like a nicer homepage section.
• It is scoped to organisations you administer. The route to a company page's posts runs through your admin role on that page. There is no supported way to read a page you do not administer, which rules out displaying a partner's or a client's feed.
• Personal profiles are a different matter again. An individual's posts are not available for general display, so a personal brand site cannot pull its owner's LinkedIn activity automatically. This surprises people more than anything else on the list.
• It is real engineering. Authentication, token refresh, error handling and a server to run it on. That is a reasonable investment for a product feature and a poor one for a section on a marketing page.

The practical filter is short. If you administer the page, have a developer, and need this to run automatically at scale, the API is the correct route. Otherwise it is not, and the rest of this guide is about the alternatives that do not require it.

The One Officially Supported Embed

LinkedIn supports embedding a single post, and it is genuinely useful for the case it fits.

1. Open the post on LinkedIn, either yours or a public one you want to reference.
2. Open the menu in the top corner of the post and choose the embed option.
3. Copy the iframe snippet LinkedIn gives you.
4. Paste it into your page where a block of content can sit.

What you get is the real post, rendered by LinkedIn, complete and current. What you also get is a third party frame on your page, which means an external request, a fixed layout you do not control, and a hole in the page if LinkedIn is slow.

Use it when one specific post deserves attention: an announcement referenced in a case study, a comment thread worth citing, a launch you are writing about. Do not use it as a way to build a stream. Ten embedded frames on one page is ten external dependencies for a section that would render as text in a fraction of the weight.

Four Ways to Get LinkedIn Content Onto Your Site

These are the realistic options once the constraints above are accepted. Most sites end up combining the second with an occasional use of the first.

The third column deserves explaining, because it is the one people miss. If the content you want to surface also exists somewhere you control, such as a newsroom, a blog or a changelog, that source almost certainly does produce a feed. Pointing a widget at your own feed and styling it in LinkedIn's idiom gives you an automatic section without touching LinkedIn at all, and the posts are usually the same posts.

Setting Up a Curated Section, Step by Step

This is the route most sites take, so it is worth doing properly rather than pasting three screenshots into a page.

1. Decide what the section is for before choosing posts. Credibility on a homepage, proof of expertise on a services page and hiring signal on a careers page need different posts. A section that tries to do all three does none.
2. Choose four to six posts. Enough to show a pattern of activity, few enough that a visitor reads them. The most recent posts are not automatically the right ones.
3. Pick the layout that matches the space. A list suits a sidebar, cards suit a full width block, a grid suits a section with room to breathe, and a ticker suits a single line near the top of a page.
4. Set the excerpt length deliberately. LinkedIn posts are long. Truncated to two lines they are pointless, shown in full they swamp the page. A few sentences with a link out is usually right.
5. Show dates, and keep them honest. A section of posts from eighteen months ago says something about your business that you did not intend to say.
6. Style it to your site, not to LinkedIn's brand. The visual idiom should read as professional posts, but the colours and type should be yours. A pasted LinkedIn blue block always looks bolted on.
7. Set a reminder to review it. The failure mode of a curated section is not that it breaks, it is that nobody updates it. A quarterly calendar entry costs nothing and prevents the entire problem.

On rhythm, be realistic rather than ambitious. A section reviewed once a quarter and kept genuinely good is worth more than one you promised to update weekly and abandoned in March. The review itself takes about ten minutes: read the current items as a stranger would, remove anything that has aged, and replace it only if something better exists. Leaving four strong posts in place is a legitimate outcome of a review.

One further decision is worth making now rather than later, which is what the section does when there is nothing to show. A curated block simply keeps its last set, which is fine. An automatic one can empty itself, and an empty box with a heading above it looks broken. Whatever you build, check what the page looks like with no items in it.

Company Page or Personal Profile

Almost every business hits this question within a day of deciding to add the section, and the permission rules make the answer less free than you would like.

Company page content is the safer foundation. It is the account you administer, it is the one an API route could eventually cover, and it is the one whose tone is already meant for an outside audience. The drawback is familiar to anyone who runs one: company pages are usually the quieter account, because the reach on LinkedIn tends to follow people rather than logos.

Personal profile content is often the better content and the harder case. An executive's posts carry more weight with a visitor than a company announcement, and they are also the content with no automatic route onto your site. In practice that pushes personal content firmly toward the curated approach, which is not a bad outcome: a chosen set of a founder's posts is a stronger page than an automatic stream of them.

Employee posts are a third category and need a word of caution. Displaying someone's professional posts on a company website is a reasonable thing to ask permission for, and an unreasonable thing to assume. Ask, and keep a note of who agreed, because people leave and the section outlives them.

The workable pattern for most sites: a curated set drawn from whichever account actually says useful things, whether that is the page or a person, with the source named on each item so a reader knows who is speaking.

Where the Section Belongs

The same block of posts helps on one page and distracts on another, so placement is a real decision rather than a matter of taste.

• Homepage, below the fold. Works as a sign of life for a visitor who is still deciding whether you are a real, current business. It does not belong above the offer.
• About page. The strongest fit on most sites. Someone reading an about page is explicitly assessing you, and recent activity is exactly the evidence they want.
• Careers page. Team and culture posts answer the candidate's real question, which is what it is like to work there, better than any paragraph you write yourself.
• Service or product pages. Only with posts about that specific service. A general feed here competes with the conversion path rather than supporting it.
• Not on checkout, signup or contact pages. Anywhere with one job, an outbound feed is a door out of the room.

One rule covers the placement question generally. Sections that build trust belong on pages where people are still deciding. Pages where people have already decided need fewer choices, not more.

What to Put in the Section

Assume a visitor gives it five seconds. What earns those seconds is not your most recent post, it is the post that answers the question they arrived with.

• Proof you do the work. A project shipped, a result described plainly, a problem solved. This is what a visitor comparing suppliers is looking for.
• A view worth having. A short, specific opinion about your field beats a reshared industry article every time. It is the only content on the page that could not have been written by a competitor.
• Company news that matters to an outsider. A funding round, a new office, a senior hire. Internal celebrations are for the platform, not for your homepage.
• Hiring signal, on the right page. Team and culture posts belong beside a careers page, where they answer a question someone is actually asking.

What to leave out is a shorter list and a more useful one: engagement bait, reposts with no comment of your own, anniversary badges, and anything that reads as talking to other people in your industry rather than to a customer.

Things Not Worth Doing

Four approaches come up repeatedly and each has a specific problem.

• Automated collection of LinkedIn pages. Against the user agreement, and technically brittle. The section stops updating one day and nothing tells you.
• Screenshots of posts as images. Unreadable on a phone, invisible to search engines, impossible to update, and often missing alt text. If you must use an image of a post, write real alt text describing what it says.
• Displaying follower or reaction counts you cannot verify. Numbers that came from somewhere unclear age badly and cost you more credibility than they buy.
• Embedding ten posts as ten frames. A page that makes ten external requests to render one section is slow in exactly the conditions where speed matters, which is a phone on a poor connection.

The general principle: if a shortcut depends on LinkedIn not noticing or not changing, it is not a shortcut, it is a maintenance task you have not scheduled yet.

Problems and Their Fixes

• The section shows nothing. Almost always the embed snippet sitting somewhere the platform strips scripts, such as a plain text field. Put it in a code or HTML block.
• It looks wrong on mobile. Card and grid layouts need width. On narrow screens a list is the layout that survives, and most widgets can switch by breakpoint.
• Posts are stale. If you curated the section, this is a calendar problem rather than a technical one. If you pointed it at a feed, check that the feed itself is still updating.
• Text overflows or truncates badly. Set an excerpt length instead of relying on the container to clip it, since clipping mid-word looks like a bug to a reader.
• Links go nowhere useful. Every item should link to the post it came from, opening in a new tab. A feed section with dead headlines is worse than no section.
• The page got slower. Measure before and after. Frames are heavy, rendered text is not, and this is the main practical argument for the curated route.

Accessibility and Page Weight

Two checks that take ten minutes and are almost always skipped on an embedded section.

Accessibility. Post text should be real text, not an image of text, which is the first reason to avoid the screenshot approach. Any avatar or post image needs alt text that describes it rather than repeating the author's name. Links need labels a screen reader can use, so an item that links out with the word "post" as its anchor tells a listener nothing. And the contrast of your chosen theme is your responsibility, not the widget's: a light grey timestamp on white passes nobody's test.

Page weight. Anything that renders in a frame carries the other party's stylesheet, script and fonts, and it loads whether or not the visitor scrolls to it. If the section sits low on the page, defer its loading until it is near the viewport, which most modern embeds support in one attribute. Then measure the page before and after on a phone connection rather than on your desk, because the desk always says it is fine.

Neither check takes long, and both matter more on the pages where the section is most useful, which tend to be the ones a stranger reaches first.

Is It Earning Its Place?

A social section is easy to add and easy to forget, so decide up front how you will know whether it is working.

The honest measures are behavioural. Does anyone click the posts. Do visitors who see the section go on to the pages that matter, such as pricing or contact. Does the section appear on pages where people are deciding, rather than on pages where they are arriving.

If nobody clicks and nobody stays, the answer is usually the content rather than the format: five carefully chosen posts about work you have done will outperform twenty automatic ones. And if the section exists mainly to prove you are active, be honest about the fact that a stale section proves the opposite. Our guide on using social media to increase website traffic covers the wider question of what social content on a site is actually for, and if all you need is a set of well-placed profile links rather than a feed, social media link widgets are the lighter answer.

Getting Started

The short path, for a site that does not have a developer to spare. Decide which page needs the section and what it is meant to prove. Choose four to six posts that prove it. Render them in LinkedIn's visual idiom with a layout that suits the space, dates visible, links opening out. Reserve the official single post embed for the occasions when one specific post deserves to be shown in full.

If the content you want also lives somewhere you control, point the widget at that feed and let it update itself. Either way, a LinkedIn feed widget handles the layout, the refresh and the styling, so the only ongoing work is choosing what deserves to be there.

Other platforms are easier than this one, and the differences are worth knowing before you build a second section: YouTube publishes a real feed and so does Tumblr.