Understanding Sitelemetry access

Your account and connection

An MCP connection authorizes access to an existing Sitelemetry account. It does not create an account, verify a website or change account permissions. Use the normal account creation and sign-in process when needed.

Audit availability

Sitelemetry provides security, SEO, AI visibility, accessibility, performance and integration audits. Available audits, modules and usage depend on the permissions and allowances already assigned to the connected account. A combined audit follows the same rules for each included area.

Renew domain verification

Protected checks require a current ownership or authorization proof for the target. An expired or lost verification pauses those checks until ownership is confirmed again.

1. Sign in to Sitelemetry normally and open the dashboard’s Verified Domains section. Select the affected domain and its verification method.
2. For DNS TXT or HTTP file verification, review the displayed proof. If a new code is needed, publish the new record or file and then run the matching verification check. Generating a new code alone does not verify the site.
3. For Google Search Console, use an account with the required property access, reconnect it if needed and synchronize properties again. Confirm that the domain is shown as verified before retrying.

Verified sites, monitoring and usage

Verified domains define which targets are authorized. Monitoring projects store sites for ongoing tracking; project capacity is separate from domain verification. A full project slot does not by itself prevent audits of other verified sites. Audit permissions and remaining usage allowances still apply.

Reading an audit response

A request that needs verification or account access has not completed an audit. Follow the stated prerequisite, then retry. Partial or unavailable measurements remain explicitly marked; they are not a passing result. Operational failures are reported separately.