seo-monitoring
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This is an instruction-only SEO monitoring guide; the notable items are expected use of analytics/Search Console access and optional user-identifier tracking.
This skill appears safe as an instruction-only SEO guide. Before using it with GA4, GSC, or User ID tracking, confirm the exact account permissions, connect only the properties you intend to analyze, and follow your privacy/consent requirements for analytics identifiers.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If connected to GSC or GA4, the agent or related tooling may be able to read SEO and analytics data for the selected properties.
Using the Google Search Console API normally requires delegated access to a site/property account. This is expected for SEO monitoring, but users should notice and scope that access.
**GSC API**: Index, clicks, impressions, coverage for automation, dashboards
Use least-privilege Google permissions, connect only the intended properties, and avoid sharing credentials or tokens in chat.
If implemented, visitor identifiers and behavior may be shared with GA4 for cross-device or cross-session analytics.
The guide explicitly recommends sending a cross-session user identifier to an external analytics provider. This is disclosed and relevant to analytics, but privacy-sensitive.
**User ID**: Cross-device, cross-session identification; send to GA4
Only implement User ID tracking when you have an appropriate privacy basis, consent where required, and clear minimization rules for what is sent to GA4.