What is SiteLock?

Only if nobody you work with uses it. SiteLock is the kind of tool a team points at its own site for uptime checks, performance tests, and audits. If someone on your team relies on it, blocking it silently breaks their monitoring. Almost none of the top websites we track have robots.txt rules for SiteLock right now.

No. SiteLock is not expected to follow robots.txt rules, so a disallow rule only states your preference. Enforce the block with firewall or server rules, then confirm in Agent Analytics that its requests actually stop.

Only if its owner sets that up. Monitoring tools check whatever they are configured to check, which can include staging sites and private health endpoints when a team grants access. Uninvited, SiteLock sees only public pages.

Someone pointed SiteLock at your site, most likely your own team. Uptime monitors, performance testers, and audit tools only visit the sites they are configured to watch.

Agent Analytics tracks SiteLock visits in real time alongside every other known AI agent, crawler, and scraper. You can also check your server logs for requests whose user agent string contains "SiteLock". Look for regular checks of the same pages or endpoints, often minutes apart. Keep in mind that SiteLock doesn't publish a verification method, so any client can claim its user agent string and a log match is a hint rather than proof.