npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

next-aeo

v1.0.16

Published

Help LLMs understand your Next.js website better.

Downloads

3,707

Readme

🧠 next-aeo

This package generates a llms.txt file that summarizes your Next.js app's content for use by language models. It scans your project for informative pages (like marketing, legal, and pricing pages) and outputs a structured Markdown file containing high-level summaries.

🚀 Usage

Before running next-aeo, you must build your Next.js app first. In the root of your project, run your build script e.g.

npm run build

Then, run the following command whenever there are significant changes to your site:

npx -y next-aeo@latest

The generated llms.txt file is saved to public/llms.txt, making it accessible at /llms.txt on your website.

If you want to make generating an llms.txt file easier, you can also add it as a script to your package.json file and specify that the build script should be run before the llms script.

"scripts": {
  "prellms": "npm run build",
  "llms": "npx -y next-aeo@latest"
}

👇 Keep reading to learn more about the llms.txt standard and how it works.

🤔 Why llms.txt?

The llms.txt file is an emerging standard that helps AI systems better understand your website's content and purpose. By providing a structured summary of your site, you can:

  • Improve AI interactions: Help chatbots and AI assistants provide more accurate information about your product or service
  • Enhance content discovery: Make it easier for AI-powered search engines to understand and index your content
  • Enable better integrations: Allow AI tools to provide contextually relevant suggestions and answers
  • Future-proof your site: Prepare for the growing ecosystem of AI-powered web tools and services

Learn more about the llms.txt standard:

✨ Features

  • Smart content extraction: Automatically identifies and extracts meaningful content from your pages
  • 🧹 Noise filtering: Skips non-content pages (404, 500) and removes navigation, ads, and other clutter
  • 🚀 Performance optimized: Processes files in batches for efficient handling of large sites
  • 🧠 AI-powered summarization: Uses advanced language models to create concise, relevant summaries
  • 📄 Standard compliant: Outputs to public/llms.txt following the llms.txt specification
  • 🔧 Zero configuration: Works out of the box with any Next.js project

🏗️ How It Works

  1. Scans your Next.js build: Analyzes HTML files in your .next/server directory
  2. Filters content: Removes non-essential elements like scripts, styles, navigation, and ads
  3. Converts to Markdown: Transforms HTML content into clean, readable Markdown
  4. Generates summaries: Uses AI to create concise summaries of each page's content
  5. Creates llms.txt: Outputs a structured file that AI systems can easily understand

📄 What Gets Included

Included pages:

  • Marketing pages (home, about, features)
  • Product information pages
  • Pricing and plans
  • Legal pages (privacy, terms)
  • Documentation and help content
  • Blog posts and articles

Automatically excluded:

  • Error pages (404, 500, _not-found)
  • Navigation menus and headers
  • Footers and sidebars
  • Advertisements and promotional banners
  • Scripts and stylesheets
  • SVG icons and decorative elements

🐛 Debug Mode

To see detailed information about the processing:

Custom Models

You can use a custom OpenAI model by passing the --openai-key and --openai-model options.

npx -y next-aeo@latest --openai-key <your-api-key> --openai-model <your-model>
npx -y next-aeo@latest --debug

🔗 Related Resources


Made with ❤️ and 🤖 by Profound