SiteAccessible
Dokumentacija

Platform install guides

WordPress, Shopify, Wix, Squarespace, Google Tag Manager, React, Next.js and Vue.

5 min branjaPosodobljeno

Dokumentacija je napisana samo v angleščini.

The snippet is plain HTML, so it works anywhere you can add a script tag. These are the routes people ask about most often.

WordPress

  1. Appearance → Theme File Editor → header.php, and paste the tag before </head>.
  2. Or, safer against theme updates: install any header-and-footer-scripts plugin and paste it into the header field.
  3. Block themes: Tools → Theme File Editor is unavailable, so use the plugin route.

Shopify

  1. Online Store → Themes → ⋯ → Edit code.
  2. Open layout/theme.liquid.
  3. Paste the tag immediately before </head> and save.

Wix

  1. In the site dashboard open Settings → Custom Code (under Advanced) and choose Add Custom Code.
  2. Paste the tag, set Add Code to Pages to All pages (Load code once) and Place Code in to Head, then apply.
  3. Wix only runs custom code on a Premium plan with a connected domain, so add that domain to the site in SiteAccessible.

Squarespace

  1. Open Code Injection: Settings → Advanced → Code Injection, or in newer dashboards Website → Website Tools → Code Injection.
  2. Paste the tag into the Header field and save.
  3. Code injection is only available on Squarespace plans that include it (not Personal).

Google Tag Manager

Create a Custom HTML tag containing the snippet, and fire it on All Pages. Leave document.write unchecked.

Next.js (App Router)

app/layout.tsx
import Script from "next/script";

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html lang="en">
      <body>
        {children}
        <Script
          src="https://siteaccessible.com/w/YOUR_SITE_KEY.js"
          strategy="afterInteractive"
          crossOrigin="anonymous"
        />
      </body>
    </html>
  );
}

React and Vue SPAs

Add the tag to the static index.html rather than mounting it from a component. The widget attaches itself to the document, so it survives client-side route changes and does not need to be re-initialised.