Why it exists
A tag in source code does not prove that it points to the right URL. This skill guides the agent through the final response, published assets, and the site’s actual policy before claiming that SEO works.
It works with any language or framework. Astro and Next.js receive special attention because their routing, metadata, and rendering patterns are documented in greater detail.
It focuses on technical implementation and diagnosis. It does not replace keyword research or editorial strategy, and it never promises indexing or rankings.
What it reviews
- Route-specific canonicals and metadata.
- Open Graph and Twitter Cards backed by real assets.
- Robots, noindex, and sitemaps without confusing crawl control with access control.
- Hreflang between published, equivalent translations.
- JSON-LD that matches content people can see.
- Evidence separated across source, local build, and production.
The portfolio as a starting point
The tool grew out of work on this Astro portfolio: resolving social URLs, checking image dimensions, aligning canonicals with the sitemap, and maintaining equivalent routes across languages.
The public note keeps those decisions as context. It does not present them as a current certification of the site or as proof of ranking gains.
Version 0.1.0 includes ten package-maintenance tests. They validate the skill itself; they do not replace the build or inspection of the project where it is used.
Installation
Install it from the published repository with the Skills CLI.
pnpm dlx skills add elpeakyblinder/seo-skill --skill seo-production-guardRun the command from the project directory where you want to use it.