Install ClauseClear on a custom HTML site

If you maintain your own HTML directly (or your CMS lets you edit raw HTML), this is the simplest path. Takes about 1 minute.

Shopify WooCommerce Wix Squarespace Custom / HTML

Before you start: have your ClauseClear merchant slug to hand from /dashboard. The slug looks like acme-ltd-a1b2c3.

1Open your T&C page’s HTML

In whatever tool you use to edit your site (VS Code, an IDE, a CMS’s “edit HTML” mode), open the source of your Terms & Conditions page.

2Paste the snippet before </body>

Find the closing </body> tag at the bottom of the page. Paste the snippet on the line above it:

<script src="https://clauseclear.co.uk/embed.js" data-merchant="YOUR-MERCHANT-SLUG"></script>

Replace YOUR-MERCHANT-SLUG with your real slug.

Example final structure:

  ...your T&C content...

  <script src="https://clauseclear.co.uk/embed.js" data-merchant="acme-ltd-a1b2c3"></script>
</body>
</html>

Save and deploy.

3Add to checkout / order summary too (optional)

To get the verified badge on your checkout page, add the same line (with the same merchant slug) to your checkout page’s HTML, also before the closing </body> tag.

The same script handles both contexts — it auto-detects whether it’s on a T&C page or a checkout page based on standard HTML markers.

4Verify it’s working

Visit your live T&C page. You should see:

An inline link saying “See the key terms you’d normally miss — Simpler Terms by ClauseClear →”
Clicking opens a modal with your audit summary.

Open your browser’s developer console (F12). If something isn’t working, ClauseClear logs initialisation messages there (e.g. [clauseclear] verified merchant: acme-ltd-a1b2c3).

5Common gotchas

Content-Security-Policy headers: if your site sends a Content-Security-Policy response header, add https://clauseclear.co.uk to both script-src and connect-src. Example minimal policy that works:
```
Content-Security-Policy: default-src 'self'; script-src 'self' https://clauseclear.co.uk; connect-src 'self' https://clauseclear.co.uk;
```
Subresource Integrity (SRI): we currently don’t publish SRI hashes because the embed.js content is updated frequently as we improve the modal. Don’t add an integrity attribute — the script will stop loading after our next deploy.
Async / defer: the snippet works either way. Adding defer is fine if you prefer.
Strict mixed-content (HTTPS only): ClauseClear is HTTPS-only. If your site is HTTP, upgrade to HTTPS first — modern browsers will refuse to load mixed content.

6If you use a static-site generator (Next.js, Astro, Hugo, Jekyll, etc.)

The same snippet works. Place it inside whatever component or template wraps your T&C page. Examples:

Next.js: use the <Script> component from next/script with strategy="afterInteractive".
Astro: drop the snippet directly into the page’s .astro file. Astro will hydrate it automatically.
Hugo / Jekyll: add to your T&C page’s front-matter or partial template.