Create and Use a Shopware llms.txt Correctly

A Shopware llms.txt is intended to provide AI systems with a compact, machine-readable overview of the most important content in your online shop. The file is currently the subject of intensive debate, but its practical benefits are less clear than many providers claim.

For Shopware operators, the technical creation of the file is therefore only one part of the task. What matters is a sensible selection of content, reliable updates, and objective performance measurement. This guide explains how to structure the file, provide it in Shopware 6, and assess it realistically.

What is an llms.txt in Shopware 6?

An llms.txt is a Markdown file in a website’s root directory that summarizes key content and links for large language models. In a Shopware 6 shop, it can list important categories, selected products, guides, shipping information, and service pages in a structured format.

The underlying idea comes from the open specification at llmstxt.org. An AI agent should be able to use a short table of contents for orientation without first evaluating the navigation, filters, scripts, and every individual shop page. The file is usually located at /llms.txt and uses simple Markdown headings and descriptive links.

What does an llms.txt file actually look like?

An llms.txt is deliberately easy to scan. # identifies the shop, > summarizes its offering and positioning in one sentence, and ## groups content into sections such as categories, guides, or service. Selected pages then appear as Markdown links in the format [Link text](URL): brief description.

The link text names the destination page, the URL points directly to the content, and the brief description tells AI systems what they will find there. This creates a curated selection of the most useful entry points rather than a complete directory of every page.

# My Shop
> Shopware 6 store for sustainable home accessories

## Important categories
- [Lighting](https://myshop.com/lighting): Lamps for homes and offices

## Service
- [Shipping and delivery](https://myshop.com/shipping): Delivery times, shipping costs, and available shipping methods

How it differs from robots.txt and sitemap.xml

The llms.txt is not a control file and replaces neither robots.txt nor sitemap.xml. A robots.txt defines access rules for crawlers. An XML sitemap helps search engines discover URLs. The llms.txt instead curates selected content and provides context without controlling access or indexing.

For your AI SEO strategy, this means: The file can serve as an additional orientation signal. Technical crawlability, structured data, helpful content, and conventional search engine optimization remain necessary.

What benefits can an llms.txt offer shops?

The potential benefit of an llms.txt is the compact delivery of relevant shop information to AI agents and other automated systems. It creates a controlled entry point that prioritizes important pages and adds short descriptions.

Potential benefits for AI systems

A well-maintained file can organize product ranges, categories, and editorial content in a comprehensible hierarchy. This is particularly useful for large catalogs in which faceted navigation, variants, and dynamic content produce many similar URLs. A clean strategy for AI in e-commerce is a useful complement.

• Clear priorities: You link to pages that explain your brand, product range, and advisory content particularly well.
• Less technical noise: Checkout, login, filter parameters, and internal search pages are excluded.
• More context: Short descriptions explain what information each destination contains.
• Easier maintenance: A compact file can be reviewed and versioned regularly.

Limitations and current research

An llms.txt guarantees neither better rankings nor citations in AI responses. Ahrefs analyzed a total of 137,210 domains in May 2026. Twenty-eight percent published an llms.txt, but 97 percent of the available files did not receive a single request.¹

Of the requests that were actually measured, 96 percent came from bots. Named AI tools caused 19.5 percent of requests to existing files.² This evidence supports a test with clear measurement, not a blanket visibility promise.

Adoption is also limited. In June 2026, Rankability found an llms.txt on 87 of 1,000 top domains examined. In the e-commerce segment, the figure was 2 of 29 domains.³ A file can therefore be useful preparation for agentic use, but it should not displace fundamental online shop optimization.

What content belongs in the file?

An effective llms.txt contains a concise shop description and a curated selection of permanently relevant URLs with clear explanations. It is not a complete shop export or a second XML sitemap.

Required content and sensible selection

Start with the shop name, a short value proposition, and the most important topic areas. Follow this with Markdown sections containing links. Each link should have a clear title and a brief description.

• Company and brand: Link to the About page, contact details, and central trust information.
• Categories: Select stable entry pages with a clear search intent.
• Products: Prioritize core products, bestsellers, or offers that require explanation.
• Guidance: Include guides, FAQs, and relevant product descriptions.
• Service: Add shipping, returns, payment methods, and warranty conditions.

How to prioritize Shopware pages correctly

Depending on the configuration, Shopware creates categories, shopping experiences, product variants, language versions, and technical system pages. Include only canonical URLs that are accessible without a session, login, or filter parameter. Checkout, account, search, wish lists, and paginated duplicates generally do not belong in the file.

For variants, link to the canonical product page and describe only stable information. Prices and availability change frequently. If the llms.txt contains these values, updates must be connected to your shop data. Otherwise, you create a readable but rapidly outdated information source.

How do you create the Shopware llms.txt?

You create a Shopware llms.txt either manually as a Markdown file or automatically with a generator or plugin. The right method depends on catalog size, update frequency, and available development resources.

Manual creation

For small product ranges, a manually maintained file is often sufficient. Create a UTF-8 text file, start with an H1 heading, and group links under H2 headings. Then upload the file so that it is accessible at https://your-domain.com/llms.txt with HTTP status 200.

1. Define the purpose, target audiences, and most important shop areas.
2. Select only canonical, publicly accessible URLs.
3. Write a short and objective description for each link.
4. Validate Markdown, HTTP status, and character encoding.
5. Plan a fixed review cycle for changes.

Generator or Shopware plugin

For larger catalogs, automation reduces maintenance effort. A generator can read the sitemap and navigation. A Shopware plugin can also access categories, shopping experiences, and products directly. For every solution, check whether exclusions, language versions, canonical URLs, and update intervals can be controlled. For conversion measures, it is also relevant whether the extension works without conflicts with other components such as a Shopware 6 conversion plugin.

How do you validate and maintain the file?

Quality assurance for an llms.txt covers accessibility, syntactic readability, content accuracy, and observable use. A file created once quickly loses value when categories disappear, products become unavailable, or URLs are redirected.

• Check the technology: The URL must return exactly HTTP status 200 and be readable as text.
• Test the links: Remove error pages, redirect chains, and noncanonical destinations.
• Compare the content: Do descriptions, product ranges, and service information still match the shop?
• Analyze server logs: Check which user agents request the file and whether destination pages are subsequently requested.
• Document changes: Version updates and measure effects over longer periods.

Do not assess the file solely on general visibility metrics. Changes in AI responses can have many causes. A reliable assessment combines log data, mentions, qualified referral traffic, and business metrics such as the conversion rate.

Who should implement it?

A Shopware llms.txt is most worthwhile for shops with products that require explanation, high-quality advisory content, and sufficient resources for ongoing maintenance. It is less urgent when basic crawling problems, weak product data, or major conversion barriers remain unresolved.

Start with a limited pilot project. Select one category, a few core products, and key advisory pages. Monitor requests and data quality for several months. Expand the file only when maintenance works reliably. This keeps the effort manageable and the outcome traceable.

Frequently asked questions about Shopware llms.txt

The most frequent questions concern the file’s benefits, location, creation, and update schedule.

Where is the llms.txt located in Shopware 6?

The file must be accessible at your shop’s public root URL, normally at https://your-domain.com/llms.txt. In self-hosted Shopware 6 installations, it is often stored in the public web directory. In cloud environments, the upload method depends on the hosting setup and the extension used.

Does an llms.txt replace robots.txt?

No. The robots.txt controls crawler access to areas of a website. An llms.txt is a curated table of contents for AI systems and has no binding control effect. The two files perform different tasks and can exist in parallel.

Does every Shopware shop need an llms.txt?

No. An llms.txt is not currently an established mandatory standard and does not guarantee better AI visibility. It can be worthwhile as a controlled test for shops with extensive content that requires explanation. Technical SEO, product data quality, and helpful content usually have higher priority.

How often should the file be updated?

Update the file whenever linked categories, products, policies, or URLs change substantially. Automated updates are advisable for dynamic product ranges. For smaller shops, a monthly or quarterly review cycle may be sufficient.

Conclusion

A Shopware llms.txt is an experimental, machine-readable guide to selected shop content, but not a guaranteed lever for AI visibility. Its greatest practical value currently lies in the controlled structuring of important URLs and in establishing a measurable test.

Implement the file only with a clear content selection, reliable updates, and log analysis. If fundamental SEO, product data, and conversion optimization still have gaps, address those tasks first.

Sources

¹ Ahrefs: We Analyzed 137K Sites: 97% of llms.txt Files Never Get Read (2026), https://ahrefs.com/blog/llmstxt-study/ (Last accessed: 29 July 2026)

² Ahrefs: We Analyzed 137K Sites: 97% of llms.txt Files Never Get Read (2026), https://ahrefs.com/blog/llmstxt-study/ (Last accessed: 29 July 2026)

³ Rankability: LLMS.txt Adoption Tracker (2026), https://www.rankability.com/data/llms-txt-adoption/ (Last accessed: 29 July 2026)