llms.txt for Nuxt Sites · Nuxt SEO

-
-
-
-

[1.4K](https://github.com/harlan-zw/nuxt-seo)

[Nuxt SEO on GitHub](https://github.com/harlan-zw/nuxt-seo)

Learn SEO

Master search optimization

Nuxt

 Vue

-
-
-
-
-
-
-

-
-
-
-
-
-
-

-
-
-
-
-
-
-
-
-
-
-

-
-
-
-
-
-
-
-
-

1.
2.
3.
4.
5.

# llms.txt for Nuxt Sites

Help AI assistants understand your Nuxt documentation with the llms.txt standard. Configure nuxt-llms for automatic generation.

[![Harlan Wilton](https://avatars.githubusercontent.com/u/5326365?v=4)Harlan Wilton](https://x.com/harlan-zw)6 mins read Published Dec 17, 2025 Updated Jan 29, 2026

The [llms.txt standard](https://llmstxt.org/) 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 to **optimize its context window**.

Jeremy Howard proposed the standard in September 2024. By 2026, it has become the de facto entry point for AI agents, coding assistants (Cursor, Claude Code), and real-time AI search engines looking for high-density information.

Nuxt has dedicated support via [nuxt-llms](https://github.com/harlan-zw/nuxt-llms): automatic generation from your config or content.

## [Quick Setup](#quick-setup)

Install the module:

```
npx nuxi module add nuxt-llms
```

Configure in `nuxt.config.ts`:

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](#when-llmstxt-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](#llmstxt-vs-robotstxt)

| Feature | robots.txt | llms.txt |
| --- | --- | --- |
| Purpose | Block/allow crawling | Guide AI to useful content |
| Format | Custom syntax | Markdown |
| When used | Training data collection | Inference (answering questions) |
| Crawler support | All major crawlers | Limited, AI coding tools |
| Required | No | No |

**Important:** By 2026, **AI crawlers have begun requesting llms.txt** during inference to quickly build a map of your site's most relevant documentation. GPTBot, ClaudeBot, and PerplexityBot use these files to ensure their real-time responses are grounded in your most up-to-date and authoritative content.

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](#file-format)

llms.txt uses a structured Markdown format. It only requires the H1 title. Everything else is optional.

/llms.txt

```
# 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](#required-sections)

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

### [Optional Sections](#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](#nuxt-llms-configuration)

### [Manual Sections](#manual-sections)

Define sections explicitly when you want full control:

nuxt.config.ts

```
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](#with-nuxt-content)

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

nuxt.config.ts

```
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](#extended-version)

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

nuxt.config.ts

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

## [Testing Your llms.txt](#testing-your-llmstxt)

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](https://chatgpt.com) or Claude and ask about your docs

Use the [mdream llms.txt validator](https://mdream.dev/tools/llms-txt/validate) to check your file for format issues, or browse the [mdream llms.txt hub](https://mdream.dev/hub) to see how other projects structure theirs.

## [Who Uses llms.txt?](#who-uses-llmstxt)

The standard has [2,000+ GitHub stars](https://github.com/AnswerDotAI/llms-txt) 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](#llmstxt-and-geo)

llms.txt complements

 but serves a different purpose:

| GEO | llms.txt |
| --- | --- |
| Optimizes content for AI citations | Provides structured entry point to docs |
| Targets AI search (ChatGPT, [Perplexity](https://perplexity.ai)) | Targets AI coding tools and MCP servers |
| Uses schema.org, content structure | Uses Markdown file format |
| Improves visibility in AI responses | Improves AI understanding of your project |

For maximum AI visibility, implement both:

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

## [Full Nuxt SEO Stack](#full-nuxt-seo-stack)

For complete 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.

---

On this page

- [Quick Setup](#quick-setup)
- [When llms.txt Matters](#when-llmstxt-matters)
- [llms.txt vs robots.txt](#llmstxt-vs-robotstxt)
- [File Format](#file-format)
- [nuxt-llms Configuration](#nuxt-llms-configuration)
- [Testing Your llms.txt](#testing-your-llmstxt)
- [Who Uses llms.txt?](#who-uses-llmstxt)
- [llms.txt and GEO](#llmstxt-and-geo)
- [Full Nuxt SEO Stack](#full-nuxt-seo-stack)

[GitHub](https://github.com/harlan-zw/nuxt-seo) [ Discord](https://discord.com/invite/275MBUBvgP)

###

-
-

Modules

-
-
-
-
-
-
-
-
-

###

-
-
-

###

Nuxt

-
-
-
-
-

Vue

-
-
-
-
-
-
-
-

###

-
-
-
-
-
-
-
-
-
-

Copyright © 2023-2026 Harlan Wilton - [MIT License](https://github.com/harlan-zw/nuxt-seo/blob/main/license) · [mdream](https://mdream.dev)