Smash Balloon fetches your Instagram feed through Instagram's API server-side, caches it in transients, and renders it as a shortcode or block — plain HTML by the time a crawl captures it, so the feed itself is served static. The one thing to plan around: under static hosting there's no live WordPress request left to refresh that cache, so the feed freezes at exactly what it looked like during the last build. Keeping it current is entirely a matter of scheduling rebuilds often enough — there's no live client-side refresh built in.
Static + Bridges
The rendered feed markup — whatever photos and captions were fetched as of the last build — is captured as a static fragment and served from the static release like any other content.
None needed for display; connecting the Instagram account and configuring feed layout/settings happens entirely in wp-admin, with no public-facing exposure at all.
None — the feed is treated as a static fragment baked in at build time, not a live bridge route. There's no mechanism to refresh it between builds short of rebuilding.
No special setup — detected automatically once active. Since the feed only updates on rebuild, make sure your rebuild schedule matches how fresh you need Instagram content to look.
The single most important thing to know: because there's no live WordPress request behind a static release, the feed cannot refresh itself — it stays exactly as fresh as your last build, however long ago that was. If Instagram content needs to look current, schedule rebuilds often enough (daily, or more for an actively-posting account) to match — this adapter does not provide a live client-side refresh or bridge route for it. This classification is also based on Smash Balloon's well-documented general architecture (API fetch, transient cache, shortcode/block render), not on behavioral validation against a live install.
Static Shield Lite is free to install and inspects your actual plugins, not just what's publicly visible.
Get Static Shield
Tulapp