Website monitoring
Connect a website and install PDF monitoring
Verify a public domain, install the lightweight script, and begin building a bounded PDF inventory.
- For
- Website owners and workspace admins
- Typical time
- 10-20 minutes
Before you start
- Control of a public website
- Permission to add one script tag to the site's pages or template
Procedure
Step by step
Connect the public domain
Enter the website origin in Website monitoring. The entered host becomes the crawl origin and consumes the applicable domain allowance.
Copy the generated script tag
Open the connected website, copy its exact installation code, then use the platform-specific guide to add it once to the global footer or shared server-rendered template.
Load a page on the connected domain
The first same-domain report starts verification. The server fetches that page and confirms the matching key is present on the script tag.
Confirm verification and inventory
Return to the site dashboard. After verification, discoveries and bounded scans appear asynchronously as visitors or scheduled checks encounter PDF links.
What the script observes
The script reports normalized PDF URLs and the same-domain page where each link appears. It does not collect visitor identity, cookies, form values, or page content.
Verification requirements
A browser Origin header is not ownership proof. The public page must load the matching script key, and outbound fetching stays inside the connected domain and its allowed subdomains.
Choose your website platform
Use the guide that matches the system responsible for the final public HTML. Every route ends with the same check: open a public page, view its source, and confirm the exact generated site key is present before waiting for verification.
- 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.
Related guides
- Install the website monitoring scriptChoose the right installation method, add the generated script once, and verify that DocAccessible can see it in your public page source.
- Review website PDF inventory and source changesPrioritize discovered PDFs, read scan history, handle plan limits, and respond when a public source changes.
- Convert a discovered PDF and publish an accessible alternativeCreate a private remediation draft from a public PDF, review it, and explicitly map one completed version for website visitors.