verce.com — llms.txt & GEO score

29 /100 F · 29 of 100 points

Links without directions

verce.com publishes an llms.txt, but it lists no links at all — so there is a title and little else for a model to follow.

The clearest gap is a workable number of links. Right now: No links at all. Closing it is worth 4 points.

Not yet an index — a model still has to guess from your HTML. Scanned 21 September 2026 against 34 checks — 11 passed, 0 partial, 23 missing.

verce.com GEO score card: 29 out of 100, with the score broken down across content, structure, discovery, search-engine basics and depth. — verce.com scored **29/100** on 21 September 2026. Source file: https://verce.com/llms.txt.

29/100geo score

0links

2sections

565 Bsize

What it does well

AI crawlers are not blocked No AI user-agent is disallowed at the root

What is missing

A workable number of links +4 No links at all
List items are markdown links +4 6 of 6 list items are plain text, not links
Grouped into balanced sections +3 2 H2 sections
Publishes llms-full.txt +3 No llms-full.txt alongside the index

Among the 22 sites measured here so far, verce.com ranks 22nd, against a median of 71. That comparison moves as new sites are scanned — it is a snapshot of this list, not of the web.

What verce.com tells an assistant

verce.com

verce.com is a domain name currently listed for sale on GoDaddy's aftermarket. It is available via Buy-It-Now, Make-an-Offer, or Lease-to-Own, depending on the listing's current configuration.

Content & links

Can a model pick the right page, first time?

0/52

Nothing in this group is in place yet.

Every link carries a description No links in the file, so there is nothing to describe
0/10
Descriptions say something concrete No links to measure
0/7
Descriptions add to the title No descriptions to compare against their titles
0/4
Points at clean markdown copies No links to point anywhere
0/10
Link titles are descriptive No link titles to judge
0/4
A workable number of links No links at all
0/4
Skippable links marked Optional Nothing is marked as skippable
0/3
No duplicate links No URLs to compare
0/2
List items are markdown links 6 of 6 list items are plain text, not links
0/4
Enough written detail per link No links to measure against
0/3
Links are absolute URLs No links to check
0/1

Structure

Does it follow the llms.txt shape?

17/20

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

Exactly one H1 project title “verce.com”
3/3
Summary directly under the title Present as a blockquote
3/3
Summary is a usable length 192 characters
3/3
Concrete language, not marketing filler No marketing filler detected
3/3
Grouped into balanced sections 2 H2 sections
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 2 headings are descriptive
2/2

Discovery & access

Can an assistant reach it, and is it allowed to?

10/11

4 of 5 checks pass. What is left: robots.txt points at a sitemap.

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 66 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 No Sitemap: line
0/1

Search-engine basics

What a crawler reads from your homepage today

0/8

Nothing in this group is in place yet.

Homepage title is the right length No title found
0/2
Title is not padded or repetitive No title to inspect
0/1
Homepage has a meta description No description meta tag
0/2
Canonical URL declared No rel="canonical" link
0/1
Language declared No lang attribute on <html>
0/1
Social card image No og:image — shares render as a bare link
0/1

Depth & upkeep

Is there more than the index, and is it current?

2/9

1 of 5 checks pass. What is left: publishes llms-full.txt, the index points at the full file, server reports when it last changed 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 565 B
2/2
Server reports when it last changed No Last-Modified header — clients cannot tell when this changed
0/1
The index is kept current Cannot be confirmed — the server sends no Last-Modified header
0/2

What verce.com should fix next

Ordered by what each one is worth. Open a row for the steps.

+30 pts

Right now: No links at all

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.
Right now: 6 of 6 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 6
- For sale: Yes

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

line 7
- Listed on: GoDaddy (aftermarket)

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

line 8
- Marketplace listing: https://forsale.godaddy.com/forsale/verce.com

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

Placeholders in { } are yours to write — we do not invent text about your pages.
Right now: 2 H2 sections

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](...)
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.
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
Right now: No description meta tag

Add a 70–160 character meta description. It is the snippet under your result, and assistants reuse it verbatim.

Where: The <meta name="description"> tag on your homepage
1. Target 70–160 characters; beyond that Google truncates it mid-sentence.
2. Write it as the sentence you would want quoted, because assistants reuse it verbatim.
Instead of
<meta name="description" content="Welcome to our website.">

Do this
<meta name="description" content="Industrial spare parts for food processing lines, shipped across Europe with same-week dispatch and two-year warranty.">
Right now: No title found

Write a 30–60 character title that names the product and what it does.

Where: The <title> tag on your homepage
1. Target 30–60 characters; past 60 the result gets cut off in search.
2. Put what you do before the brand name — the first words are what survives truncation.
Instead of
<title>Acme Parts | Acme | Industrial Spare Parts Supplier Europe Acme</title>

Do this
<title>Industrial spare parts for food lines — Acme</title>
Right now: Cannot be confirmed — the server sends no Last-Modified header

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.
Right now: No rel="canonical" link

Add <link rel="canonical"> so www and non-www are not counted as two competing sites.

Where: The <head> of every page
1. Add <link rel="canonical" href="..."> with the absolute, preferred URL.
2. Pick one host — www or non-www — and make every canonical point at it.
Do this
<link rel="canonical" href="https://acme.example/">
Right now: No lang attribute on <html>

Set <html lang="…">. It tells screen readers how to pronounce the page and models which language to expect.

Where: The <html> tag
1. Set lang to the page’s actual language: <html lang="tr"> or <html lang="en">.
2. It tells screen readers how to pronounce the page and models which language to expect.
Instead of
<html>

Do this
<html lang="tr">
Right now: No Last-Modified header — clients cannot tell when this changed

Let the server send Last-Modified on llms.txt. Without it a client has to re-download the whole file to notice a change.

Where: Your web server configuration
1. Serve llms.txt as a real file on disk so the server can derive Last-Modified from its mtime.
2. If it is generated by an application route, set the header yourself from the generation time.
3. Without it a client has to re-download the whole file to notice a change, and cannot answer "is this current?".
Instead of
HTTP/1.1 200 OK\nContent-Type: text/plain

Do this
HTTP/1.1 200 OK\nContent-Type: text/plain\nLast-Modified: Wed, 10 Sep 2026 08:14:00 GMT
Right now: No og:image — shares render as a bare link

Add an og:image. One tag, and it is the difference between a link and a card wherever you are shared.

Where: The <head> of your homepage
1. Add an og:image pointing at a 1200×630 PNG or JPG, with an absolute URL.
2. Add og:title and og:description alongside it so the card is not assembled from guesses.
3. Without it, every share of your link renders as bare text.
Do this
<meta property="og:image" content="https://acme.example/og.png"> <meta property="og:image:width" content="1200"> <meta property="og:image:height" content="630">
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
Right now: No title to inspect

Say the brand once. Use the freed characters to describe what the product does.

Where: The <title> tag on your homepage
1. Say the brand once. The repeated word this check found is spending visible characters for nothing.
2. Use the freed characters to describe what the product does.
Instead of
<title>Hurdacı — İstanbul Hurdacı | Hurdacı</title>

Do this
<title>Scrap metal collection in Istanbul — same-day payment</title>
Right now: No Sitemap: line

Add a Sitemap: line to robots.txt. llms.txt says what matters; the sitemap says what exists.

Where: /robots.txt
1. Add one Sitemap: line with the absolute URL of your sitemap.
2. llms.txt tells a model what matters; the sitemap tells a crawler what exists. They are not substitutes.
Do this
Sitemap: https://yourdomain.com/sitemap.xml

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.