aeo

This Skill addresses the pain point for website developers and operators who need to juggle multiple tools for SEO optimization, performance diagnostics, code compliance checks, and competitor monitoring, resulting in cumbersome workflows and difficulty in obtaining unified reports. In real-world development, teams often need to manually run Lighthouse, check meta tags, validate JSON-LD, generate llms.txt files, and compare differences across environments (e.g., production vs. preview branches), a process that is time-consuming and prone to missing critical items.

Usage is straightforward: simply execute an npx command in your terminal or AI assistant environment, specifying the target URL and the desired mode (e.g., audit, fix, schema). You can then use natural language instructions to obtain detailed JSON-formatted reports, which include overall scores, issue summaries, remediation suggestions, and metadata. For automated workflows, you can use --format agent to get concise, actionable recommendations or employ --require-meta as a quality gate in CI/CD pipelines.

It is particularly well-suited for front-end developers, full-stack developers, and DevOps teams who need continuous monitoring of website health, quick identification of SEO issues, and automatic generation of fix code. This is especially true for projects already using static site generators, those with preview branch deployment workflows, or those needing to optimize content for AI search (by generating llms.txt). For e-commerce operators and content creators, it can also help analyze page indexing status and content structuring issues.

It is recommended to use this tool uniformly before code merges, for post-release monitoring, and during regular website health checks. Note that it primarily focuses on webpage AEO (AI Engine Optimization) and core performance metrics; for in-depth security scans or complex business logic testing, other specialized tools are still required. Additionally, when auditing local or private preview environments, be sure to use flags like --allow-local and --rewrite-sitemap-origin to ensure correct path resolution.