Website SEO — On-Page Optimization System
v1.0.0Complete on-page SEO system for any website — page optimization, schema markup, technical SEO checklist, internal linking strategy, Core Web Vitals guidance,...
⭐ 1· 2k·6 current·7 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (on-page SEO, schema, technical checklist) matches the SKILL.md content: checklists, prompts, and templates for title tags, meta descriptions, headings, content, Core Web Vitals, and schema. The skill is advisory only and does not request unrelated capabilities (no cloud credentials, no binaries).
Instruction Scope
The instructions are guidance and prompt templates that ask the user to paste page content, business details, and site information for audits and schema generation. It references testing tools (PageSpeed Insights) but does not include automated calls or require credentials. This is expected for a manual advisory skill, but users should be aware they will be asked to supply page contents and potentially business contact details when requesting generated schema or audits.
Install Mechanism
No install spec or code files are present. Being instruction-only means nothing is written to disk and there are no downloaded artifacts to review.
Credentials
The skill declares no environment variables, no credentials, and no config paths. That aligns with its described advisory/manual role—no disproportionate access is requested.
Persistence & Privilege
The skill is not set to always:true and does not request persistent system presence or modify other skills. It can be invoked by the agent as normal; there are no additional privilege escalations requested.
Assessment
This skill is advisory and coherent with its SEO purpose, but be cautious about the content you paste: do not paste secrets, API keys, or other sensitive credentials into prompts. If you later ask the skill to perform automated checks (e.g., submit sitemaps, query Search Console, or run PageSpeed APIs), those actions would require additional integrations/credentials — only provide such tokens if you trust the integration and can limit permissions (read-only where possible). For schema generation and business info, prefer public or non-sensitive fields (address, phone, hours) and double-check the generated markup before publishing. If you want automated site scanning or CMS-level changes, ask for a version that explicitly documents required integrations and their security model before granting access.Like a lobster shell, security has layers — review code before you run it.
contentvk97962ak85sjexh5hh1nvrpjz581x528latestvk97962ak85sjexh5hh1nvrpjz581x528marketingvk97962ak85sjexh5hh1nvrpjz581x528social-mediavk97962ak85sjexh5hh1nvrpjz581x528
License
MIT-0
Free to use, modify, and redistribute. No attribution required.