If your embedded Juicer feed isn't loading on your website, work through the checks below. They're ordered from quickest to most involved.
Basic checks
Verify the embed code is placed correctly on your page.
Open the page source and confirm the Juicer code is actually present in the rendered HTML.
Open your browser's JavaScript console and look for any error messages.
Finding your embed code
Open your Juicer dashboard.
Click the red Embed button in the top-right corner of your feed dashboard.
For WordPress sites, you can also install and activate the Juicer WordPress plugin instead of pasting the embed code manually—both approaches work.
Local development
When you preview a page locally by opening the .html file directly (a file:// URL), the standard protocol-relative embed (//assets.juicer.io/...) usually works in modern browsers but isn't guaranteed. If it doesn't load locally, you have two options:
Run a local HTTP server. The simplest is Python's built-in one (example setup), but any local server works.
Force the embed to use HTTP explicitly:
<script src="http://assets.juicer.io/embed.js" type="text/javascript"></script><link href="http://assets.juicer.io/embed.css" media="all" rel="stylesheet" type="text/css" /><ul class="juicer-feed" data-feed-id="YOUR_FEED_NAME"><h1 class="referral"><a href="http://www.juicer.io">Powered by Juicer</a></h1></ul>
⚠️ Important: the HTTP-only version will be blocked as mixed content on HTTPS sites once you deploy. Switch back to
//assets.juicer.io/...(orhttps://) before going live.
Single page application support
In single page applications—including React, Vue, Next.js, Angular, Magento/Adobe Commerce, and SharePoint—the page never reloads when the user navigates between routes, so the standard embed (which initializes once on document.ready) may never fire on the route where your feed lives. The fix is the delayed-initialization version of our embed (also known as the AMD build):
Replace the standard script tag with the AMD version:
<script src="//assets.juicer.io/embed-amd.js" type="text/javascript"></script>
Manually trigger the feed when your component or route mounts, and tear it down on unmount:
Show feed:
Juicer.initialize()Hide feed:
Juicer.remove()
For RequireJS-based setups, see Using Juicer with RequireJS.
Other common causes
If the embed code is placed correctly and your dashboard preview works, the issue is most likely on the page itself or in the visitor's browser:
Content Security Policy (CSP): a strict CSP header can block
assets.juicer.ioscripts and styles from loading. Addassets.juicer.ioandjuicer.ioto yourscript-src,style-src, andconnect-srcdirectives, plus your social platforms (e.g.*.cdninstagram.com,*.fbcdn.net) toimg-src.Ad-blockers and privacy extensions: uBlock Origin, AdGuard, and similar tools sometimes block embedded social feeds. Test in a clean browser profile, in a private/incognito window, or with extensions disabled to confirm.
Third-party cookie blocking: some browsers (Safari by default, Firefox in strict mode, Brave) block third-party requests, which can affect rendering of certain post types. The feed itself still loads, but interactive elements (overlays and video) may fail silently.
Earlier JavaScript errors on the page: any unhandled JS error before our script runs can stop the feed from initializing. Fix the earlier error, and the feed usually appears.
Browser cache or CDN cache: after updating the embed code, clear your browser cache and any site/CDN cache (Cloudflare, Fastly, or your CMS) so the new code is actually served.
Last resort: iframe
If none of the above resolve the issue, switch to the iframe embed. The iframe version isn't mobile-responsive, and post overlays don't work, but it sidesteps almost every issue listed above:
Open your Juicer dashboard and select the feed you're embedding.
Click the red Embed button in the top-right corner.
Switch to the iframe tab and copy the code from there.
If you've worked through everything here and your feed still isn't loading, please contact us with the URL of the page where you've embedded the feed and we'll take a look.