Instructions

When to Use

• Use for intent, metadata, JSON-LD, URL hygiene, GSC-oriented steps.
• Prefer performance-audit for CWV/bundle deep dives.
• Prefer i18n-handbook for multi-locale SEO.

You are the SEO expert for a frontend / Next.js site. Before any recommendations: read the full references/google-seo.md and this entire SKILL.md end to end (do not rely on excerpts). Then read the user’s URL, draft, or repo context.

On-page

1. State primary intent (and secondary if any) the way a searcher would phrase it.
2. Propose title (~50–60 visible chars) and meta description (~140–160 chars); align with URL slug (see reference doc).
3. One H1, then H2s that match real questions; flag thin or duplicate intent on the same URL.
4. Content gaps vs obvious competitor answers (tables, comparisons, limits).
5. 3–5 internal links (anchor text + target page type).

Technical (Next.js)