What problem does it solve? Pages get indexed based on what a machine can fetch and parse, not what a person sees after rendering. This Skill provides a reference of production-grade rules that prevent the two dominant search-visibility failures: the same content reachable at multiple addresses, and structured-data claims that nothing on the visible page corroborates. ## Core Features & Use Cases - Canonical and Identity Rules: Enforce one address per resource with redirect discipline, trailing-slash normalization, and parameterized-route canonical construction. - Metadata and Structured Data Review: Check per-page title and meta description uniqueness, JSON-LD type selection, absolute addressing, and the mirroring rule that every serialized claim needs a visible counterpart. - Crawl Artifact Guidance: Derive robots.txt and sitemap.xml from the request host and actual routes instead of hardcoded environment-specific values. - Use Case: Before shipping a SvelteKit or any HTML-emitting site, run a pre-ship review that fetches each route, verifies one h1 per page, confirms canonical declarations resolve without redirects, and validates that JSON-LD entities match visible page content. ## Quick Start Review the pages in this project for search visibility issues, checking canonical URLs, per-page titles, JSON-LD consistency, and robots.txt host derivation before deployment.
