Skip to content
Help Center
Log in Sign up free

Your platform is not in the guides

We have step-by-step guides for the most common platforms. Everything else follows the same three-part pattern, and almost every builder has the two places you need.

Platforms customers regularly ask about that are not yet in the guides: IdoSell, DUDA, Subbly, MODX, Mobirise, plus most self-built sites.

What you are looking for

  1. A place for site-wide code, ideally injected before the closing </body> tag.

    Depending on the platform it is called: Custom code, Code injection, Site-wide code, Header and footer scripts, Tracking code, Custom HTML in the theme. Put part 1 and part 2 of the snippet there.

    If the only field available is in the <head> rather than the footer, use it. The widget still works, it is only slightly worse for page speed.

  2. A place for an HTML block on the page where the reviews should appear.

    Called: HTML block, Custom HTML, Embed code, Raw HTML, Code widget. Put part 3 there.

That is the whole job. If your platform has both, the widget will work.

If there is no site-wide code field

Some closed builders on cheaper plans do not allow custom scripts at all. Then put all three parts into one HTML block on the page where the widget should appear. It works, with two caveats: the widget only exists on that page, and if you add several such blocks the library loads more than once, which can break rendering.

After installing, always check these

  1. Your domain is in the whitelist in Settings, matching what visitors actually type, including or excluding www as appropriate.
  2. The container from part 3 is present on the page you are looking at. The library alone renders nothing.
  3. You are looking at the live site, not the editor preview. Most builders do not run custom code in the editor, and the whitelist blocks it there anyway.
  4. The cache is cleared, both the platform’s and any CDN in front of it.

Full checklist: widget still not visible and the JavaScript reference.

Builders that serve custom code from an iframe

Some builders, Wix being the known case, run your code inside an iframe hosted on their domain, not yours. The whitelist then sees their domain and blocks the widget. Two ways out: whitelist that host, or clear the whitelist so the widget runs anywhere. Details in the Wix guide.

If you hit this on another builder, the symptom is the same: everything looks correct and nothing renders. Write to us with your site address and we will tell you which host to whitelist.

Want a guide for your platform?

Write to [email protected] with the platform name. If several customers use it, we will add a guide with screenshots. Send the names of the two fields you found and it gets written faster.