kafcryogenics.com — llms.txt & GEO score

KAF Cryogenics

KAF Cryogenics works on cryogenic, LNG, LPG and LCO2 equipment, pressure vessels, dished heads and related engineering support for industrial gas, energy and process applications. The scope covers cryogenic storage tanks for LIN, LOX and LAR, LNG storage and regasification equipment, LPG storage and transfer systems, LCO2 storage and transport tanks, ambient vaporizers, pressure vessels, dished heads, power generation packages, engineering support, repair and maintenance, spare parts and used equipment. Equipment configurations are reviewed against the design code applicable to the destination market and application (ASME Section VIII, EN 13458, EN 13530, EN 13445, EN 12542, AD 2000 and the EU Pressure Equipment Directive PED 2014/68/EU), with quality, environmental and welding management referenced to ISO 9001, ISO 14001 and ISO 3834-2.

6 of 11 checks pass. What is left: descriptions say something concrete, points at clean markdown copies, link titles are descriptive, skippable links marked Optional and list items are markdown links.

• Every link carries a description 17 of 17 described (100%)
  10/10
• Descriptions say something concrete Average 71 characters across 17 described links
  6/7
• Descriptions add to the title No description merely repeats its title
  4/4
• Points at clean markdown copies 0 of 17 end in .md or .txt (0%, detected by file extension)
  0/10
• Link titles are descriptive 4 weak titles (bare URLs, “here”, one-word labels)
  1/4
• A workable number of links 17 links (12–50 is the sweet spot)
  4/4
• Skippable links marked Optional Nothing is marked as skippable
  0/3
• No duplicate links All 17 URLs are distinct
  2/2
• List items are markdown links 5 of 22 list items are plain text, not links
  3/4
• Enough written detail per link 33 words per link across 568 words
  3/3
• Links are absolute URLs All 17 links are absolute URLs
  1/1

5 of 7 checks pass. What is left: summary is a usable length and grouped into balanced sections.

• Exactly one H1 project title “KAF Cryogenics”
  3/3
• Summary directly under the title Present as a blockquote
  3/3
• Summary is a usable length 849 characters — too long
  0/3
• Concrete language, not marketing filler No marketing filler detected
  3/3
• Grouped into balanced sections 3 H2 sections, largest group holds 17 of 17 links
  1/4
• Conforms to the published grammar Markdown only, headings used as the spec defines them
  2/2
• Section names say what is inside All 3 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/plain
  1/1
• robots.txt exists 71 B 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 62 characters, from title — will be cut off
  2/2
• Title is not padded or repetitive No repeated terms
  1/1
• Homepage has a meta description 202 characters, from meta description — Google will truncate it
  2/2
• Canonical URL declared https://kafcryogenics.com/
  1/1
• Language declared lang="en"
  1/1
• Social card image og:image is set
  1/1

3 of 5 checks pass. What is left: publishes llms-full.txt and the index points at the full file.

• Publishes llms-full.txt No llms-full.txt alongside the index
  0/3
• The index points at the full file No llms-full.txt exists to link to
  0/1
• Index is a sensible size 4.8 KB
  2/2
• Server reports when it last changed Server sends Last-Modified
  1/1
• The index is kept current Last changed 17 days ago
  2/2

• Points at clean markdown copies Content & links +10

  Right now: 0 of 17 end in .md or .txt (0%, detected by file extension)

  Publish a .md version of each page and link to that. The single biggest win here: the model reads your content instead of your navigation and footer.

  Where: Your CMS or docs build — this is the biggest single win here

  1. Publish a .md version of each page you link to, at a predictable URL (page.md next to page).
  2. Point the llms.txt links at the .md copies, not at the HTML pages.
  3. Strip navigation, cookie banners and footers from the markdown — that is the whole point: the model reads your content instead of your chrome.
  4. Declare the pair in your HTML with a link relation so clients can find it without guessing.

  In your file

  line 12

  - [About](https://kafcryogenics.com/about/): Company overview, quality policy, health and safety policy, standards and certifications, statutory company registration details

  - [About](https://kafcryogenics.com/about.md): Company overview, quality policy, health and safety policy, standards and certifications, statutory company registration details

  line 13

  - [Equipment Categories](https://kafcryogenics.com/products/): Overview of all eleven equipment categories

  - [Equipment Categories](https://kafcryogenics.com/products.md): Overview of all eleven equipment categories

  line 14

  - [Cryogenic Storage Tanks](https://kafcryogenics.com/products/cryogenic-storage-tanks/): Vertical and horizontal vacuum insulated tanks for LIN, LOX and LAR

  - [Cryogenic Storage Tanks](https://kafcryogenics.com/products/cryogenic-storage-tanks.md): Vertical and horizontal vacuum insulated tanks for LIN, LOX and LAR

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

• Grouped into balanced sections Structure +3

  Right now: 3 H2 sections, largest group holds 17 of 17 links

  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](...)

• Link titles are descriptive Content & links +3

  Right now: 4 weak titles (bare URLs, “here”, one-word labels)

  Replace bare URLs and “click here” with the page’s real name — the title is half the signal.

  Where: The "[Title]" part of each link

  1. Replace bare URLs, "here", "click here" and one-word labels with the page’s real name.
  2. The title is half the signal — a model reads it before it reads your description.

  In your file

  line 11

  - [Home](https://kafcryogenics.com/): Equipment categories, industries served, scope of services

  - [{the page’s real name}](https://kafcryogenics.com/): Equipment categories, industries served, scope of services

  line 12

  - [About](https://kafcryogenics.com/about/): Company overview, quality policy, health and safety policy, standards and certifications, statutory company registration details

  - [{the page’s real name}](https://kafcryogenics.com/about/): Company overview, quality policy, health and safety policy, standards and certifications, statutory company registration details

  line 25

  - [FAQ](https://kafcryogenics.com/faq/): Technical questions and answers grouped by equipment category

  - [{the page’s real name}](https://kafcryogenics.com/faq/): Technical questions and answers grouped by equipment category

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

• Publishes llms-full.txt Depth & upkeep +3

  Right now: No llms-full.txt alongside the index

  Generate an llms-full.txt that inlines every linked page. Community convention rather than spec, but assistants with a large context window take the whole thing in one request.

  Where: Your docs build, output at /llms-full.txt

  1. Concatenate the markdown of every page listed in llms.txt into one file.
  2. Keep the heading structure: a client uses those headings to navigate a multi-megabyte file.
  3. Regenerate it in the same build step that publishes the docs, so it cannot drift.
  4. Note that llms-full.txt is a community convention, not part of the proposal — useful, but optional.
• 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

• Summary is a usable length Structure +3

  Right now: 849 characters — too long

  Aim for 80–350 characters: one or two sentences that make sense read aloud on their own.

  Where: The "> " line in llms.txt

  1. Aim for 80–350 characters: one or two sentences that stand on their own when read aloud.
  2. Under 80 and it says nothing specific; over 350 and a model summarises your summary.
  3. Cut adjectives first — they are the part that carries no information.
• Descriptions say something concrete Content & links +1

  Right now: Average 71 characters across 17 described links

  Write 60+ characters that add information the title does not: numbers, limits, formats, names.

  Where: The text after ": " on each link

  1. Write 60 characters or more, and make them add information the title does not.
  2. Cover every link: this is measured per LINK, not per description, so an undescribed line counts as zero.
  3. Name the concrete things on the page: numbers, limits, formats, model names.
  4. If the description could be pasted under any other link, it is not a description yet.

  In your file

  line 13

  - [Equipment Categories](https://kafcryogenics.com/products/): Overview of all eleven equipment categories

  - [Equipment Categories](https: {what is on the page — numbers, limits, formats}

  line 26

  - [Request Equipment](https://kafcryogenics.com/request-equipment/): Short structured equipment request form

  - [Request Equipment](https: {what is on the page — numbers, limits, formats}

  line 27

  - [Contact](https://kafcryogenics.com/contact/): Contact form and direct contact details

  - [Contact](https: {what is on the page — numbers, limits, formats}

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

• List items are markdown links Content & links +1

  Right now: 5 of 22 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 35

  - Equipment requests are reviewed against the technical parameters that define this equipment category: capacity, MAWP, orientation, insulation type, medium and applicable design code.

  - [Equipment requests are reviewed against the technical parameters that define this equipment category: capacity, MAWP, orientation, insulation type, medium and applicable design code.]({https://your-site/path}.md): {what this page covers}

  line 36

  - The applicable design code depends on the destination market and application; equipment is configured to the code the project requires.

  - [The applicable design code depends on the destination market and application; equipment is configured to the code the project requires.]({https://your-site/path}.md): {what this page covers}

  line 37

  - Technical documentation (datasheets, drawings, material and test certificates) is provided per project according to the scope agreed for that order.

  - [Technical documentation (datasheets, drawings, material and test certificates) is provided per project according to the scope agreed for that order.]({https://your-site/path}.md): {what this page covers}

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

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

  Right now: No llms-full.txt exists to link to

  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.