[Roadmap] react-helmet-pro industry-grade SEO platform

[lahiruudayakumara]

Vision

Evolve react-helmet-pro from a modern React head manager into a dependable, framework-aware SEO platform with strong correctness, security, developer tooling, and release discipline.

This roadmap tracks engineering epics. Each epic must retain backward compatibility where practical, publish measurable acceptance criteria, include tests and documentation, and avoid claims that metadata guarantees ranking or rich-result eligibility.

Phase 1 — Foundation and correctness

• [Epic] SEO validation, diagnostics, and audit API #5 — SEO validation, diagnostics, and audit API
• [Epic] Provider SEO defaults and automatic social metadata fallbacks #6 — Provider SEO defaults and automatic social metadata fallbacks
• [Epic] Canonical URL resolution and normalization policies #7 — Canonical URL resolution and normalization policies
• [Epic] Advanced robots directives and hreflang management #8 — Advanced robots directives and hreflang management
• [Epic] Harden head deduplication, inheritance, and concurrent rendering #12 — Head deduplication, inheritance, and concurrent rendering
• [Epic] Industry-grade compatibility, performance, security, and releases #19 — Compatibility, performance, security, and release program

Exit criteria

• Stable tag identity and precedence model
• SSR request isolation and React concurrency coverage
• Public validation API
• Compatibility matrix, bundle budgets, and security regression suite
• No undocumented breaking changes

Phase 2 — Search platform primitives

• [Epic] Expand structured-data support for Google search features #9 — Expanded Google-supported structured data
• [Epic] JSON-LD graph composition, entity registry, and deduplication #10 — JSON-LD graph composition and entity deduplication
• [Epic] Sitemap, robots.txt, and indexing route generators #11 — Sitemap, robots.txt, and indexing route generators
• [Epic] CSP nonces, secure tag placement, and resource hints #13 — CSP nonces, secure placement, and resource hints
• [Epic] SEO testing utilities, snapshot serializers, and generated schema types #18 — SEO testing utilities and generated schema types

Exit criteria

• Structured-data component catalog with safe serialization
• Reusable graph entities and stable hydration
• Standards-compliant crawler file generation
• CSP-aware rendering
• Consumer-facing test matchers

Phase 3 — Ecosystem integrations

• [Epic] Complete Next.js App Router metadata integration #14 — Next.js App Router metadata integration
• [Epic] React Router, Remix, Astro, Vite SSR, and server adapters #15 — React Router, Remix, Astro, Vite SSR, and server adapters

Exit criteria

• Optional framework entry points
• No framework dependency in the core runtime
• Published compatibility matrices
• Request isolation and streaming integration tests
• Deployable example applications

Phase 4 — Product APIs and developer experience

• [Epic] Vertical SEO APIs for commerce, local, media, pagination, and paywalls #16 — Vertical SEO APIs for commerce, local, media, pagination, and paywalls
• [Epic] Developer tooling: CLI audits, ESLint rules, and browser inspector #17 — CLI audits, ESLint rules, and browser inspector

Exit criteria

• High-level domain APIs compose stable primitives
• CLI and lint checks run in CI
• Development inspector is excluded from production
• JSON/SARIF reporting is available

Cross-cutting definition of done

Every implementation issue derived from these epics should include:

• API design and TypeScript types
• SSR, hydration, client navigation, and edge-case coverage as applicable
• Security and escaping review
• Bundle-size/performance impact
• Documentation and realistic examples
• Changelog and migration notes
• No unrelated changes
• Semver classification

Planning guidance

Break epics into independently releasable implementation issues before development begins. Prefer shared primitives over framework-specific duplication. Ship experimental APIs behind clearly marked entry points until their compatibility and semantics are proven.