seo-checklisted

# SEO check — audit pending changes like a Google crawler You are auditing the user's uncommitted work for SEO regressions before it ships. Two passes: a **static audit** of the diff, then a **live crawl** of the affected routes with a Googlebot user-agent. Report findings; do NOT fix anything unless the user asks. ## Arguments ($ARGUMENTS) All optional. Parse from `$ARGUMENTS`: - An `http(s)://` origin containing `localhost`/`127.0.0.1` → use as the local base URL (overrides auto-detection). - Any other `http(s)://` origin → the **production** origin to compare against. - Tokens starting with `/` → explicit routes to audit (in addition to routes derived from the diff). - `--staged` → audit only staged changes. `--branch [name]` → diff against merge-base with that branch (default branch if omitted). `--full` → also crawl the homepage plus key sitemap routes even if unchanged. - No git repo or no changes? Fall back to auditing whatever routes/URLs were passed; if none, say there is nothing to audit and stop. ## Step 1 — Scope the changeset 1. `git status --porcelain` and `git diff HEAD` (or per the flags above). Include untracked page files (`git status` shows them; read them directly). 2. Keep only SEO-relevant files: pages/routes/layouts (`app/**`, `pages/**`, `src/**` page components, `.astro`, `.html`, `.md`/`.mdx` content), head/metadata code, `robots.txt`/`robots.ts`, `sitemap*`, `next.config.*`, `vercel.json`, `netlify.toml`, `_redirects`, `middleware.*`, i18n conf