# Can agents read cornelraiu.com?

**90/100, Yes.** Agents can read cornelraiu.com. The fixes below are ranked by the points they win back.

Scanned 2 Nov 2026, 18:49 UTC · 8 pages · scoring v1 · [Full report](https://canagentsread.com/cornelraiu.com)

| Tier | Points | Checks |
|---|---|---|
| Getting in | 75 / 75 | 5 passed |
| Making sense | 8.9 / 15 | 5 passed · 3 partial · 2 failed · 1 doesn't apply |
| Extras | 6.1 / 10 | 11 passed · 1 partial · 7 failed · 6 doesn't apply |

## Biggest wins first

1. **Serve Markdown when it's asked for** (+3.3 points): Asking the homepage for text/markdown still returns text/html.
2. **Link About, Contact and Privacy** (+1.1 points): Found: About. Missing: Contact (not linked from the homepage), Privacy (not linked from the homepage).
3. **Describe the site in schema.org** (+0.8 points): The homepage has JSON-LD, but no Organization or WebSite with both a name and a url.
4. **Say who runs the site** (+0.6 points): No Organization schema on the pages we read.
5. **Say in llms.txt when to use the site** (+0.5 points): llms.txt doesn't say when an agent should point people to this site.
6. **Publish .md copies of pages** (+0.5 points): No /index.md, and 0 of 3 pages we tried have a .md copy.
7. **Link to the Markdown version** (+0.5 points): The homepage has no <link rel="alternate" type="text/markdown">.
8. **Serve Markdown to AI user agents** (+0.5 points): AI agents that don't ask for Markdown get HTML.
9. **Point to agent files in a Link header** (+0.5 points): The homepage response has no Link header.
10. **Add lastmod dates to the sitemap** (+0.5 points): 0 of 12 sitemap entries have a <lastmod> date.
11. **Add a Content-Signal line to robots.txt** (+0.5 points): robots.txt has no Content-Signal line.
12. **Fill in the page basics** (+0.3 points): 5 of 6 basics filled in. Missing: og:image.
13. **Name AI agents in robots.txt** (+0.3 points): 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.

A prompt for a coding agent with the five biggest fixes is at https://canagentsread.com/cornelraiu.com/fix-prompt.md.

## Getting in (75 of 75 points)

### AI agents are let in

Passed · 21 / 21 points · `agent_access`

All 4 AI agents get the page: ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot.

### Words are in the HTML

Passed · 21 / 21 points · `no_js_content`

3,383 characters of text in the server HTML, 1 H1 and 4 H2s.

### Pages are public, with real text

Passed · 13 / 13 points · `public_content`

All 8 pages we read are public and have real content.

### Redirects don't detour

Passed · 11 / 11 points · `clean_redirects`

No meta-refresh stubs, JavaScript redirects or cross-domain hops across 8 pages.

### Dead links say so

Passed · 9 / 9 points · `agent_404`

A missing page returns HTTP 404 with links back into the site.

## Making sense (8.9 of 15 points)

### Speaks Markdown when asked

Failed · 0 / 3.3 points · `md_negotiation`

Asking the homepage for text/markdown still returns text/html.

**How to 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.

### Says who runs it

Failed · 0 / 0.6 points · `org_schema`

No Organization schema on the pages we read.

**How to fix:** 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": "hello@example.com"},
  "address": {"@type": "PostalAddress", "addressLocality": "City", "addressCountry": "RO"}
}
```

### Describes itself in schema.org

Partial · 0.8 / 1.7 points · `json_ld`

The homepage has JSON-LD, but no Organization or WebSite with both a name and a url.

**How to fix:** 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.

### Page basics filled in

Partial · 1.4 / 1.7 points · `metadata`

5 of 6 basics filled in. Missing: og:image.

**How to fix:** Add these to the homepage:

```html
<meta property="og:image" content="https://example.com/share.png">
```

### About, Contact, Privacy linked

Partial · 0.6 / 1.7 points · `trust_pages`

Found: About. Missing: Contact (not linked from the homepage), Privacy (not linked from the homepage).

**How to 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.

### Visible to search

Passed · 1.7 / 1.7 points · `indexable`

The homepage lets search engines index it.

### Has a map of its pages

Passed · 1.7 / 1.7 points · `sitemap`

The sitemap lists 12 pages; 5 of the 5 we opened load.

### Each page names one address

Passed · 0.6 / 0.6 points · `canonical`

All 8 canonicals we found name their own page.

### Images are described

Passed · 0.6 / 0.6 points · `image_alt`

All 6 images we found have alt text.

### Pages fit in one read

Passed · 1.7 / 1.7 points · `token_budget`

Every page we read fits in one read; the largest is about 4,381 tokens.

### Prices are findable

Doesn't apply · not scored · `pricing_page`

We found nothing for sale: no pricing page, shop links or Product schema.

## Extras (6.1 of 10 points)

### Says when to use it

Failed · 0 / 0.5 points · `llms_guidance`

llms.txt doesn't say when an agent should point people to this site.

**How to fix:** 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
```

### .md copies of pages

Failed · 0 / 0.5 points · `md_twins`

No /index.md, and 0 of 3 pages we tried have a .md copy.

**How to fix:** 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

Failed · 0 / 0.5 points · `md_alternate`

The homepage has no <link rel="alternate" type="text/markdown">.

**How to fix:** Add a link to the page's Markdown version in its `<head>`, and make sure the address returns `text/markdown`:

```html
<link rel="alternate" type="text/markdown" href="/index.md">
```

### Gives AI agents Markdown without being asked

Failed · 0 / 0.5 points · `bot_markdown`

AI agents that don't ask for Markdown get HTML.

**How to fix:** 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

Failed · 0 / 0.5 points · `link_headers`

The homepage response has no Link header.

**How to fix:** Add a `Link` header to the homepage response that points agents to your agent files:

```http
Link: </llms.txt>; rel="describedby", </index.md>; rel="alternate"; type="text/markdown"
```

### Sitemap says what changed

Failed · 0 / 0.5 points · `sitemap_fresh`

0 of 12 sitemap entries have a <lastmod> date.

**How to fix:** 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

Failed · 0 / 0.5 points · `content_signals`

robots.txt has no Content-Signal line.

**How to fix:** 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.

### Clear rules for AI bots

Partial · 0.3 / 0.5 points · `robots_ai_policy`

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.

**How to fix:** 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.

### Leaves an llms.txt

Passed · 0.5 / 0.5 points · `llms_txt`

There is an llms.txt at /llms.txt (1,437 characters).

### llms.txt reads like a contents page

Passed · 0.5 / 0.5 points · `llms_format`

llms.txt has a # heading, links to pages and fits in one read.

### llms.txt links work

Passed · 0.5 / 0.5 points · `llms_links`

All 5 llms.txt links we opened load.

### Links to its other profiles

Passed · 0.5 / 0.5 points · `same_as`

The schema lists 3 profiles in sameAs.

### Clear page outline

Passed · 0.5 / 0.5 points · `doc_structure`

The homepage has main, header, nav and footer landmarks, one H1 and no skipped heading levels.

### Real buttons and links

Passed · 0.5 / 0.5 points · `native_controls`

All 253 controls in the server HTML are real buttons, links and fields.

### Buttons say what they do

Passed · 0.5 / 0.5 points · `control_names`

All 252 buttons and links have a name.

### No hidden instructions

Passed · 0.5 / 0.5 points · `no_hidden_prompts`

No instructions for AI agents hidden in the 8 pages we read.

### Says when pages were updated

Passed · 0.5 / 0.5 points · `dates`

7 of 8 pages we read show a publish or update date.

### Answers quickly

Passed · 0.5 / 0.5 points · `speed`

The homepage answered in a middle time of 77 ms across 5 fetches.

### Has an update feed

Passed · 0.5 / 0.5 points · `feed`

The feed at https://cornelraiu.com/rss.xml has 5 entries.

### Every field has a label

Doesn't apply · not scored · `form_labels`

No form fields on the pages we read.

### Can be searched by URL

Doesn't apply · not scored · `site_search`

The homepage has no search box.

### Lists its APIs

Doesn't apply · not scored · `api_catalog`

No API catalog at /.well-known/api-catalog.

### Publishes an agent card

Doesn't apply · not scored · `agent_card`

No agent card at /.well-known/agent-card.json or /.well-known/agent.json.

### Products are described

Doesn't apply · not scored · `product_data`

We found no sign the site sells products: no shop or cart links and no Product schema.

### Shipping and returns are findable

Doesn't apply · not scored · `shop_policies`

The site doesn't sell on its own pages: no cart or checkout links, and no offers of its own.

---

Scanned by [canagentsread](https://canagentsread.com), which checks whether AI agents can read a website. Scores read: 85–100 Yes, 65–84 Mostly, 40–64 Partly, 0–39 No.