oykuzeynepaydin.com — llms.txt & GEO score

Öykü Zeynep Aydın — Klinik Psikolog

Klinik Psikolog ve ISST Şema Terapisti Öykü Zeynep Aydın, İstanbul Kadıköy/Kozyatağı'ndaki ofisinde yüz yüze ve güvenli bir platform üzerinden online psikoterapi sunar. İstanbul Kültür Üniversitesi Psikoloji (2016, bölüm birincisi) ve Bremen Üniversitesi Klinik Psikoloji yüksek lisansı (2020) mezunudur. Şema Terapi, Bilişsel ve Davranışçı Terapi (BDT), Metakognitif Terapi ve Şefkat Odaklı Terapi ekollerinden faydalanarak genç ve yetişkinlerle bireysel terapi yürütür. Depresyon, kaygı, OKB, travma ve yas, özsaygı, ilişki ve bağlanma, duygu düzenleme, stres/tükenmişlik ile dikkat ve motivasyon güçlükleri en sık çalışılan alanlardır; her alanın kendi sayfası vardır. Site Türkçedir.

5 of 11 checks pass. What is left: enough links carry a description, descriptions say something concrete, a workable number of links, skippable links marked Optional, list items are markdown links and grouped so the map stays navigable.

• Enough links carry a description 4 of 75 described (5%) — for a map-shaped file the bar is 60%, not every line
  1/10
• Descriptions say something concrete Average 70 characters across 4 described links
  0/7
• Descriptions add to the title No description merely repeats its title
  4/4
• Points at clean markdown copies 66 of 75 end in .md or .txt (88%, detected by file extension)
  9/10
• Link titles are descriptive 1 weak title (bare URLs, “here”, one-word labels)
  4/4
• A workable number of links 75 links, nearly all pointing at machine-readable copies — an exhaustive map rather than a short guide, which is a legitimate shape for a documentation site
  3/4
• Skippable links marked Optional Nothing is marked as skippable
  0/3
• No duplicate links All 75 URLs are distinct
  2/2
• List items are markdown links 14 of 89 list items are plain text, not links
  3/4
• Grouped so the map stays navigable Median heading group holds 4 links across 15 groups (11 sub-headings)
  2/3
• Links are absolute URLs All 75 links are absolute URLs
  1/1

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

• Exactly one H1 project title “Öykü Zeynep Aydın — Klinik Psikolog”
  3/3
• Summary directly under the title Present as a blockquote
  3/3
• Summary is a usable length 687 characters — too long
  0/3
• Concrete language, not marketing filler No marketing filler detected
  3/3
• Grouped into balanced sections 6 H2 sections and 11 sub-headings, largest group holds 10 of 75 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 6 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 289 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

The homepage did not answer our request (HTTP 403), so these checks were not scored — a failed measurement is not a failing site.

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

• Enough links carry a description Content & links +9

  Right now: 4 of 75 described (5%) — for a map-shaped file the bar is 60%, not every line

  Add ": " and one short line after every link. An undescribed link is a coin flip — the model has to open it to find out what it is.

  Where: Each "- [Title](url)" line

  1. Add ": " and one short line after every link — not most of them, every one.
  2. Describe what the page answers, not what it is called.
  3. An undescribed link is a coin flip: the model has to open it to find out.

  In your file

  line 33

  - [Depresyon ve Duygudurum Sorunları](https://oykuzeynepaydin.com/calisma-alanlari/depresyon.md)

  - [Depresyon ve Duygudurum Sorunları](https://oykuzeynepaydin.com/calisma-alanlari/depresyon.md): {one line on what this page covers}

  line 34

  - [Kaygı (Anksiyete) Bozuklukları](https://oykuzeynepaydin.com/calisma-alanlari/kaygi.md)

  - [Kaygı (Anksiyete) Bozuklukları](https://oykuzeynepaydin.com/calisma-alanlari/kaygi.md): {one line on what this page covers}

  line 35

  - [Obsesif-Kompulsif ve İlişkili Bozukluklar](https://oykuzeynepaydin.com/calisma-alanlari/okb.md)

  - [Obsesif-Kompulsif ve İlişkili Bozukluklar](https://oykuzeynepaydin.com/calisma-alanlari/okb.md): {one line on what this page covers}

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

• Descriptions say something concrete Content & links +7

  Right now: Average 70 characters across 4 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 27

  - [Yazılar](https://oykuzeynepaydin.com/yazilar.md): 50 kısa yazı, konuya göre gruplu

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

  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: 687 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.
• A workable number of links Content & links +1

  Right now: 75 links, nearly all pointing at machine-readable copies — an exhaustive map rather than a short guide, which is a legitimate shape for a documentation site

  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.
• Grouped so the map stays navigable Content & links +1

  Right now: Median heading group holds 4 links across 15 groups (11 sub-headings)

  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: 14 of 89 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 7

  - Unvan: Klinik Psikolog & ISST Şema Terapisti (Klinik Psikoloji yüksek lisansı, Bremen Üniversitesi)

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

  line 8

  - Konum: Bayar Caddesi, Ağaoğlu Dizayn Canpolat Residence, Kat 7 Daire 15, Kozyatağı, 34742 Kadıköy/İstanbul

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

  line 9

  - Görüşme biçimi: Yüz yüze (Kozyatağı ofisi) ve online

  - [Görüşme biçimi]({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.