seo-monitoring

PassAudited by ClawScan on May 1, 2026.

Overview

This is a coherent instruction-only SEO monitoring guide; the main things to notice are optional analytics/API integrations and cross-device user tracking guidance.

This skill appears reasonable as an SEO monitoring guide. Before implementing its GA4 or GSC recommendations, check privacy requirements, avoid sending PII to analytics providers, and limit API/dashboard access to people who need it.

Findings (2)

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.

Low

#ASI07: Insecure Inter-Agent Communication

What this means

If implemented, visitor identifiers may be shared with GA4 and used for cross-device tracking.

Why it was flagged

The skill recommends sending a persistent user identifier to an external analytics provider, which is relevant to privacy and data-boundary decisions.

Skill content

- **User ID**: Cross-device, cross-session identification; send to GA4

Recommendation

Use consent-aware analytics configuration, avoid sending personal information as the User ID, and document what identifiers are shared with third-party analytics tools.

Low

#ASI03: Identity and Privilege Abuse

What this means

Connecting this workflow to Search Console could expose site performance and indexing data to whatever dashboard or automation the user builds.

Why it was flagged

Using the Google Search Console API for site-specific SEO data implies delegated access to analytics/search-console data, which is expected for the stated purpose but should be scoped.

Skill content

- **GSC API**: Index, clicks, impressions, coverage for automation, dashboards

Recommendation

Grant only the minimum required Search Console/API access, keep credentials out of shared documents, and review who can access generated dashboards.