llms.txt for Nuxt Sites

The llms.txt standard provides AI assistants with a concise summary of your site's content. Think of it as robots.txt for AI inference—not blocking access, but guiding AI to your most useful documentation.

Jeremy Howard proposed the standard in September 2024. Unlike robots.txt, llms.txt uses Markdown and targets AI tools at inference time rather than crawlers at training time.

Nuxt has dedicated support via nuxt-llms—automatic generation from your config or content.

Quick Setup

Install the module:

npx nuxi module add nuxt-llms

Configure in nuxt.config.ts:

export default defineNuxtConfig({
  modules: ['nuxt-llms'],
  llms: {
    domain: 'https://example.com',
    title: 'My Nuxt App',
    description: 'Documentation for My Nuxt App',
    sections: [
      {
        title: 'Getting Started',
        links: [
          { title: 'Installation', href: '/docs/installation' },
          { title: 'Configuration', href: '/docs/configuration' }
        ]
      }
    ]
  }
})

The module generates /llms.txt and /llms-full.txt automatically at build time.

When llms.txt Matters

llms.txt solves a specific problem: LLM context windows are too small to process entire websites. Your Nuxt documentation might be thousands of pages, but an AI assistant needs a curated entry point.

llms.txt is useful for:

• Documentation sites (API references, tutorials, guides)
• Open source projects
• Technical blogs with evergreen content
• Sites where AI assistants frequently reference your content

llms.txt is overkill for:

• Marketing sites without technical docs
• E-commerce product pages
• News sites with time-sensitive content
• Small sites with fewer than 10 pages

llms.txt vs robots.txt

Important: AI crawlers don't currently request llms.txt during inference. GPTBot, ClaudeBot, and PerplexityBot use pre-built datasets and respect robots.txt, not llms.txt.

The primary use case today is AI coding assistants (Cursor, Claude Code) and MCP servers that explicitly fetch llms.txt to understand project documentation.

File Format

llms.txt uses a structured Markdown format. Only the H1 title is required—everything else is optional.

# Nuxt SEO Documentation

> Complete SEO toolkit for Nuxt applications. Handles sitemaps, robots.txt, OG images, and schema.org.

Key modules: sitemap, robots, og-image, schema-org, seo-utils.

## Getting Started

- [Installation](https://nuxtseo.com/docs/nuxt-seo/getting-started/introduction): Install the full Nuxt SEO module
- [Site Config](https://nuxtseo.com/docs/site-config/getting-started/introduction): Configure your site URL and name

## Modules

- [Sitemap](https://nuxtseo.com/docs/sitemap/getting-started/introduction): Automatic sitemap generation
- [Robots](https://nuxtseo.com/docs/robots/getting-started/introduction): robots.txt and meta robots
- [OG Image](https://nuxtseo.com/docs/og-image/getting-started/introduction): Dynamic social images

## Optional

- [Changelog](https://github.com/harlan-zw/nuxt-seo/blob/main/CHANGELOG.md)

Required Sections

H1 Title — The only required element. Name of your project or site.

Optional Sections

Blockquote — Brief summary with key information for understanding the rest of the file.

Body content — Paragraphs, lists, or any Markdown except headings. Provides context about the project.

H2 sections — File lists with links to detailed documentation. Each entry is a Markdown link with optional description:

- [Link Text](https://url): Optional description of what this page covers

Optional section — An H2 titled "Optional" marks content that AI can skip if context is limited.

nuxt-llms Configuration

Manual Sections

Define sections explicitly when you want full control:

export default defineNuxtConfig({
  modules: ['nuxt-llms'],
  llms: {
    domain: 'https://example.com',
    title: 'My Nuxt App',
    description: 'A Nuxt 3 application with TypeScript.',
    sections: [
      {
        title: 'Documentation',
        links: [
          { title: 'API Reference', href: '/docs/api' },
          { title: 'Components', href: '/docs/components' },
          { title: 'Getting Started', href: '/docs/setup' }
        ]
      },
      {
        title: 'Optional',
        links: [
          { title: 'Changelog', href: '/changelog' }
        ]
      }
    ]
  }
})

With Nuxt Content

If you're using Nuxt Content, nuxt-llms can generate sections from your content automatically:

export default defineNuxtConfig({
  modules: ['@nuxt/content', 'nuxt-llms'],
  llms: {
    domain: 'https://example.com',
    title: 'My Docs',
    // Automatically generates from /content/docs
    content: {
      collections: ['docs']
    }
  }
})

Extended Version

The module generates both /llms.txt (concise) and /llms-full.txt (comprehensive) automatically. AI tools can choose based on their context limits.

export default defineNuxtConfig({
  llms: {
    // ... config
    full: {
      // Include full page content in llms-full.txt
      includeContent: true
    }
  }
})

Testing Your llms.txt

1. Check it loads: Visit https://yoursite.com/llms.txt
2. Validate format: Ensure H1 exists and links are absolute URLs
3. Test with AI: Paste your llms.txt into ChatGPT or Claude and ask about your docs

There's no official validator yet, but the llms-txt-hub directory lists sites implementing the standard.

Who Uses llms.txt?

The standard has 2,000+ GitHub stars and growing adoption among documentation sites. Notable implementers include Answer.AI, fast.ai, and various open source projects.

However, adoption by AI providers is limited. As of late 2025:

• No major AI crawler (GPTBot, ClaudeBot, PerplexityBot) requests llms.txt during inference
• MCP servers and AI coding tools can use it when explicitly configured
• Documentation frameworks (VitePress, Docusaurus, Nuxt) generate it automatically

The spec is still emerging. Implementing llms.txt today is forward-looking—it positions your docs for better AI integration as adoption grows.

llms.txt and GEO

llms.txt complements Generative Engine Optimization but serves a different purpose:

For maximum AI visibility, implement both:

1. Schema.org structured data for GEO (use nuxt-schema-org)
2. llms.txt for documentation discovery (use nuxt-llms)
3. Content structure optimized for extraction

Full Nuxt SEO Stack

For comprehensive AI and search optimization, use the full Nuxt SEO module:

This includes automatic schema.org, sitemaps, robots.txt, and OG images—all signals that help both traditional search and AI search understand your content.