Social feeds
Social media widget: choose a feed, link or embed
Last updated · A-Widget
On this page7
Social media widget types: icons, posts and feeds
Use an icon or text link when the user should go to the source. An allowed official post embed can show a specific item in context. Choose a permitted multi-post feed when a current sequence of content has a clear job.
Keep the website's main details independent of the widget. A social connection can expire or be blocked. Visitors should still find the business's service, contact route and key terms.
Network-by-task reference
| Network or source | Simple link | Embedded display to inspect | Condition to verify |
|---|---|---|---|
| Public profile or post | Eligible single post or supported account feed | Current account type, source permission and refresh | |
| Public Page or post | Current supported Meta or authorised provider route | Page eligibility and current display support | |
| Another social network | Correct source address | That network's own supported route | Separate terms and account requirements |
| Several networks | Clearly labelled source links | Provider-supported aggregation | Each source's permission and actual package scope |
Check Facebook Page eligibility in Meta’s current account controls before choosing an embed. If you cannot confirm support for your Page, use a normal Page link. Do not substitute an old snippet or scraped copy for a supported connection.
Choose your account and permission route
Identify the account that owns the content and the person who can authorise it. A website editor may not own the social profile. Keep login work in the official flow and review the requested access.
Read current platform-specific rules. Squarespace's Instagram guide and Wix's current app guide describe professional-account routes. Do not generalise their controls to every vendor.
For a hosted service such as Elfsight, inspect the exact widget and plan. A package may count views separately from posts or connected accounts. Unknown support should remain not verified rather than be turned into a universal feature claim.
Place and check the social media widget
Use the current supported block, app or code for the website. Confirm the platform plan permits the required script or frame. Record the installation location and keep the old page setup for rollback.
Open the live page while signed out. Check source identity, attribution and destination links. A correct-looking grid can still display the wrong account if the installer manages several profiles.
On a phone, inspect readable captions and controls. Use the keyboard to enter and leave any popup. Avoid a floating display that covers the page's main action.
Keep the site's privacy details aligned with the real external loading. A user may block or decline the display. Provide a normal source link and preserve the page's key content.
Refresh and failure fallbacks
Compare the current source with the vendor's documented update behavior. Do not assume real-time refresh. A delayed display can be a source-connection issue, vendor refresh or website cache.
If a connection expires, use the current vendor renewal route and confirm the profile afterwards. If support is not established, use a plain link. Do not scrape posts or copy reviews to simulate an unavailable connection.
Record a dated observation before claiming an outage. A blank widget on one browser is not proof that a whole network is down. Check a safe listed view and the vendor's official status source where available.
Find the right setup guide
Use the Instagram embed guide for post-versus-feed choices. Use the WordPress guide for plugin placement and the Facebook guide for that network's separate limits.
Decide what a mixed feed promises
A combined grid can mix posts from several accounts without making their ownership obvious. Label each source so readers can distinguish the business’s own posts from a partner’s content. Do not title that grid “our latest posts” if some items belong to someone else.
Before combining networks, define the order you want: publication time, a curated selection or one group per source. Confirm the chosen service supports that order. A sequence that looks chronological can mislead if one network refreshes more slowly than another. Use a neutral heading when freshness is uncertain, and avoid a claim that every new item appears immediately.
Keep the fallback tied to each source. If only one connection expires, show its labelled profile link rather than replacing the whole grid with copied screenshots. Visitors can still reach the original material without mistaking a frozen image for a connected feed.
Continue with the right task
FAQ
Does an aggregator remove network rules?
No. Each source still has its own permissions, account rules and content rules. Inspect the vendor's supported route for each network and the exact package you plan to use. A multi-network label does not prove permission to copy any public post or review.
What is the simplest useful fallback?
A clearly labelled link to the correct profile, Page or post can remain useful when an embed fails. Keep key business and contact facts on the website itself. Do not show copied content as though it were a current connected feed.