Add @aeorank/nuxt — AI-visibility scanner for Nuxt sites#578
Conversation
📝 WalkthroughWalkthroughA new module entry for Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 Warning |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@README.md`:
- Line 40: The Modules section in README.md currently lists an individual module
entry '@aeorank/nuxt' which breaks the section's intended pattern of linking to
external module catalogs; remove the '@aeorank/nuxt' bullet from the Modules
section (or move it to a more appropriate section like "Starter Template" if you
want to showcase individual modules) and instead add a brief note directing
authors to submit Nuxt modules to the official Nuxt modules directory
(https://nuxt.com/modules); ensure the change targets the Modules section and
the specific '@aeorank/nuxt' text so the section remains a pointer to external
module listings only.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
|
|
||
| - [Official listing](https://nuxt.com/modules) | ||
| - [nuxt-module topic on GitHub](https://github.com/topics/nuxt-module) | ||
| - [@aeorank/nuxt](https://github.com/vinpatel/aeorank/tree/main/packages/nuxt) - Scores your site's AI visibility and generates the files (llms.txt, ai.txt, CLAUDE.md, and more) that help your pages get cited by ChatGPT, Perplexity, Claude, and Google AI Overviews. |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify npm package and GitHub repository existence
echo "=== Checking npm package ==="
curl -s https://registry.npmjs.org/@aeorank/nuxt | jq -r '.name, .version, .description, .license' || echo "Package not found"
echo ""
echo "=== Checking GitHub repository ==="
gh repo view vinpatel/aeorank --json name,description,isArchived,visibility,licenseInfo 2>&1 || echo "Repository not accessible"
echo ""
echo "=== Checking if packages/nuxt directory exists ==="
gh api repos/vinpatel/aeorank/contents/packages/nuxt 2>&1 | jq -r 'if type=="array" then "Directory exists" else .message end'Repository: nuxt/awesome
Length of output: 509
🏁 Script executed:
# Read the README.md to verify the structure of the Modules section
sed -n '30,50p' README.mdRepository: nuxt/awesome
Length of output: 1285
Reconsider placement: this section appears designed to reference external module catalogs, not list individual modules.
The Modules section currently contains only reference links to comprehensive module listings (official directory and GitHub topic). The @aeorank/nuxt entry is the first individual module listed here, which breaks the section's established pattern. Other sections like "Starter Template" explicitly list individual items with descriptions, but the Modules section appears intentionally minimal—directing users to maintained external directories instead.
The package itself is legitimate (MIT-licensed, GitHub repository is public and active), but individual Nuxt modules should be submitted to the official Nuxt modules directory rather than listed directly in this awesome-list.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@README.md` at line 40, The Modules section in README.md currently lists an
individual module entry '@aeorank/nuxt' which breaks the section's intended
pattern of linking to external module catalogs; remove the '@aeorank/nuxt'
bullet from the Modules section (or move it to a more appropriate section like
"Starter Template" if you want to showcase individual modules) and instead add a
brief note directing authors to submit Nuxt modules to the official Nuxt modules
directory (https://nuxt.com/modules); ensure the change targets the Modules
section and the specific '@aeorank/nuxt' text so the section remains a pointer
to external module listings only.
2 participants
Adding @aeorank/nuxt to the Modules section. It's an open-source Nuxt module (MIT) that scores your site 0-100 across 36 criteria for how ChatGPT, Perplexity, Claude, and Google AI Overviews see it, then generates the files AI engines actually read (llms.txt, llms-full.txt, ai.txt, CLAUDE.md, schema.json, robots-patch.txt, faq-blocks.html, citation-anchors.html, sitemap-ai.xml).
Repo: https://github.com/vinpatel/aeorank — docs and a live scanner at https://aeorank.dev.
Hope it's useful for folks shipping Nuxt sites who want their content picked up by LLM-powered search. Happy to tweak the wording or move the entry if you'd prefer a different spot.