If your Juicer feed isn't showing on your website—or changes you make in the dashboard don't appear on your live page—the most common cause is an outdated embed code on your site. This guide explains how to spot it and fix it.
How to tell this is your problem
The signs look different from the surface, but they all point to the same issue:
You change a setting (layout, filter, "open overlay on post click", post style) and it saves in the dashboard, but nothing changes on your website.
Your feed used to work and now shows nothing, or just a blank container.
You reconnected a social source (after a token expired, a password change, or an Instagram security check)—Juicer shows it syncing, but your site still doesn't show new posts.
The feed renders correctly inside your Juicer dashboard preview, but not on your live site.
You updated the design or template and your website still shows the old look.
If any of these match, read on.
Why this happens
Juicer has moved to a new feed engine (Feeds 2.0). Our modern feeds don't render with the older two-file embed snippet that was used on many sites for years. As long as your website still loads the old script, none of your dashboard changes—new designs, new posts from reconnected sources, setting toggles—can show up.
The legacy embed looks roughly like this. Check your website's page source for any of these three lines:
<script src="//assets.juicer.io/embed.js" type="text/javascript"></script> <link href="//assets.juicer.io/embed.css" media="all" rel="stylesheet" type="text/css" /> <ul class="juicer-feed" data-feed-id="YOUR-FEED-SLUG"></ul>
If you see a <script> pointing at assets.juicer.io/embed.js, a <link> for embed.css, or a <ul class="juicer-feed"> wrapper, you're on the old embed and need to update it.
How to fix it
Fixing this takes two things, and both are required—doing only one won't make the feed appear.
Step 1 — Contact Juicer support to enable the v2 embed script on your feed
The new rendering is controlled by a per-feed flag on our end. Until we flip it on for your feed, the updated script keeps serving the old version—even if you already have the new snippet on your site.
⚠️ Important: if you open the Embed button in your dashboard today, you'll already see the new single-line snippet there. That's expected—every account shows it regardless of which version is active on the server. Copying it to your site on your own won't fix the problem by itself, because the URL in that snippet will still serve the legacy rendering until we enable v2 for your feed. So please reach out to us first, and we'll flip the switch.
Step 2 — Replace the old code on your website with the new single line
Once we've confirmed v2 is enabled for your feed, grab the snippet from the Embed button in your dashboard (or copy the one below and swap in your feed slug):
<script type="text/javascript" src="https://www.juicer.io/embed/YOUR-FEED-SLUG/embed-code.js" async defer></script>
This one line replaces all three pieces of the old embed—the <script>, the <link> stylesheet, and the <ul class="juicer-feed"> wrapper. Remove all of them when you swap the new code in.
After step 2 is deployed to your website, the feed will render with the new engine and every dashboard change will start reflecting on your live page.
Verify it's working
Once the code is updated and v2 is enabled:
Hard refresh your page (
Ctrl+Shift+Ron Windows,Cmd+Shift+Ron Mac).Try the page in an incognito or private window to rule out your own browser cache.
If your site runs on a CDN, a caching plugin (common with WordPress, university sites, and enterprise hosting), or a corporate cache layer, ask your web team to purge it.
View the page source one more time—you should see exactly one Juicer script line, with no
embed.csslink and no<ul class="juicer-feed">wrapper.
Still not working?
If you've swapped the code, cleared every cache, and still see nothing, reach back out with:
The live URL of the page where your feed should appear.
A screenshot of your browser's JavaScript console on that page (how to open the console).
There may be a secondary issue—a jQuery conflict, an iframe embed, a content-security-policy rule—that's separate from the embed version. With those details we can pinpoint it quickly.