A map of your site for AI (llms.txt)

A map of your site for AI (llms.txt) for Site app

llms.txt site map for AI assistants and search

5.0 1 rating

Basic Premium

Free

Install A map of your site for AI (llms.txt) plugin directly from your Webasyst backend using the Installer app.

Your review
Installs
70+
Developer
Support
License
LGPL
Version
1.0.1
Updated
August 18, 2026
Minimal requirements
  • PHP version >=7.4
  • Version of Framework >=2.7.0
  • App Site

More and more often people don't scroll through search results - they ask a neural network or a voice assistant: "who does this", "where can I order", "recommend a company". The assistant builds its answer from websites it managed to understand correctly. The plugin generates llms.txt - a clean map of your website for AI: pages, services, articles and contacts in a form neural networks read directly, without guessing.

According to Adobe, AI-referred traffic to websites has grown severalfold in a year (in e-commerce - by 393%) and converts noticeably better than regular search. The llms.txt map is what puts your company and your facts into the AI answer - instead of guesses, or a competitor.

How AI decides what to recommend

The same visitor - two different endings

When AI answers a question about a service or a company, it looks at your site. The difference is what it actually sees there - and that decides whether the client comes to you or to a competitor.

Without llms.txt

  1. A person asks AI: "who does …", "where can I order …".
  2. The agent lands on raw HTML: menus, banners, scripts, popups.
  3. It has to guess - mixes up services, picks stale contacts or the wrong description.

→ recommends a competitor or gets your facts wrong

With llms.txt

  1. The same question to the same AI.
  2. The agent reads a clean map: sections, service pages, articles, contacts.
  3. It answers with facts - your real names, services and terms.

→ recommends your site, the client comes to you

AI search & chat assistants

People ask AI - and leave the request on your site

The 2026 scenario is simple: they find a company through AI - then visit the site and submit a request. The assistant builds its answer from live search: it picks sites it trusts and cites their facts. It will recommend you with far more confidence when, instead of raw HTML, it has a ready llms.txt map - with your sections, services and contacts.

  • ChatGPTChatGPT
  • GeminiGemini
  • ClaudeClaude
  • PerplexityPerplexity
  • DeepSeekDeepSeek

Working with the Russian-speaking market too? There Alice (Yandex) leads AI search, alongside YandexGPT and GigaChat.

Seen live in AI search

AI search already explains why your website needs llms.txt

These aren't our words. Ask AI-powered search "why is llms.txt important for a business website" - and the AI answer calls llms.txt a structured, easy-to-read summary of the site that helps ChatGPT, Perplexity, Gemini and Claude cite current, authoritative pages - and it links its sources. Your site lands in answers like these once it has a ready llms.txt map.

AI search answer explaining why llms.txt is important for a business website, with cited sources

A real AI search answer (Bing) on "why is llms.txt important for a business website" - with the sources it cites.

Voice assistants

Assistants answer by voice - and they live everywhere, not just in a speaker

Voice assistants live on the phone, in apps, browsers, cars and TVs - not only in a smart speaker. When someone asks out loud "recommend someone who does this" or "find where to order", the answer is built by the assistant's AI model - and it needs a clear source of facts about your company.

How this ties to the llms.txt map. The speaker or assistant doesn't read your site itself - it passes the question to its AI model. To answer, the model turns to AI search, which pulls data from websites and classic search engines. Your site's data is easier and more accurate for AI search to take from a ready llms.txt map than to parse raw HTML. The chain is simple:

Client's voice Assistant's AI model AI search Site data + classic search llms.txt = your site's data, readable

The three ecosystems that answer by voice in the West:

  • AlexaAmazon Alexa
  • GoogleGoogle Assistant
  • SiriApple Siri

And for the Russian-speaking market (RU/CIS), if you work there too:

  • AliceAlice · Yandex
  • VKMarusia · VK
  • SberSalut · Sber

Smart speakers and in-car assistants are already in millions of homes and vehicles. If a person doesn't name a company, the assistant picks one itself - all the more important that your site is clear to it.

Why this plugin

Not a one-off file, but part of a system

  • Builds itself, nothing extra leaks. The map is generated from your published site pages and Blog app posts (if the Blog app is installed) and updates on changes. Drafts and unpublished pages never enter it - only what is publicly visible.
  • Your facts for AI stay in your hands. Contacts plus a short and a detailed company description are set in the plugin settings and land at the very top of the map - that is exactly what AI answers with.
  • Correct encoding on any host. The map is served by the site engine (like robots.txt) - always clean UTF-8, no broken characters that plain static files hit on some hosts. It never touches your theme, speed or classic SEO.
  • Part of the KakTak.Net line. llms.txt is your site map for AI; alongside it work our Schema.org (JSON-LD) markup (the essence of every page - organization, articles, breadcrumbs) and IndexNow (instant updates in search): one style, one support, one ecosystem - instead of scattered utilities from different authors.
Stronger together

llms.txt guides AI through your site, markup and IndexNow close the loop

These are parts of one system for making your site AI-ready. llms.txt is the map: it shows the AI where your sections, services and articles are (where to go). Schema.org (JSON-LD) markup is the detail of every page: who you are, what you offer, how to get in touch (what to show). IndexNow instantly tells search engines about changes, so AI sees fresh data. Together they close the loop: a person asks AI - AI answers with your facts - the client comes to you - and finds you again through AI.

A person asks AI llms.txt - site map JSON-LD - page detail IndexNow - freshness AI recommends - the client is yours

Three plugins from one KakTak.Net line - map, detail and freshness - make a site AI-ready together. Start with llms.txt and add the others as you need them.

Base and premium

Base is free - all domains in premium

Base free

  • Your primary site domain.
  • Full map: llms.txt and llms-full.txt - sections, pages, articles, contacts.
  • Updates on a schedule and by one button.

Premium multi-domain

  • All Site settlements on different domains - at once, automatically.
  • Separate descriptions and contacts per domain.
  • For anyone running several sites and landing pages from one panel.

The base edition is free - the map covers the whole site with no page limit and updates itself along with your content.

How it works

Quietly, in the background, hands-off

  • One click builds llms.txt and llms-full.txt; then the files update themselves when pages change (on a schedule) or manually.
  • The ready file is served instantly - built ahead of time, not on a visitor's request, and it never loads the site.
  • llms.txt is the short map for a quick first read; llms-full.txt is the detailed one, with page texts (length is configurable).
  • Full control: the language of service labels (English, Russian, Ukrainian), rebuild, view and reset settings any time.

Honest by design. No AI platform is required to read llms.txt, and it does not lift Google rankings - Google has said so directly. This is not a traffic trick but base infrastructure for the AI-agent era: the effect grows with AI search and is strongest paired with Schema.org markup and instant IndexNow re-indexing. The plugin makes your site machine-readable and honestly described - so when an assistant reads, it reads facts, not guesses.

KakTak.Net

All products of this developer