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
Install the dependency-free `/site/v1.js` snippet with the generated public site key in the website template so it can observe pages containing PDFs.
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.
Related guides
- 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.
- Understand plans, billing, and usage limitsRead workspace allowances, choose a plan, start checkout, and understand which limits apply to each workflow.