Display the Widget on One Subdomain Only
Overview
Want the accessibility widget to appear on just one subdomain — for example on shop.example.com but not on your main example.com? The widget shows up wherever its install snippet is placed, and its settings are tracked per subdomain. That gives you two clean ways to scope it: install the snippet only where you want it, or — if the same code is shared across your whole site — hide it everywhere else using Headless Mode. This guide covers both.
Who This Is For
Site owners who want the widget on a specific subdomain only
Teams whose site template is shared across the root domain and subdomains
Anyone who sees the widget appearing where they didn't intend
What You'll Learn
Why the widget appears where the snippet is placed
That widget settings are managed per subdomain
How to install the snippet on only the subdomain you want
How to use Headless Mode to suppress it elsewhere when the code is site-wide
How Placement Works
Two things determine where the widget shows:
Where the install snippet lives. The widget only loads on pages that actually include the AllAccessible snippet (or the AllAccessible plugin, for WordPress). No snippet on a page = no widget on that page.
Per-subdomain settings. AllAccessible tracks each subdomain individually, and each subdomain has its own widget settings and accessibility statement. So you can configure — and hide — the widget for one subdomain without affecting another.
The takeaway: scoping the widget to one subdomain is mostly about where you install the code, with Headless Mode as a backstop when the code is unavoidably shared.
Method 1: Install the Snippet Only on the Target Subdomain (Recommended)
This is the cleanest approach when your subdomains have separate templates or codebases.
Add the subdomain in your dashboard first if you haven't already — see Adding a Subdomain.
Log in to app.allaccessible.org and open the How to Install page to get your install snippet (or your account ID for the WordPress plugin).
Place the snippet only in the HTML of the subdomain you want covered — for example, on
shop.example.comonly, not onexample.com.Do not add the snippet to any subdomain where you don't want the widget.
Publish, then load a page on that subdomain to confirm the widget appears there and nowhere else.
📷 The How to Install page showing the copy-paste snippet
Because the widget only loads where the code exists, this keeps it entirely off the subdomains you skipped.
Method 2: Hide It Elsewhere With Headless Mode (When the Code Is Site-Wide)
Many sites share a single header, footer, or theme across the root domain and all subdomains. In that case the same snippet loads everywhere, and you can't simply "not install it" on one subdomain. Use Headless Mode on the subdomains where you want the widget hidden.
Headless Mode runs the accessibility scan and fix pipeline without showing the floating button or panel to visitors. It's a per-subdomain setting, so you can leave the widget visible on shop.example.com while hiding it on example.com.
Steps
Open the subdomain where you want the widget hidden (e.g.
example.com)Go to the Widget Settings tab
Scroll to the Advanced / Developer section
Turn on Headless Mode
Click Save Changes
Leave Headless Mode off on the subdomain where you want the widget visible
Changes typically apply immediately after saving; allow up to 30 minutes for cached widgets to propagate.
Important Trade-Off
With Headless Mode on, visitors to that subdomain cannot open the accessibility menu themselves (text size, contrast, text-to-speech, and so on) unless you provide your own way to open it. The automatic fixes still run. For the full explanation of this trade-off, see Stop the Widget From Showing to All Visitors.
Which Method Should I Use?
Your setup | Best method |
Subdomains have separate code/templates | Method 1 — install the snippet only where you want it |
One shared template loads across all subdomains | Method 2 — Headless Mode on the subdomains to hide |
You want the widget everywhere except one subdomain | Method 2 on that one subdomain |
Frequently Asked Questions
Q: Can I hide the widget on specific pages within a subdomain?
A: Headless Mode and other visibility controls apply at the subdomain level, not per page. For page-level control, you'd provide your own trigger and run in Headless Mode. See Stop the Widget From Showing to All Visitors.
Q: Do I need a separate account or subscription for each subdomain?
A: No. Subdomains live under one site. Add the subdomain in the dashboard, then place the snippet where you want it.
Q: If I use Headless Mode on a subdomain, do accessibility fixes stop there?
A: No. The scan and automatic remediation keep running. Headless Mode only hides the visible button and panel for that subdomain.
Q: The widget is showing on a subdomain where I never installed it. How?
A: That usually means a shared site template is loading the snippet everywhere. Use Headless Mode on that subdomain (Method 2), or remove the snippet from the shared template and install it only where you want it (Method 1).
Related Articles
Understanding Subdomains - How subdomains work in AllAccessible
Adding a Subdomain - Add a subdomain before installing
Stop the Widget From Showing to All Visitors - Headless Mode explained in full
Managing Multiple Subdomains - Per-subdomain settings
Need Help?
If the widget is appearing on the wrong subdomain and neither method resolves it:
Email: [email protected]
Include: the subdomain it should appear on, the ones it should not, and how the widget is installed (plugin or snippet)
Last Updated: July 2026
Applies To: Widget Settings (per subdomain)