Unomage llms.txt Generatorllms.txt for jotunn.eu
Jotunn d.o.o. publishes legal content across 3 pages.
Sections
Toggle a section off to exclude it from both files below — updates instantly, no re-crawl needed.
llms.txt
# Jotunn d.o.o. > Jotunn d.o.o. publishes legal content across 3 pages. ## Optional - [Jotunn d.o.o. | Magento / Adobe Commerce Engineering](https://jotunn.eu/): Jotunn d.o.o. is a Croatia-based software company providing Magento and Adobe Commerce engineering for backend-heavy ecommerce systems. - [Adobe Commerce Price Index Failure: Diagnosis and Stabilization | Jotunn](https://jotunn.eu/case-studies/price-index-collapse/): A technical case study on a 125-million-row Adobe Commerce price index table, the production symptoms it caused, and the stabilization work that reduced pressu… - [Jotunn d.o.o. | Legal](https://jotunn.eu/legal/): Company details, privacy information, and cookie information for Jotunn d.o.o.
llms-full.txt (convention, not spec)
# Jotunn d.o.o. — full text > This file is a widely-used convention, not part of the llms.txt proposal. It concatenates the content of the pages listed in llms.txt (excluding the Optional section) so an agent can read everything in one request instead of fetching each page.
Compared to what's already published
No existing llms.txt was found at this domain's root — this would be a new file.
How to install this
WordPress
Most WordPress page builders — including Kadence, the theme this site itself runs on — cannot create a root-level static file. Two options: (1) a small plugin or must-use plugin that adds a rewrite rule so `/llms.txt` returns the file content with `Content-Type: text/plain` (register via `add_rewrite_rule()` and flush rewrite rules once), or (2) if you have SFTP/file-manager access to the server, upload `llms.txt` directly to your WordPress installation's document root (the same folder as `wp-config.php`) — Apache/Nginx will then serve it as a static file with no PHP involved, which is simpler and faster if you can do it.
Static site / Netlify / Vercel
Drop the downloaded `llms.txt` (and `llms-full.txt`) straight into your `public/` (or equivalent static assets) folder and redeploy. It will be served at `/llms.txt` automatically, with no further configuration.
Next.js
App Router: place `llms.txt` in the `public/` folder — it is served at `/llms.txt` automatically. If you want it generated dynamically instead, add an `app/llms.txt/route.ts` file that returns the text with `Content-Type: text/plain`.
Nginx / Apache (own server)
Upload `llms.txt` and `llms-full.txt` to your site's document root. Both servers serve a static file at the matching path with no configuration needed, as long as `.txt` isn't explicitly blocked. Confirm the response has `Content-Type: text/plain` (add a `types` / `AddType` entry if your server defaults to `application/octet-stream` for unknown extensions).
Behind Cloudflare (any backend)
If your origin can't easily serve a static file at root (e.g. a locked-down CMS), a Cloudflare Worker or a Page Rule can intercept `GET /llms.txt` and return the saved text directly, without touching your origin server at all.
Does this do anything?
Publishing this file costs nothing and might help a little with Anthropic's and Perplexity's crawlers — Google and OpenAI show no confirmed use of it as of September 2026. It does not fix a JavaScript-only page, a blocked crawler, or thin content. Treat it as a free, low-effort addition, not a strategy.
llms.txt is the easy part. The things that actually block AI crawlers are harder to see.