seo-audit
PassAudited by ClawScan on May 1, 2026.
Overview
The SEO audit skill is coherent and purpose-aligned, with only normal notes around optional analytics access, local context reading, and a helper script for analyzing pages.
This appears safe for its SEO-audit purpose. Before installing, verify the publisher if needed, review any `.claude/product-marketing-context.md` content, share only necessary read-only analytics/Search Console data, and run the helper script only against pages or files you intend to audit.
Findings (4)
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 used, the helper may read page HTML or access a target URL to generate SEO findings.
The included helper script can analyze a local HTML file or fetch a user-supplied URL, which is expected for an SEO checker but gives the agent a file/URL-processing capability.
Usage: python3 seo_checker.py [--file page.html] [--url https://...] [--json]
Use the helper only on intended pages or files, and avoid pointing it at private local files or non-public URLs unless that is deliberate.
Sharing analytics or Search Console data may reveal traffic, ranking, query, and business-performance information.
The skill may ask about or use Search Console and analytics access, which is normal for SEO audits but can expose account-level site performance data.
Access to Search Console / analytics? ... Google Search Console (essential)
Prefer read-only exports or least-privilege access, and share only the properties and time ranges needed for the audit.
Information in that local marketing context file could influence recommendations or be included in the conversation.
The skill directs the agent to read a persistent local context file and rely on it for the audit, which is scoped and purpose-aligned but may contain sensitive or stale business context.
If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context
Review that context file for sensitive or outdated information before using the skill.
Users have less external context for verifying the publisher or reviewing the project outside the registry.
The registry metadata does not provide an upstream source or homepage, so provenance is limited even though no risky install mechanism is shown.
Source: unknown Homepage: none
If provenance matters for your environment, verify the publisher and review the included files before installing.