Show the widget on every page
If the accessibility button appears on your home page but not on your other pages, the script tag was added to one page instead of to every page. This is the most common install problem, and the fix is the same in every case: the script has to load on every page, so it belongs in the one place your whole site shares — your global header or footer template.
The widget only runs on pages where the script tag is present. It does not "spread" to other pages on its own.
How you make the script load everywhere depends on how your site is built. Find your case below.
Case 1 — A CMS or site builder (WordPress, Shopify, Wix, Squarespace, etc.)
These platforms have one header/footer template that every page reuses. Put the script there once and it loads site-wide.
Use the platform guide for the exact place:
If your platform isn't listed, look in its settings for "custom code," "header/footer code," "code injection," or "add tracking/script to all pages," and paste the snippet there. When in doubt, Google Tag Manager injects the script into every page that has your GTM container.
Case 2 — Hand-coded static site with one HTML file per page
If your site is separate .html files (index.html, about.html, contact.html, …), each file has its own </body> — so pasting the snippet into index.html only covers the home page.
You have two options:
- Use server-side includes / a templating step. If your pages are built from a shared header or footer partial (an include, a layout, a static-site-generator template), add the snippet to that shared partial once and rebuild. Every page then carries it.
- Paste it into every page. If there is no shared partial, add the same snippet before
</body>in each.htmlfile. Tedious, but it's the only way without a template.
There is no setting in InclusifyX that adds the widget to pages where the script isn't present — the script has to be on the page.
Case 3 — Single-page app (React, Vue, and similar)
A single-page app loads one HTML shell and then swaps content as the visitor navigates, without a full page reload. Put the script in that one shell — index.html (or your framework's root HTML template) before </body> — and it's present for the whole app.
The widget detects in-app route changes and re-applies itself, so you do not need to re-inject the script on each navigation.
Framework specifics:
If the widget loads on first paint but seems to drop after you navigate within the app, see The widget disappears when I navigate my app.
Confirm it's site-wide
- Open three or four different pages of your site (home, an interior page, a deep page).
- The accessibility button should appear on each.
- If it's missing on a page, that page isn't loading the script — check that the page uses the shared template you edited.
Was this page helpful?