kafindustries.com — llms.txt & GEO score

KAF Industries

KAF Industries is an Istanbul-based industrial trading and sourcing company with nearly 50 years of combined sector experience. It operates six business groups: cryogenic equipment (sales of new and used tanks, repair, maintenance, refurbishment and rental), industrial and specialty gases (trading and supply partner, not a producer), steel (authorized Türkiye sales representative of DKC Stainless of South Korea for hot-rolled stainless plates; carbon steel; project-based dished head coordination), textile (the Tekstil A.S. family), international trade and sourcing (calcium carbide, perlite, selected chemicals, project-based sourcing) and business advisory. KAF Industries is not a manufacturer; it is a trading, supply and coordination partner.

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

• Every link carries a description 16 of 16 described (100%)
  10/10
• Descriptions say something concrete Average 110 characters across 16 described links
  7/7
• Descriptions add to the title No description merely repeats its title
  4/4
• Points at clean markdown copies 0 of 16 end in .md or .txt (0%, detected by file extension)
  0/10
• Link titles are descriptive 7 weak titles (bare URLs, “here”, one-word labels)
  0/4
• A workable number of links 16 links (12–50 is the sweet spot)
  4/4
• Skippable links marked Optional Nothing is marked as skippable
  0/3
• No duplicate links All 16 URLs are distinct
  2/2
• List items are markdown links 7 of 23 list items are plain text, not links
  2/4
• Enough written detail per link 45 words per link across 727 words
  3/3
• Links are absolute URLs All 16 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 Industries”
  3/3
• Summary directly under the title Present as a blockquote
  3/3
• Summary is a usable length 752 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 16 of 16 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 51 characters, from title
  2/2
• Title is not padded or repetitive No repeated terms
  1/1
• Homepage has a meta description 160 characters, from meta description
  2/2
• Canonical URL declared https://kafindustries.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 5.6 KB
  2/2
• Server reports when it last changed Server sends Last-Modified
  1/1
• The index is kept current 61 days old
  2/2

• Points at clean markdown copies Content & links +10

  Right now: 0 of 16 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

  - [Business Groups](https://kafindustries.com/business-groups/): Overview of all six business groups

  - [Business Groups](https://kafindustries.com/business-groups.md): Overview of all six business groups

  line 13

  - [Cryogenic Equipment](https://kafindustries.com/business-groups/cryogenics/): New and used cryogenic tanks, repair and refurbishment, rental of tanks, trailers and ISO containers

  - [Cryogenic Equipment](https://kafindustries.com/business-groups/cryogenics.md): New and used cryogenic tanks, repair and refurbishment, rental of tanks, trailers and ISO containers

  line 14

  - [Gases](https://kafindustries.com/business-groups/gases/): Industrial gases, specialty and high-purity gases, CO2, nitrous oxide; international supply partner

  - [Gases](https://kafindustries.com/business-groups/gases.md): Industrial gases, specialty and high-purity gases, CO2, nitrous oxide; international supply partner

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

• Link titles are descriptive Content & links +4

  Right now: 7 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://kafindustries.com/): Company overview, six business groups, FAQ

  - [{the page’s real name}](https://kafindustries.com/): Company overview, six business groups, FAQ

  line 14

  - [Gases](https://kafindustries.com/business-groups/gases/): Industrial gases, specialty and high-purity gases, CO2, nitrous oxide; international supply partner

  - [{the page’s real name}](https://kafindustries.com/business-groups/gases/): Industrial gases, specialty and high-purity gases, CO2, nitrous oxide; international supply partner

  line 15

  - [Steel](https://kafindustries.com/business-groups/steel/): DKC Stainless authorized representation, hot-rolled stainless plates in wide and custom dimensions, carbon steel, dished heads

  - [{the page’s real name}](https://kafindustries.com/business-groups/steel/): DKC Stainless authorized representation, hot-rolled stainless plates in wide and custom dimensions, carbon steel, dished heads

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

• 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: 752 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.
• List items are markdown links Content & links +2

  Right now: 7 of 23 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 36

  - KAF Industries sells and rents both new and used cryogenic tanks; every used tank is inspected for vacuum condition, service history, pressure class and code compliance before sale.

  - [KAF Industries sells and rents both new and used cryogenic tanks; every used tank is inspected for vacuum condition, service history, pressure class and code compliance before sale.]({https://your-site/path}.md): {what this page covers}

  line 37

  - KAF Industries is the authorized sales representative of DKC Stainless (South Korea) in Türkiye; DKC specializes in hot-rolled stainless steel plates, ordered mill-direct in project-specific and wide dimensions.

  - [KAF Industries is the authorized sales representative of DKC Stainless (South Korea) in Türkiye; DKC specializes in hot-rolled stainless steel plates, ordered mill-direct in project-specific and wide dimensions.]({https://your-site/path}.md): {what this page covers}

  line 38

  - KAF Industries supplies dished heads (elliptical and torispherical) as a production coordinator working with qualified manufacturers, not as a manufacturer.

  - [KAF Industries supplies dished heads (elliptical and torispherical) as a production coordinator working with qualified manufacturers, not as a manufacturer.]({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.