www.uzmanhurdaci.com — llms.txt & GEO score

Uzman Hurdacı - Metal Geri Dönüşüm ve Yerinde Hurda Alımı

Uzman Hurdacı, Ankara Sincan, Yenikent, Etimesgut, Ostim, İvedik ve tüm Ankara genelinde demir, bakır, alüminyum, kablo, paslanmaz ve sanayi artık hurdaları için yerinde inceleme, şeffaf elektronik kantar tartımı ve planlı nakliye ile yerinde hurda alımı ve geri dönüşüm hizmetleri sunmaktadır.

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

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

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

• Exactly one H1 project title “Uzman Hurdacı - Metal Geri Dönüşüm ve Yerinde Hurda Alımı”
  3/3
• Summary directly under the title Present as a blockquote
  3/3
• Summary is a usable length 294 characters
  3/3
• Concrete language, not marketing filler No marketing filler detected
  3/3
• Grouped into balanced sections 4 H2 sections, largest group holds 9 of 19 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 4 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 254 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 50 characters, from title
  2/2
• Title is not padded or repetitive No repeated terms
  1/1
• Homepage has a meta description 158 characters, from meta description
  2/2
• Canonical URL declared https://www.uzmanhurdaci.com/
  1/1
• Language declared lang="tr-TR"
  1/1
• Social card image og:image is set
  1/1

4 of 5 checks pass. What is left: the index points at the full file.

• Publishes llms-full.txt Companion full-text file found
  3/3
• The index points at the full file Not linked from llms.txt
  0/1
• Index is a sensible size 4.6 KB
  2/2
• Server reports when it last changed Server sends Last-Modified
  1/1
• The index is kept current Last changed 1 day ago
  2/2

• Points at clean markdown copies Content & links +10

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

  - [Hakkımızda](https://www.uzmanhurdaci.com/hakkimizda/): Kurumsal geçmişimiz, çalışma ilkelerimiz, kantar ve nakliye altyapımız.

  - [Hakkımızda](https://www.uzmanhurdaci.com/hakkimizda.md): Kurumsal geçmişimiz, çalışma ilkelerimiz, kantar ve nakliye altyapımız.

  line 11

  - [Hizmetlerimiz](https://www.uzmanhurdaci.com/hizmetler/): Hurda metal alımı, demir, bakır, alüminyum, kablo, paslanmaz ve fabrika söküm hizmetleri.

  - [Hizmetlerimiz](https://www.uzmanhurdaci.com/hizmetler.md): Hurda metal alımı, demir, bakır, alüminyum, kablo, paslanmaz ve fabrika söküm hizmetleri.

  line 12

  - [Hurda Fiyatları](https://www.uzmanhurdaci.com/hurda-fiyatlari/): LME ve serbest piyasa endeksli canlı borsa kurları, şeffaf elektronik kantar tartımı ve fiyatlandırma esasları.

  - [Hurda Fiyatları](https://www.uzmanhurdaci.com/hurda-fiyatlari.md): LME ve serbest piyasa endeksli canlı borsa kurları, şeffaf elektronik kantar tartımı ve fiyatlandırma esasları.

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

• 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

• Enough written detail per link Content & links +1

  Right now: 25 words per link across 466 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.
• Grouped into balanced sections Structure +1

  Right now: 4 H2 sections, largest group holds 9 of 19 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 +1

  Right now: 1 weak title (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 15

  - [Blog](https://www.uzmanhurdaci.com/blog/): Hurda metal türleri, geri dönüşüm sektörü ve malzeme sınıflandırma rehberleri.

  - [{the page’s real name}](https://www.uzmanhurdaci.com/blog/): Hurda metal türleri, geri dönüşüm sektörü ve malzeme sınıflandırma rehberleri.

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

• List items are markdown links Content & links +1

  Right now: 4 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 37

  - **Saha Sorumlusu:** Menderes Usta (20+ yıllık metalurji ve hurda saha uzmanı)

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

  line 38

  - **Telefon & WhatsApp:** 0536 734 89 95

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

  line 39

  - **İşletme Merkezi:** Yenikent Sanayi Sitesi, 17. Cadde No:14 Sincan / Ankara

  - [**İşletme Merkezi]({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: Not linked from llms.txt

  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.