Skip to content

Pro Site Scans ​

Pro scans save reports and update the service inventory. They require Scan permission, a compatible enabled consent engine, and usable license access.

Scan site ​

  1. Choose Scan site from Services or Scans.
  2. Keep the administrator tab open while the scan processes short batches.
  3. Review the completed report and its coverage.
  4. Open Services to classify and apply the findings you approve.

Pages are discovered from Joomla's menu, categories, and articles, with sitemap information when available. A sitemap is not required. Pages per manual scan defaults to 20 and can be raised to 200 in Options. A scan of a larger site is therefore a bounded selection, not a promise that every page was checked.

Use Included URLs and Excluded paths to adjust the scope. If a manual scan pauses, return to its active scan and use Resume when offered. A scheduler-owned scan continues through Joomla rather than through the browser.

Scan one page ​

Open the Scan site menu and choose One page…, enter a public page on the same site, and choose Scan this page. This is useful after adding an embed or when investigating one landing page.

External hosts and unsafe targets are rejected. Use the public URL you intend to inspect, including the appropriate language path on a multilingual site.

What the report contains ​

  • Recognized and unknown external services, with their confidence and locations.
  • Scripts, stylesheets, iframes, tracking pixels, connection hints, and relevant inline references found in the server-rendered markup.
  • Pages checked, incomplete coverage, and any errors or limits.
  • Your site's own files in a separate section, rather than mixed into external-service rows.
  • New or disappeared services when a previous scan has comparable page coverage.

Open a report by its date in Scan reports. Search and filters help find earlier runs. Deleting reports requires Joomla's Delete permission for the component.

Comparing scans ​

Comparisons use the same checked pages. Partial coverage must not be read as evidence that an unobserved service disappeared. For scheduled runs, the report can also identify a service not previously recorded in the site inventory.

Reports state whether coverage was complete and comparable. Review those labels before treating a change summary as a site-wide conclusion.

Coverage limits ​

This scanner reads server-rendered HTML. It does not execute JavaScript, interact with a login session, or observe browser cookies and storage. Services inserted later by a tag manager may require a manual browser review.

A scan records findings; it never changes blocking rules automatically. Continue with Services & blocking rules to review and apply changes, and Setup Health for the browser checklist.

For automatic runs, see Scheduled scans. For the standalone Free one-page scanner, see Site Scanner.