www.infotechacademy.com.tr — llms.txt & GEO score

Infotech Academy

Infotech Academy, Türkiye'nin önde gelen bilgi teknolojileri eğitim kurumudur. Alanında aktif saha tecrübesine sahip uzman eğitmenlerle, uygulamaya yönelik, güncel ve sertifikalı IT eğitimleri sunar. Bireysel ve kurumsal eğitim hizmetlerinin yanı sıra proje geliştirme ve danışmanlık hizmetleri de verilmektedir.

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

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

6 of 7 checks pass. What is left: grouped into balanced sections.

• Exactly one H1 project title “Infotech Academy”
  3/3
• Summary directly under the title Present as a blockquote
  3/3
• Summary is a usable length 312 characters
  3/3
• Concrete language, not marketing filler No marketing filler detected
  3/3
• Grouped into balanced sections 7 H2 sections and 8 sub-headings, largest group holds 13 of 32 links
  3/4
• Conforms to the published grammar Markdown only, headings used as the spec defines them
  2/2
• Section names say what is inside All 7 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 1.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 66 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 152 characters, from meta description
  2/2
• Canonical URL declared https://www.infotechacademy.com.tr/
  1/1
• Language declared lang="tr-TR"
  1/1
• Social card image og:image is set
  1/1

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

• 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 9.5 KB
  2/2
• Server reports when it last changed Server sends Last-Modified
  1/1
• The index is kept current 190 days old
  1/2

• Points at clean markdown copies Content & links +10

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

  - [Yazılım Uzmanlığı Eğitimi (MCSD)](https://www.infotechacademy.com.tr/egitim/yazilim-uzmanligi-egitimi-mcsd): C#, OOP, ASP.NET Core MVC, SQL Server ve proje geliştirmeyi kapsayan kapsamlı yazılım uzmanlığı programı.

  - [Yazılım Uzmanlığı Eğitimi (MCSD)](https://www.infotechacademy.com.tr/egitim/yazilim-uzmanligi-egitimi-mcsd.md): C#, OOP, ASP.NET Core MVC, SQL Server ve proje geliştirmeyi kapsayan kapsamlı yazılım uzmanlığı programı.

  line 45

  - [Kurumsal ASP.NET Core MVC Web Tasarım/Yazılım Eğitimi](https://www.infotechacademy.com.tr/egitim/kurumsal-asp-net-core-mvc-web-tasarimyazilim-egitimleri): .NET Core altyapısında kurumsal web uygulama geliştirme.

  - [Kurumsal ASP.NET Core MVC Web Tasarım/Yazılım Eğitimi](https://www.infotechacademy.com.tr/egitim/kurumsal-asp-net-core-mvc-web-tasarimyazilim-egitimleri.md): .NET Core altyapısında kurumsal web uygulama geliştirme.

  line 46

  - [Kurumsal TypeScript Programlama Eğitimi](https://www.infotechacademy.com.tr/egitim/kurumsal-typescript-programlama-egitimi): JavaScript'in OOP uyumlu, güvenilir sürümü TypeScript.

  - [Kurumsal TypeScript Programlama Eğitimi](https://www.infotechacademy.com.tr/egitim/kurumsal-typescript-programlama-egitimi.md): JavaScript'in OOP uyumlu, güvenilir sürümü TypeScript.

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

• List items are markdown links Content & links +3

  Right now: 32 of 64 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 5

  - Web sitesi: https://www.infotechacademy.com.tr

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

  line 6

  - İletişim: [email protected]

  - [İletişim]({https://your-site/path}.md): {what this page covers}

  line 7

  - Telefon: +90 212 909 21 89

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

  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

• Descriptions say something concrete Content & links +1

  Right now: Average 55 characters across 32 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 49

  - [React JS ile Front-End Web Uygulamaları Geliştirme](https://www.infotechacademy.com.tr/egitim/react-js-ile-front-end-web-uygulamalari-gelistirme-egitimi): Sıfırdan ileri seviyeye React JS eğitimi.

  - [React JS ile Front-End Web Uygulamaları Geliştirme](https: {what is on the page — numbers, limits, formats}

  line 50

  - [Blazor Eğitimi Front-End Kursu](https://www.infotechacademy.com.tr/egitim/blazor-egitimi-front-end-kursu): Blazor ile modern web uygulaması geliştirme.

  - [Blazor Eğitimi Front-End Kursu](https: {what is on the page — numbers, limits, formats}

  line 67

  - [Java Android Geliştirme Uzmanlığı Eğitimi](https://www.infotechacademy.com.tr/egitim/java-android-gelistirme-uzmanligi-egitimi): Java ile Android uygulama geliştirme.

  - [Java Android Geliştirme Uzmanlığı Eğitimi](https: {what is on the page — numbers, limits, formats}

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

• Grouped into balanced sections Structure +1

  Right now: 7 H2 sections and 8 sub-headings, largest group holds 13 of 32 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](...)

• The index is kept current Depth & upkeep +1

  Right now: 190 days old

  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.
• 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.