react-seo-skills

React SEO Skills

SEO and AI-search visibility for Next.js, Astro, and React applications. Works in Cursor, Claude Code, and Codex via native skill discovery.

<!-- BEGIN:react-seo-skills -->

This may NOT be the Next.js, React, Vite, or react-helmet-async you know. Frameworks ship breaking changes — APIs, conventions, and file structures in the target codebase may differ from your training data. Before implementing any SEO or GEO work: 1. Read the codebase first. Check the installed versions in package.json and the lockfile, the folder structure, and the project's existing conventions. 2. Verify against current documentation. If the installed version is newer than what you are confident about, look up the official docs for that exact version. Never implement from memory when versions disagree. 3. Implement against what the project actually uses — not what you remember. Example: params in generateMetadata is a plain object in Next.js 14 but a Promise in Next.js 15+.

<!-- END:react-seo-skills -->

Rules

1. Detect language before anything else. JavaScript project → write .js/.jsx

with no types. TypeScript project → write .ts/.tsx with types. See language.md.

1. Detect the stack before writing code. Never apply Next.js APIs to an Astro

or Vite project, Astro patterns to Next.js or Vite, or Vite patterns to a Next.js or Astro project.

1. Verify framework versions before writing code. Check package.json for

the installed versions of next, react, vite, and react-helmet-async. If a version is newer than your training data, consult its official docs before implementing — APIs and conventions change between major versions.

1. Ask for real project details — never guess or invent them. Before writing

metadata, ask the developer for: site name, production domain, default OG image URL, social handles, contact details, locale(s), and target keywords. All example.com / Site Name values in the reference files are placeholders. If you must proceed without an answer, mark every placeholder with a TODO comment and list them for the developer at the end.

1. Never repeat SEO code. Define metadata once in a shared, reusable place —

a SEO component (Pages Router, Vite), root-layout defaults plus title.template (App Router), or schema builder helpers for JSON-LD. If the same meta block appears on more than one page, extract it before continuing.

1. Start with keywords for full SEO setups. See keywords.md

before writing meta tags.

1. Validate every implementation. Point the developer to

validation.md. Never assume output is correct.

1. Choose the React metadata approach deliberately. React 19 can hoist

<title>, <meta>, and <link> from rendered JSX. Use react-helmet-async when the project needs its additional API, React 16–18 support, or SSR context handling; never add it automatically to every app. Never use the deprecated react-helmet package.

1. Warn about CSR limitations accurately. A client-only SPA can update

metadata after JavaScript runs, but some crawlers and social fetchers may inspect the initial HTML only. Recommend prerendering or SSR when indexable route content and metadata must be present in the initial response.

1. Use framework conventions. Do not invent custom abstractions unless asked.
2. Do not over-tag. Prioritize title, description, canonical, OG, and JSON-LD.
3. Flag performance issues that affect ranking: unoptimized images, render-blocking

scripts, poor LCP. See the performance quick checks in validation.md.

Detection Order

Always run in this sequence:

Stack Detection

If both app/ and pages/ exist, App Router takes precedence in Next.js 13+.

Planned (not yet supported): TanStack Start (0.4.0). If a project uses it, apply the closest matching general principles, tell the developer dedicated support is coming, and do not invent framework-specific APIs.

Implementation Order

Adapt all code to the detected language before implementing.

SEO Audit Mode

1. Detect language — are SEO files using the correct extensions and syntax?
2. Detect stack using the table above.
3. Keywords — keyword map? Distinct intents per page?
4. Metadata — title, description, canonical, OG, Twitter on key routes.
5. Structured data — JSON-LD present? Correct @type? Absolute URLs?
6. Sitemap & robots — exists and reflects the site's crawl policy?
7. GEO — checklist in geo.md.
8. Stack-specific rendering — metadata and per-route coverage match the detected stack.
9. CSR/SSR check — are important content and metadata present in the initial HTML?
10. Report as Critical / Suggestion / OK.

Stack Quick Reference

General Principles

• Present options and trade-offs. Recommend one path only when asked.
• Performance is SEO — Core Web Vitals affect ranking.
• AI-search visibility builds on foundational SEO; use the GEO guidance when the

project's audience or distribution channels make it relevant.