Embed Instagram feed: single posts and multi-post feeds

Use a vendor's current approved route rather than scraping images or copying another site's code. Keep a plain profile link available when a display is unsupported or fails.

Embed an Instagram feed or one post?

Do not call a static copied gallery a live feed. Do not assume an official single-post embed by itself updates a list of later posts. Choose the task before selecting code.

Check eligibility and media rights

For one post, use the embed option offered by Instagram for that allowed content when it is available. If the embed control is absent, use a normal link. Do the same when the content does not permit embedding. Do not build a fake embed from copied media.

For a feed, read the chosen vendor's current account need. Squarespace and Wix now document professional-account rules for their respective feed routes. Those platform-specific rules should not be treated as proof that every vendor has identical support.

Confirm that the person connecting the account may use it for the website. Review the requested permissions in the official approval flow. Do not pass passwords or access tokens through a page editor or an email exchange.

Rights in the media remain a separate question. A public post can contain material whose reuse is restricted. Use the permitted display route and respect the source's attribution and content rules. A screenshot does not remove those limits.

Get the authorised Instagram feed embed

For a single post, use code supplied by the source's current embed control. Keep the original source link and required credit. Do not alter the content to imply a distinct statement or a business endorsement.

For a hosted feed, create the display in the planned vendor account and connect the supported Instagram profile. Check the account name and current allowed posts before copying the generated code.

Elfsight's Instagram feed page is a current hosted reference. Inspect its widget-specific plan and help for views, branding and refresh. A broad “free widget” headline is not an unlimited-use promise.

Keep public widget identifiers separate from secrets. A supported snippet may contain an identifier planned for the browser. It should not contain a private API credential that grants wider account access.

Place the code on the website

Use the documented route for your platform and plan. A frame, an external script and a native block can have distinct restrictions. Confirm that the chosen editor area supports the required code rather than pasting it into unrelated fields.

Keep a copy of the previous page setup. Place the display near context explaining why it is useful. Avoid making it the only location for key services, hours or contact details.

Record where the code lives. A site-wide injection and a page block can overlap. One planned source of installation makes later removal and diagnosis much clearer.

Save and publish, then inspect the signed-out page. Check the public page too. An editor preview does not prove that users can load the code or see the correct account.

Check keyboard, mobile and consent

On a phone, inspect the full display. Captions and controls should not require sideways page movement. If a post opens in an overlay, check the close control and the return to the original page.

Use a keyboard to reach the content and links. A grid should not trap focus or leave an invisible active control. Keep meaningful source links available without requiring a pointer-only action.

Review what the external display loads and the privacy details for the real route. Match the site's consent behavior to that setup. Do not copy a generic list of trackers into a policy without checking the real scripts.

Keep a profile link when the embed is blocked or declined. The page should still be useful without the external display. A user should not need to accept an optional feed merely to find a business contact route.

Refresh and reconnect

Compare the feed with the current source and the vendor's documented update behavior. Do not assume every route is real-time. A delay can come from the service's refresh cycle or the website's cache.

If the connection has expired or lost permission, use the vendor's current renewal steps. Confirm the planned profile afterwards. Authorising a distinct account may produce a plausible-looking but incorrect feed.

If the vendor shows current posts but the website does not, inspect the useful page and cache layer. If the source itself is unavailable, preserve the link fallback. Do not describe a vendor-wide outage without a dated official status source.

Platform-specific setup guides

Use the WordPress feed guide for plugin and hosted routes. Use the Shopify setup for theme apps, Squarespace setup for the current native block and Wix setup for the current app.

For a simpler decision, compare social media widget types. A plain source link can be the right answer when a feed adds upkeep without helping the page's task.

Keep the embed separate from page copy

Put the service explanation and source link in normal page content around the embed. That gives the visitor context even if the external display is blocked. Do not write an important booking condition only inside a post caption.

When the embed changes height or opens an overlay, check the next page control too. A visitor should still be able to read the service, close the display and continue. If that path fails, simplify the placement before adding more posts.

Continue with the right task

• facebook widget for website
• website widgets