Other platforms and the script tag
We checked each platform's own documentation (on 2026-10-29) for a way to add the script tag to every page. This page says what that documentation confirms. It does not mean we have run our loader on these platforms: OPEN. The dashboard shows no guide for them.
Use the script tag from your dashboard's install page. The table says where it goes.
| Platform | Where the documentation says to add it | Limits the documentation states | Not confirmed |
|---|---|---|---|
| Framer | Project Settings, Custom Code tab; all pages or chosen pages | Not loaded in the editor preview; publish and test | Plan requirement and whether data-* attributes are kept: verify |
| Ghost | Settings, Advanced, Code Injection, site header | Header code is on every page | Plan requirement and whether data-* attributes are kept: verify |
| BigCommerce | Script Manager, scope Storefront pages | Stencil themes only. Checkout and account pages need an integrity hash that breaks when the file changes, so do not choose all pages | Plan, data-* attributes, hreflang: verify |
| Magento / Adobe Commerce | Content, Design, Configuration, store view, HTML Head, Scripts and Style Sheets | Payment pages enforce a content security policy from 2.4.7; the loader address must be allowed in a module | data-* attributes. Adobe Commerce as a Cloud Service has a different storefront and is not covered: verify |
| Drupal | A library in your theme (libraries.yml) with type: external, header: true and attributes for async and data-* | Attached through the theme, so the admin theme needs it separately | Content security policy modes: verify |
| Joomla | An entry in the template's joomla.asset.json with attributes for data-* | Applies to the template that uses it | Head placement, async: verify |
| HubSpot CMS | Settings, Content, Pages, domain, Site Header HTML | Available on all plans, with options that vary by plan and content type | Which page types are excluded: verify |
| WooCommerce | Use the WordPress plugin | The Cart and Checkout blocks are drawn by script; whether the loader reaches their text is not documented | Block translation: OPEN |
| Weebly | Not found in Weebly's own documentation | Everything: OPEN | |
| Duda | Official pages could not be opened | Everything: OPEN | |
| Google Tag Manager | A Custom HTML tag | Tag Manager loads before our loader does, so first-paint flicker is likely. Wix says Tag Manager does not work through custom code | Timing and data-* attributes: OPEN |
Platforms with their own languages#
Several platforms translate by themselves with real language addresses: Wix Multilingual, Webflow Localization (paid add-on), Shopify Markets, HubSpot language variations, Drupal's content translation, Magento store views, and translation plugins on WordPress. Prefer them when search traffic matters. Do not run two translators on the same page. See SEO and the script tag.
Frameworks and hosts#
See single-page apps, Next.js, Nuxt, Astro and static sites. SvelteKit and Gatsby can add a script (app.html, gatsby-ssr); we have no kit for them and have not run the loader there: OPEN.