Sitelemetry

Sitelemetry’s public examples attach details such as an endpoint, response header or certificate to a finding. The workflow then adds impact and repair guidance, with a way to run checks again after a change. That gives a website team something more concrete to investigate than a score on its own.

Paid coverage spans security, technical SEO, AI visibility, accessibility, performance and integrations. The scope still depends on the run. External tools such as Nmap, Nuclei, ZAP and WPScan need the appropriate plan, configuration and an available worker. A listed entitlement does not guarantee that an engine ran.

MCP access lets compatible assistants request audits and work with returned findings. The same account limits apply. Protected scans require current target verification and authorization; users must own the site or have express permission to assess it.

The privacy policy explains that the assistant provider receives tool requests and audit results as part of the conversation. That matters when a report contains sensitive technical details. Before connecting an assistant, a team needs to decide whether those findings can be shared with its provider.

The Free plan includes 10 security scans per month using 10 of the platform’s 27 security modules, one saved project and one user. It excludes the other audit areas, scheduled monitoring and JSON or PDF exports.

Starter is listed at $49 per month in USD, renewing monthly, with broader audit areas, one monitored project, weekly checks and JSON reports within its usage limits. Taxes and the final purchase total are confirmed at checkout.

Sitelemetry’s terms describe results as a snapshot of the target, methods and observation time. Findings still need validation, and proposed repairs need testing in the actual environment. Neither a clean report nor static accessibility checks establish security or compliance.