Add Instagram feed to WordPress: plugin and embed routes

Use a small, clear placement that supports the page. Keep key business facts in normal website content. A user should still find your contact details and services when the external feed cannot load.

Check Instagram account and permissions

Identify the Instagram account that owns the content and the person allowed to connect it. A website editor may not have that account access. Do not ask someone to send a password or access token by email as a shortcut.

Read the current account rules for the chosen connection. Instagram platform changes have affected older personal-account routes. Use the vendor's current guide rather than a tutorial that assumes an old connection still works.

For the plugin route, the Smash Balloon Social Photo Feed listing is a current WordPress reference. It names the plugin owner and listed setup. For a hosted route, inspect Elfsight's Instagram feed help and current plan rules.

Review the requested permissions before authorising. Connect only the planned account. Sign-in is only one step. Check that the widget reads the profile the website represents.

Media rights remain separate

Access to an account does not settle every right in a post. A business may own its image. That does not settle rights to music, user images or other material shown with it. Check the rights for this use. Keep rights and privacy in view when choosing what to display.

Do not scrape a feed or copy another account's photos to imitate a connection. Use the platform's permitted embed or a vendor's supported approved route. If permission is unclear, a plain link to the profile can be a more suitable option.

Add an Instagram feed to WordPress: plugin or hosted embed

Choose the plugin route when the owner wants the feed managed in WordPress and can maintain the plugin. Choose a hosted route when the vendor's account and plan are a better fit. Neither choice shows that every post type or account is supported.

A single-post embed is a distinct task from a feed. It displays a chosen item rather than maintaining a list of recent content. The embed guide explains that distinction.

Compare current plan limits

Check views, displayed posts, refresh behavior and branding for the real product. A free trial is not an ongoing free plan. A general “free widget” headline does not prove unlimited use or every layout.

For Elfsight, inspect the widget-specific plan as well as broad pricing. A page load or widget view can have a vendor-defined meaning. Do not compare that unit directly with Instagram followers or the number of posts in the source account.

Keep unknown values not checked. If a current source does not prove a refresh interval or post limit for your account, do not invent one. The useful decision is whether the documented scope supports your page's task.

Connect the account safely

Follow the vendor's current approval flow. Use the account that owns the planned profile and review the requested access. Keep login work inside the official platform or supported vendor flow.

Confirm the account name after connection. Check a recent allowed post and the source link. A feed connected to the wrong profile can look plausible, especially when several business accounts use similar images.

If the connection fails, retain the error and inspect the current account rules. Do not repeatedly create new widgets or grant broader permissions without knowing the cause. A changed platform rule and a wrong account are distinct problems.

Record who can renew the connection. Password changes, permission changes or account changes may affect it. A website contractor's temporary access should not be the only route to future upkeep.

Place the Instagram feed on WordPress

For a maintained plugin

Verify the current plugin listing, publisher and supported site rules. Use a safe backup or site copy before changing a working installation. The plugin name alone does not prove it is the vendor's official route.

Create the feed using the plugin's current instructions and connect the supported account. Then place the generated block, shortcode or supported widget through the route the vendor documents. Do not guess a shortcode from another plugin's tutorial.

Keep one planned placement while checking it. A feed in both a page block and a site-wide template may duplicate content or create needless loading. Record where the plugin's display is inserted.

For a hosted embed

Create the feed in the correct vendor account and use its current embed code. Confirm that your WordPress route permits the required script. Hosted WordPress plans can differ from self-hosted WordPress in plugin and code permissions.

Place the code only where the platform and vendor allow it. Keep secret credentials out of page source. A public widget identifier used by a supported embed is not the same as an API access token.

Save and publish through the normal editor. Open the signed-out page rather than relying only on the administrator preview. The public result is the one visitors use.

Check refresh, mobile and media rights

Confirm the correct profile and source links. Compare a recent allowed post with the feed, allowing for the vendor's documented refresh behavior. Do not call the feed broken simply because it is not real-time.

Inspect a phone layout. Captions, controls and links should remain readable. Check the size of each post and control. Fewer, clearer posts can serve the page better than a cramped row.

Use the keyboard to reach the feed and follow a post link. If an item opens in an overlay, check closing and focus return. A visual grid should not trap someone who cannot use a pointer.

Review the chosen content for rights and personal details. A social post being public does not make it suitable for every page. Remove or exclude a display through the vendor's supported controls where needed, without misrepresenting what the source contains.

Keep a useful fallback

Place a clear profile link near the feed. Label the destination so users know it opens Instagram. If the feed fails, the link still leads to the source. It does not claim that the website holds a current copy.

Keep opening hours, service descriptions and key notices outside the feed. A connection problem should not make a user depend on a social account for key business facts. Normal website content is the reliable baseline.

Fix connection and caching problems

Identify the route first: native plugin, hosted embed or single post. The repair path differs. Check the live page, vendor account and source account before changing code.

If the account is disconnected, use the vendor's current renewal steps. Verify the planned profile after renewal. Do not assume another approved account has the same content or permission.

If the vendor shows current data but WordPress shows old data, inspect the site's cache and any documented plugin cache. Change that layer rather than clearing unrelated systems. Keep a record of the last observed source post and display state.

If the feed is absent, check publication, code permissions and blocking extensions in a controlled way. A script can be held by consent or blocked by the browser. Preserve a normal profile link while investigating.

Remove without losing the source account

Remove the known display block or embed from the page and inspect the public result. Disable the vendor connection only through the supported account controls. Removing website code and deleting Instagram content are distinct actions.

If you replace the vendor, keep the current route until the new one is checked. Then remove the old code so the page does not load both. Handle any plan separately from the visible placement.

Check where each kind of post link leads

Use a recent allowed post to inspect the link behavior. Open it from the public WordPress page and read the destination profile. Then return and close any overlay. Keep the user able to reach the normal page links after that action.

If the feed includes more than one post format, inspect each format you plan to show. A photo card, video card and long caption may have different space needs. This is a check of your chosen setup, not a promise that every format is supported.

If a format does not fit, use the vendor's supported display choices or a simpler source link. Avoid adding a custom player around copied media merely to keep the same visual layout. The fallback should preserve a truthful route to the source.

More in this guide

Choose your platform: Shopify, Squarespace or Wix. For a broader choice, read Instagram widget types and the social media widget reference.

The Squarespace feed troubleshooting guide separates native and hosted connections. The Facebook widget guide covers a distinct network and does not assume Instagram permissions apply there.

Keep the source and website jobs distinct

For a fictional studio, Instagram may hold recent work while WordPress holds services and contact details. The feed helps show the recent work. It should not become the only place where a user can find the studio's address or booking route.

If the social connection stops, the site should still answer the basic service questions. Leave a clear profile link for recent posts. Do not fill the empty feed with copied old items while calling it current.

When the account changes, verify the new source before restyling the display. A new owner or profile can need a fresh approval flow. Confirm the exact account name and post links, not just the presence of images.

This division keeps the site useful through a connection fault. It also makes upkeep clearer: the source owner manages social content, while the site owner manages page placement and the fallback.

Review the fallback after a theme edit

A theme change can remove or bury the plain profile link while leaving the feed code intact. Check both after the edit. The fallback is useful only if a user can find it when the external display fails.

Assign a source owner before launch

A site editor may manage the page while someone else owns the social account. Record who can renew that connection. If that person leaves, use the vendor's supported access process rather than sharing an old password. The fallback link and ordinary service content should remain usable while the account owner restores the feed.

Continue with the right task

• small business chatbot needs pain points
• website widgets