Repository navigation
fix(stats): remove obsolete FAQ rich-result metadata - #1436
Conversation
|
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Remove FAQPage structured data src/routes/stats/npm/index.tsx |
The route removes the FAQPage data object and its JSON-LD script. The visible FAQ section and WebApplication JSON-LD remain. |
Priority:
Estimated code review effort: 1 (Trivial) | ~3 minutes
Change: Bug fix
Possibly related PRs
- TanStack/tanstack.com#1435: Changes SEO and JSON-LD behavior for NPM statistics comparison routes.
Merge Risk: 
Minimal · up to 79b6f
-
The metadata removal appears ready for normal deployment checks; no merge-blocking issue was identified.
Pre-merge checks: 
5
-
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files.
-
Finishing Touches
-
📝 Generate docstrings
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
Remove the duplicate FAQ JSON-LD from NPM Stats. The visible FAQ remains, along with the WebApplication metadata and its clean
/stats/npmURL.This completes the FAQ metadata review requested in #1152. Google retired FAQ rich results in May 2026, and no other consumer is documented in this codebase. The broader issue stays open for deployment and comparison-route verification.
Summary by CodeRabbit