Can agents read cornelraiu.com?
Agents can read cornelraiu.com. The fixes below are ranked by the points they win back.
The top 5 fixes get cornelraiu.com to 96, Yes
Ranked by the points they win back. 13 fixes in all, worth 10.1 points. Tick the fixes you want, then copy them as one prompt for Claude Code, Cursor or Codex.
-
1
Serve Markdown when it's asked for Asking the homepage for text/markdown still returns text/html.+3.3 points
Show the changeHide the change
When a request's
Acceptheader asks fortext/markdown, answer with a Markdown version of the page: sendContent-Type: text/markdownand start with the page title as a#heading. AddVary: Acceptso caches keep the HTML and Markdown versions apart. -
2
Link About, Contact and Privacy Found: About. Missing: Contact (not linked from the homepage), Privacy (not linked from the homepage).+1.1 points
Show the changeHide the change
Link to your About, Contact and Privacy pages from every page, usually in the footer, and make sure each one loads without signing in.
-
3
Describe the site in schema.org The homepage has JSON-LD, but no Organization or WebSite with both a name and a url.+0.8 points
Show the changeHide the change
Add a JSON-LD block to the homepage
<head>that names the site:<script type="application/ld+json"> {"@context": "https://schema.org", "@type": "Organization", "name": "Your company", "url": "https://example.com"} </script>Check that every JSON-LD block parses as valid JSON.
-
4
Say who runs the site No Organization schema on the pages we read.+0.6 points
Show the changeHide the change
Describe your company in Organization JSON-LD on the homepage, with all six fields:
{ "@context": "https://schema.org", "@type": "Organization", "name": "Your company", "url": "https://example.com", "logo": "https://example.com/logo.png", "sameAs": ["https://www.linkedin.com/company/your-company"], "contactPoint": {"@type": "ContactPoint", "contactType": "customer support", "email": "[email protected]"}, "address": {"@type": "PostalAddress", "addressLocality": "City", "addressCountry": "RO"} } -
5
Say in llms.txt when to use the site llms.txt doesn't say when an agent should point people to this site.+0.5 points
Show the changeHide the change
Add a section to llms.txt that tells agents when to point people to you, and when not to:
## When to use this site - Comparing prices for X - Not for: Y
8 smaller fixes, worth 3.7 points together
-
6
Publish .md copies of pages No /index.md, and 0 of 3 pages we tried have a .md copy.+0.5 points
Show the changeHide the change
Serve a Markdown copy of each page at its address plus
.md(/pricing→/pricing.md,/docs/→/docs/index.md), and of the homepage at/index.md, sent astext/markdown. -
7
Link to the Markdown version The homepage has no <link rel="alternate" type="text/markdown">.+0.5 points
Show the changeHide the change
Add a link to the page's Markdown version in its
<head>, and make sure the address returnstext/markdown:<link rel="alternate" type="text/markdown" href="/index.md"> -
8
Serve Markdown to AI user agents AI agents that don't ask for Markdown get HTML.+0.5 points
Show the changeHide the change
Serve the Markdown version of a page to known AI user agents (ChatGPT-User, Claude-User, PerplexityBot and the like) even when they send
Accept: */*. Match the user agent in your server or CDN, returntext/markdown, and sendVary: User-Agent. -
9
Point to agent files in a Link header The homepage response has no Link header.+0.5 points
Show the changeHide the change
Add a
Linkheader to the homepage response that points agents to your agent files:Link: </llms.txt>; rel="describedby", </index.md>; rel="alternate"; type="text/markdown" -
10
Add lastmod dates to the sitemap 0 of 12 sitemap entries have a <lastmod> date.+0.5 points
Show the changeHide the change
Give every sitemap
<url>a<lastmod>with the date the page last really changed, in W3C format (2026-10-25), and update it only when the content changes. -
11
Add a Content-Signal line to robots.txt robots.txt has no Content-Signal line.+0.5 points
Show the changeHide the change
Add a Content-Signal line to robots.txt saying how your content may be used. For example, to allow search and live AI answers but not training:
User-agent: * Content-Signal: search=yes, ai-input=yes, ai-train=no Allow: /The choice is yours: any setting earns the points.
-
12
Fill in the page basics 5 of 6 basics filled in. Missing: og:image.+0.3 points
Show the changeHide the change
Add these to the homepage:
<meta property="og:image" content="https://example.com/share.png"> -
13
Name AI agents in robots.txt robots.txt lets AI agents in, but only through User-agent: *. It doesn't name OAI-SearchBot, Claude-SearchBot, PerplexityBot, ChatGPT-User, Claude-User, Perplexity-User.+0.3 points
Show the changeHide the change
Name the AI agents that fetch pages to answer people, and let them in, in robots.txt:
User-agent: OAI-SearchBot User-agent: Claude-SearchBot User-agent: PerplexityBot User-agent: ChatGPT-User User-agent: Claude-User User-agent: Perplexity-User Allow: /You can still block training crawlers like GPTBot, ClaudeBot or CCBot; that doesn't cost points.
# Make cornelraiu.com readable by AI agents
canagentsread.com scanned cornelraiu.com on 2 Nov 2026: 90/100, Yes.
Make these 5 changes, then rescan https://canagentsread.com/cornelraiu.com to confirm.
## 1. Serve Markdown when it's asked for (+3.3 points)
Found: Asking the homepage for text/markdown still returns text/html.
Change: When a request's `Accept` header asks for `text/markdown`, answer with a Markdown version of the page: send `Content-Type: text/markdown` and start with the page title as a `#` heading. Add `Vary: Accept` so caches keep the HTML and Markdown versions apart.
## 2. Link About, Contact and Privacy (+1.1 points)
Found: Found: About. Missing: Contact (not linked from the homepage), Privacy (not linked from the homepage).
Change: Link to your About, Contact and Privacy pages from every page, usually in the footer, and make sure each one loads without signing in.
## 3. Describe the site in schema.org (+0.8 points)
Found: The homepage has JSON-LD, but no Organization or WebSite with both a name and a url.
Change: Add a JSON-LD block to the homepage `<head>` that names the site:
```html
<script type="application/ld+json">
{"@context": "https://schema.org", "@type": "Organization", "name": "Your company", "url": "https://example.com"}
</script>
```
Check that every JSON-LD block parses as valid JSON.
## 4. Say who runs the site (+0.6 points)
Found: No Organization schema on the pages we read.
Change: Describe your company in Organization JSON-LD on the homepage, with all six fields:
```json
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your company",
"url": "https://example.com",
"logo": "https://example.com/logo.png",
"sameAs": ["https://www.linkedin.com/company/your-company"],
"contactPoint": {"@type": "ContactPoint", "contactType": "customer support", "email": "[email protected]"},
"address": {"@type": "PostalAddress", "addressLocality": "City", "addressCountry": "RO"}
}
```
## 5. Say in llms.txt when to use the site (+0.5 points)
Found: llms.txt doesn't say when an agent should point people to this site.
Change: Add a section to llms.txt that tells agents when to point people to you, and when not to:
```markdown
## When to use this site
- Comparing prices for X
- Not for: Y
```
What agents saw on cornelraiu.com
Getting in
75 of 75 points · 5 passedMaking sense
8.9 of 15 points · 5 passed · 3 partial · 2 failed · 1 doesn't applyShow the fixHide the fix
When a request's Accept header asks for text/markdown, answer with a Markdown version of the page: send Content-Type: text/markdown and start with the page title as a # heading. Add Vary: Accept so caches keep the HTML and Markdown versions apart.
Show the fixHide the fix
Describe your company in Organization JSON-LD on the homepage, with all six fields:
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your company",
"url": "https://example.com",
"logo": "https://example.com/logo.png",
"sameAs": ["https://www.linkedin.com/company/your-company"],
"contactPoint": {"@type": "ContactPoint", "contactType": "customer support", "email": "[email protected]"},
"address": {"@type": "PostalAddress", "addressLocality": "City", "addressCountry": "RO"}
}
Show the fixHide the fix
Add a JSON-LD block to the homepage <head> that names the site:
<script type="application/ld+json">
{"@context": "https://schema.org", "@type": "Organization", "name": "Your company", "url": "https://example.com"}
</script>
Check that every JSON-LD block parses as valid JSON.
Show the fixHide the fix
Add these to the homepage:
<meta property="og:image" content="https://example.com/share.png">
Show the fixHide the fix
Link to your About, Contact and Privacy pages from every page, usually in the footer, and make sure each one loads without signing in.
Extras
6.1 of 10 points · 11 passed · 1 partial · 7 failed · 6 doesn't applySays when to use it Show the fixHide the fix
llms.txt doesn't say when an agent should point people to this site.
Add a section to llms.txt that tells agents when to point people to you, and when not to:
## When to use this site
- Comparing prices for X
- Not for: Y
How we check this.md copies of pages Show the fixHide the fix
No /index.md, and 0 of 3 pages we tried have a .md copy.
Serve a Markdown copy of each page at its address plus .md (/pricing → /pricing.md, /docs/ → /docs/index.md), and of the homepage at /index.md, sent as text/markdown.
Points to its Markdown Show the fixHide the fix
The homepage has no <link rel="alternate" type="text/markdown">.
Add a link to the page's Markdown version in its <head>, and make sure the address returns text/markdown:
<link rel="alternate" type="text/markdown" href="/index.md">
How we check thisGives AI agents Markdown without being asked Show the fixHide the fix
AI agents that don't ask for Markdown get HTML.
Serve the Markdown version of a page to known AI user agents (ChatGPT-User, Claude-User, PerplexityBot and the like) even when they send Accept: */*. Match the user agent in your server or CDN, return text/markdown, and send Vary: User-Agent.
Points to agent files in HTTP headers Show the fixHide the fix
The homepage response has no Link header.
Add a Link header to the homepage response that points agents to your agent files:
Link: </llms.txt>; rel="describedby", </index.md>; rel="alternate"; type="text/markdown"
How we check thisSitemap says what changed Show the fixHide the fix
0 of 12 sitemap entries have a <lastmod> date.
Give every sitemap <url> a <lastmod> with the date the page last really changed, in W3C format (2026-10-25), and update it only when the content changes.
States its AI preferences Show the fixHide the fix
robots.txt has no Content-Signal line.
Add a Content-Signal line to robots.txt saying how your content may be used. For example, to allow search and live AI answers but not training:
User-agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=no
Allow: /
The choice is yours: any setting earns the points.
How we check thisClear rules for AI bots Show the fixHide the fix
robots.txt lets AI agents in, but only through User-agent: *. It doesn't name OAI-SearchBot, Claude-SearchBot, PerplexityBot, ChatGPT-User, Claude-User, Perplexity-User.
Name the AI agents that fetch pages to answer people, and let them in, in robots.txt:
User-agent: OAI-SearchBot
User-agent: Claude-SearchBot
User-agent: PerplexityBot
User-agent: ChatGPT-User
User-agent: Claude-User
User-agent: Perplexity-User
Allow: /
You can still block training crawlers like GPTBot, ClaudeBot or CCBot; that doesn't cost points.
How we check thisFound · 11: Leaves an llms.txt, llms.txt reads like a contents page, llms.txt links work, Links to its other profiles, Clear page outline, Real buttons and links, Buttons say what they do, , Says when pages were updated, Answers quickly, Has an update feed
Doesn't apply or couldn't check · 6: Every field has a label, Can be searched by URL, Lists its APIs, Publishes an agent card, Products are described, Shipping and returns are findable
Can agents read your site?
Paste a URL and you'll get a report like this one.