seo

Audit this repository's SEO and GEO health from its source code, verified against the live site when a deployed URL is available. Every run produces two durable artifacts:

• SEO.md (repo root) — living fact sheet about the site's SEO, updated in place each run
• seo-reports/seo-report-YYYY-MM-DD.md — scored report and improvement plan for this run

The audit is read-only: apart from those two artifacts, touch no files unless the user accepts an offered fix in Step 6.

If the user passed a focus area as an argument, still run Step 1, then restrict Steps 2–5 to the rubric categories that match the focus, and say in the report which categories were skipped.

Step 1 — Establish context

1. Read SEO.md at the repo root if it exists. It carries facts from previous runs — deployed URL, target keywords, route inventory — and a ## Notes section that is manually maintained: preserve it verbatim.
2. Detect the stack and rendering strategy using the framework table in references/stack-guide.md. Determine per route group whether HTML is server-rendered/static or client-rendered — this decides whether crawlers see content in the raw response.
3. Build the route inventory: every indexable route or page template, and where its title/meta/schema come from.
4. Resolve the deployed URL, in order: skill argument → SEO.md → repo config (package.json homepage, CNAME, vercel.json, netlify.toml, framework config site/siteUrl). If none found, ask the user once for the URL and their target keywords/pages. No URL is fine — live checks become N/A.

Done when: stack, rendering strategy per route group, route inventory, and deployed URL (or an explicit "none") are all known.