www.lalivenatural.com — llms.txt & GEO score

Agent Instructions — Lalive Natural

Nothing in this group is in place yet.

• Every link carries a description No links in the file, so there is nothing to describe
  0/10
• Descriptions say something concrete No links to measure
  0/7
• Descriptions add to the title No descriptions to compare against their titles
  0/4
• Points at clean markdown copies No links to point anywhere
  0/10
• Link titles are descriptive No link titles to judge
  0/4
• A workable number of links No links at all
  0/4
• Skippable links marked Optional Nothing is marked as skippable
  0/3
• No duplicate links No URLs to compare
  0/2
• List items are markdown links 34 of 34 list items are plain text, not links
  0/4
• Enough written detail per link No links to measure against
  0/3
• Links are absolute URLs No links to check
  0/1

4 of 7 checks pass. What is left: summary directly under the title, concrete language, not marketing filler and grouped into balanced sections.

• Exactly one H1 project title “Agent Instructions — Lalive Natural”
  3/3
• Summary directly under the title An opening paragraph is there, but not as a "> " blockquote — clients that look for the quoted summary will miss it
  2/3
• Summary is a usable length 119 characters (from the opening paragraph)
  3/3
• Concrete language, not marketing filler Found seamless
  2/3
• Grouped into balanced sections 5 H2 sections and 5 sub-headings
  2/4
• Conforms to the published grammar Markdown only, headings used as the spec defines them
  2/2
• Section names say what is inside All 5 headings are descriptive
  2/2

All 5 checks pass in this group.

• At the root of the domain you typed Found at the standard /llms.txt path
  2/2
• Sent as plain text Content-Type: text/markdown; charset=utf-8
  1/1
• robots.txt exists 3.6 KB of crawler rules
  1/1
• AI crawlers are not blocked No AI user-agent is disallowed at the root
  6/6
• robots.txt points at a sitemap A Sitemap: line is declared
  1/1

All 6 checks pass in this group.

• Homepage title is the right length 43 characters, from title
  2/2
• Title is not padded or repetitive No repeated terms
  1/1
• Homepage has a meta description 153 characters, from meta description
  2/2
• Canonical URL declared https://www.lalivenatural.com/
  1/1
• Language declared lang="tr"
  1/1
• Social card image og:image is set
  1/1

2 of 5 checks pass. What is left: the index points at the full file, server reports when it last changed and the index is kept current.

• Publishes llms-full.txt Companion full-text file found
  3/3
• The index points at the full file Not linked from llms.txt
  0/1
• Index is a sensible size 4.4 KB
  2/2
• Server reports when it last changed No Last-Modified header — clients cannot tell when this changed
  0/1
• The index is kept current Cannot be confirmed — the server sends no Last-Modified header
  0/2

• A workable number of links Content & links +4

  Right now: No links at all

  Either curate to roughly 10–40 links, or go the other way and map everything to .md copies. The costly middle is a long list of HTML links with no descriptions.

  Where: The link lists in llms.txt

  1. Aim for roughly 10–40 curated links.
  2. Above about fifty, a model has to read the whole file before it can choose, and every entry gets diluted.
  3. If you generated the file from a sitemap, delete most of it: curation is the entire value of the format.
  4. Below ten, add the pages you would send a new customer to first.
• List items are markdown links Content & links +4

  Right now: 34 of 34 list items are plain text, not links

  A file list needs `- [Title](url): description`. A plain line gives a model something to read but nowhere to go — it cannot follow it, quote it, or check it.

  Where: Every "- " line in llms.txt

  1. Turn each plain line into a markdown link: "- [Title](https://your-site/page.md): description".
  2. A line without a URL gives a model something to read but nowhere to go — it cannot follow, quote or verify it.
  3. If a fact has no page behind it (an address, a phone number), put it in the free-text body above the sections, not in a file list.
  4. Note that "#" is a heading in markdown, not a comment — lines starting with # become H1/H2 headings.

  In your file

  line 15

  - Cross-store catalog search and price/discount discovery

  - [Cross-store catalog search and price/discount discovery]({https://your-site/path}.md): {what this page covers}

  line 16

  - Buyer-approved checkout via Shop Pay (no card-handling on the agent's part)

  - [Buyer-approved checkout via Shop Pay (no card-handling on the agent's part)]({https://your-site/path}.md): {what this page covers}

  line 17

  - Order tracking

  - [Order tracking]({https://your-site/path}.md): {what this page covers}

  Placeholders in { } are yours to write — we do not invent text about your pages.

• Skippable links marked Optional Content & links +3

  Right now: Nothing is marked as skippable

  Move the nice-to-haves under ## Optional so a model on a tight budget knows what to drop first.

  Where: A new "## Optional" section at the end of llms.txt

  1. Move the nice-to-have links — history, press, careers — under "## Optional".
  2. By convention a client may skip that whole section when context is tight.
  3. This is you deciding what gets dropped first, instead of the model guessing.

  Do this

  ## Optional
  
  - [Company history](https://acme.example/about.md): Background, not needed to answer product questions

• Grouped into balanced sections Structure +2

  Right now: 5 H2 sections and 5 sub-headings

  Group links under headings a reader would look for, and spread them — one group holding most of the file is the same as no grouping.

  Where: The "## " headings in llms.txt

  1. Split the link list into at least five "## " groups by what a reader would be looking for.
  2. Typical split: Docs, API, Guides, Product, Company, Optional.
  3. Grouping is what lets a model skip nine tenths of the file and still find the right page.

  Instead of

  ## Links
  
  - [A](...)
  - [B](...)
  - [C](...)

  Do this

  ## Docs
  
  - [A](...)
  
  ## API
  
  - [B](...)
  
  ## Optional
  
  - [C](...)

• The index is kept current Depth & upkeep +2

  Right now: Cannot be confirmed — the server sends no Last-Modified header

  Regenerate llms.txt when the docs change. A year-old index quietly points models at pages that have moved.

  Where: Your build pipeline

  1. Regenerate llms.txt in the same step that publishes content, so it cannot go stale silently.
  2. Treat it as a build artifact, not a hand-edited file — hand-edited indexes drift within a quarter.
  3. An llms.txt with discontinued products is worse than none: a model will repeat the wrong facts confidently.
• Concrete language, not marketing filler Structure +1

  Right now: Found seamless

  Say what you do, for whom, with what result. If a competitor could paste your sentence unchanged, it says nothing.

  Where: The summary and link descriptions

  1. Delete the filler words this check flagged — innovative, cutting-edge, world-class, seamless, leading provider.
  2. Replace each with the concrete thing it was standing in for: a number, a place, a material, a limit.
  3. Test: if a competitor could paste your sentence onto their site unchanged, it says nothing.

  In your file

  line 79

  This store is built on [Shopify](https://www.shopify.com), the commerce platform powering millions of stores worldwide. Shopify stores support UCP natively, enabling seamless agent-driven commerce. The Shop skill at

  Placeholders in { } are yours to write — we do not invent text about your pages.

• Server reports when it last changed Depth & upkeep +1

  Right now: No Last-Modified header — clients cannot tell when this changed

  Let the server send Last-Modified on llms.txt. Without it a client has to re-download the whole file to notice a change.

  Where: Your web server configuration

  1. Serve llms.txt as a real file on disk so the server can derive Last-Modified from its mtime.
  2. If it is generated by an application route, set the header yourself from the generation time.
  3. Without it a client has to re-download the whole file to notice a change, and cannot answer "is this current?".

  Instead of

  HTTP/1.1 200 OK\nContent-Type: text/plain

  Do this

  HTTP/1.1 200 OK\nContent-Type: text/plain\nLast-Modified: Wed, 10 Sep 2026 08:14:00 GMT

• Summary directly under the title Structure +1

  Right now: An opening paragraph is there, but not as a "> " blockquote — clients that look for the quoted summary will miss it

  Put the opening line in a > blockquote. The spec calls it optional, but it is the first thing a model reads and often the only thing it quotes back.

  Where: The line directly under the H1

  1. Add a single line starting with "> ".
  2. Answer three things in it: what you do, for whom, and what makes it specific.
  3. This is the sentence a model is most likely to quote back, so write it last, after the rest of the file.

  Instead of

  > We are an innovative company delivering world-class solutions.

  Do this

  > Industrial spare parts for food processing lines, shipped across Europe with same-week dispatch.

• The index points at the full file Depth & upkeep +1

  Right now: Not linked from llms.txt

  Mention llms-full.txt inside llms.txt. Guessing the filename works often enough to be tempting and not often enough to rely on.

  Where: Inside llms.txt

  1. Mention the full file in llms.txt itself, as a link or a line of context.
  2. Guessing the filename works often enough to be tempting and not often enough to rely on.

  Do this

  Full inlined text: https://acme.example/llms-full.txt

This score is Devsly’s own heuristic, not an official standard — llms.txt has no scoring body. It measures how well a file serves an AI assistant, and it does not predict whether any assistant will cite the site. The reading is a snapshot from 21 September 2026; run it again for the current state, or check a different site.