Website monitoring
Install the website monitoring script
Choose the right installation method, add the generated script once, and verify that DocAccessible can see it in your public page source.
- For
- Website administrators, developers, and agency partners
- Typical time
- 10-30 minutes
Before you start
- A connected website in DocAccessible
- The exact installation code copied from that website's Installation tab
- Permission to publish site-wide code on the connected public domain
Procedure
Step by step
Open the connected website
In Website monitoring, select the domain you are installing and open Installation. Do not reuse code from another connected website because every domain has a different public site key.
Copy the complete generated tag
Choose Copy installation code. Keep the script URL, async attribute, and data-site-key exactly as generated.
Choose the global installation point
Use your CMS's site-wide Footer or Body - end code area, the shared server-rendered layout, or the active theme's supported asset system. Add the tag once, not once per PDF.
Publish the website change
Save and publish the real production site. Clear application, CMS, host, and CDN caches when they can continue serving older HTML.
Open a public page on the connected domain
Visit a normal public page that includes the script. This first browser report starts verification and provides the exact page that DocAccessible will fetch.
Confirm source and connection status
Use View page source and search for your data-site-key. Then return to Installation and wait for Script connected. Only after verification can scheduled checking and approved visitor mappings operate normally.
What the generated code looks like
The example below shows the shape of the tag. YOUR_SITE_KEY is only a placeholder. Always paste the exact code from the connected website so the service origin and key match your workspace record.
<script async src="https://docaccessible.com/site/v1.js" data-site-key="YOUR_SITE_KEY"></script>Choose your platform
Select the system that produces the public website. If an agency, managed host, or custom theme controls the final HTML, send them the custom-site guide together with the generated tag.
- WordPressUse a site-wide code tool or a child-theme hook without editing the parent theme.
- ShopifyAdd the generated tag to theme.liquid and keep the change with the active theme.
- WebflowUse site-level Footer code, publish the site, and verify the custom domain.
- WixAdd custom code to every page at Body - end and confirm it survives publication.
- SquarespaceUse site-wide Footer code injection on an eligible plan.
- Drupal or JoomlaInstall through the active theme or the CMS asset manager and clear caches.
- Custom HTML, React, Next.js, and server frameworksPlace the script in the shared server-rendered layout so it appears in page source.
- Google Tag Manager and client-only injectionUnderstand why runtime-only tags cannot complete verification and choose a supported route.
The page-source check that matters
DocAccessible does not treat a browser request alone as proof that you control the domain. Its worker fetches the reported public page and looks for the official script URL with the exact site key in the returned HTML.
- Use View page source, not only the browser Elements panel.
- Search for data-site-key and compare the complete value with the Installation tab.
- Confirm the page URL uses the same connected host and HTTPS origin.
- Do not install only through a tag manager, useEffect, or another client-only loader.
Content Security Policy
A restrictive Content Security Policy must allow the exact DocAccessible origin shown in your generated tag. Merge the origin into the existing directives; do not replace the website's complete policy with this example.
- script-src permits the browser to load /site/v1.js.
- connect-src permits inventory reports and approved viewer requests.
- img-src permits images in an approved accessible viewer.
script-src 'self' https://docaccessible.com;
connect-src 'self' https://docaccessible.com;
img-src 'self' data: https://docaccessible.com;If verification does not complete
Start with the source check because it separates publishing problems from network or policy problems. After each correction, open a fresh public page and return to the Installation tab.
- Wrong key: remove old or duplicate tags and paste the current connected website's code.
- Missing from source: move the tag from a client-only component into the CMS global code area or server-rendered layout.
- Old source: purge page, host, reverse-proxy, and CDN caches, then reload in a private window.
- Blocked request: inspect the browser console for Content Security Policy, extension, consent, or network errors.
- Wrong host: install and open a page on the exact connected domain, including the intended www or non-www host.
- Private page: choose a publicly reachable page without authentication, maintenance mode, or an IP allowlist.
Move or remove the installation safely
Keep only one copy of the script per rendered page. When changing themes or platforms, install and verify the tag in the replacement before removing the old implementation.
Disconnecting the website removes its inventory and viewer mappings. Removing only the script stops new browser discoveries but does not automatically delete workspace records.
Related guides
- Connect a website and install PDF monitoringVerify a public domain, install the lightweight script, and begin building a bounded PDF inventory.
- Install the website script on a custom-built siteAdd the generated tag to static HTML, shared server templates, React or Vite entry HTML, or a Next.js root layout without breaking verification.
- Tag managers and client-only script installationUnderstand why Google Tag Manager and runtime-only injection cannot complete secure website verification, and move the tag to a supported global template.