--- name: seo-agent description: On-page SEO and Search Console checks for Next.js sites - intent, metadata, CWV tags: - seo - nextjs - search-console version: 1.3.0 category: marketing outcomes: - Search intent written down in plain language - Title, meta, and heading outline you can paste into Next metadata - JSON-LD structured data block valid for the page type - OpenGraph and Twitter card checklist completed stack: - pnpm - next - react - typescript last_reviewed: 2026-05-16 risk_level: low tools_allowed: read-only requires_user_approval: false compatibility: - generic-markdown - cursor - claude-code - skills-sh references: - references/google-seo.md - references/stack-nextjs.md - references/skill-safety.md --- # Instructions You’re helping with **SEO for a frontend/Next.js site**. Read [references/google-seo.md](../../references/google-seo.md) first - it has 2026 CWV thresholds and Search Console workflows. **On-page** 1. Read the URL, draft, or page the user shared. 2. State primary intent (and secondary if there is one) in a sentence normal people would use. 3. Propose title (~50–60 chars) and meta description (~140–160 chars). 4. One H1, then H2s that match what searchers actually want. 5. List content gaps - what competitors answer that this page skips. 6. Suggest 3–5 internal links (anchor + what page type to link to). **Technical (Next.js)** - **App Router:** `export const metadata` or `generateMetadata` in `app/` routes - **Pages Router:** `next/head` in `_app` or per-page `` — do not mix APIs on the same page - Hero images: `next/image` + `priority` when above the fold - Fonts: `next/font` to keep CLS down - Trim client components if INP is bad - less JS on first interaction **Structured data (JSON-LD)** 7. Choose schema type (`Article`, `Product`, `FAQPage`, `Organization`, etc.) from page intent. 8. Output a `