dentumitkoy.com — llms.txt & GEO score

Dent Ümitköy

Dent Ümitköy (yasal unvanı: Dent Ümitköy Ağız ve Diş Sağlığı Polikliniği Ticaret Limited Şirketi), 2007 yılından beri Ankara Ümitköy'de Dt. Songül Mirzaoğlu ve uzman ekibi tarafından işletilen bir ağız ve diş sağlığı polikliniğidir. İmplant, Dijital Gülüş Tasarımı (Digital Smile Design - DSD), CAD/CAM sistemleriyle zirkonyum ve porselen kaplama, diş beyazlatma, diş laminesi, estetik ve temel diş hekimliği hizmetleri sunulmaktadır.

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

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

6 of 7 checks pass. What is left: summary is a usable length.

• Exactly one H1 project title “Dent Ümitköy”
  3/3
• Summary directly under the title Present as a blockquote
  3/3
• Summary is a usable length 434 characters — too long
  2/3
• Concrete language, not marketing filler No marketing filler detected
  3/3
• Grouped into balanced sections 7 H2 sections, largest group holds 12 of 28 links
  4/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; charset=utf-8
  1/1
• robots.txt exists 771 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 60 characters, from title
  2/2
• Title is not padded or repetitive No repeated terms
  1/1
• Homepage has a meta description 154 characters, from meta description
  2/2
• Canonical URL declared https://dentumitkoy.com
  1/1
• Language declared lang="tr"
  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 Last changed 0 days ago
  2/2

• Points at clean markdown copies Content & links +10

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

  - [Hakkımızda](https://dentumitkoy.com/hakkimizda): Klinik hikayesi, kurucu hekim ve değerler.

  - [Hakkımızda](https://dentumitkoy.com/hakkimizda.md): Klinik hikayesi, kurucu hekim ve değerler.

  line 15

  - [Ekibimiz](https://dentumitkoy.com/ekibimiz): Diş hekimleri ve klinik kadrosu.

  - [Ekibimiz](https://dentumitkoy.com/ekibimiz.md): Diş hekimleri ve klinik kadrosu.

  line 16

  - [İletişim](https://dentumitkoy.com/iletisim): Adres, telefon, çalışma saatleri.

  - [İletişim](https://dentumitkoy.com/iletisim.md): Adres, telefon, çalışma saatleri.

  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 +2

  Right now: Average 52 characters across 25 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 14

  - [Hakkımızda](https://dentumitkoy.com/hakkimizda): Klinik hikayesi, kurucu hekim ve değerler.

  - [Hakkımızda](https: {what is on the page — numbers, limits, formats}

  line 15

  - [Ekibimiz](https://dentumitkoy.com/ekibimiz): Diş hekimleri ve klinik kadrosu.

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

  line 16

  - [İletişim](https://dentumitkoy.com/iletisim): Adres, telefon, çalışma saatleri.

  - [İletişim](https: {what is on the page — numbers, limits, formats}

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

• Enough written detail per link Content & links +2

  Right now: 20 words per link across 559 words

  A list of names is not documentation. Aim for 30+ words per link across the file — summary, section context and descriptions together. For an exhaustive map what matters instead is that the list is grouped so a model can skip whole branches.

  Where: The descriptions and section context in llms.txt

  1. Count the words in your file against the number of links — aim for 30 or more per link.
  2. A list of page names is an index, not documentation; the descriptions are what a model actually reads.
  3. Add a line of context under each "## " heading saying what that group covers.
• List items are markdown links Content & links +1

  Right now: 5 of 33 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 44

  - Dt. Songül Mirzaoğlu, Ankara Üniversitesi Diş Hekimliği Fakültesi mezunu, İtalya'daki University of Studies Guglielmo Marconi'de Estetik Diş Hekimliği yüksek lisansı yapmıştır. New York, Fransa, İtalya ve Portekiz'de implantoloji ve ileri estetik diş hekimliği eğitimleri almıştır.

  - [Dt. Songül Mirzaoğlu, Ankara Üniversitesi Diş Hekimliği Fakültesi mezunu, İtalya'daki University of Studies Guglielmo Marconi'de Estetik Diş Hekimliği yüksek lisansı yapmıştır. New York, Fransa, İtalya ve Portekiz'de implantoloji ve ileri estetik diş hekimliği eğitimleri almıştır.]({https://your-site/path}.md): {what this page covers}

  line 45

  - Kişisel web sitesi: [songulmirzaoglu.com](https://songulmirzaoglu.com/)

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

  line 54

  - Adres: Ümitköy, Osmanağa Konakları, 2494/4. Sk. No:7, 06810 Çankaya/Ankara, Türkiye

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

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

• Summary is a usable length Structure +1

  Right now: 434 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.
• 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 18 September 2026; run it again for the current state, or check a different site.