check-tin.asif.dev — F/100 agent-readiness

01Fail
robots.txt present & sane
+6 pts if fixed
Serve a non-blocking /robots.txt that references your Sitemap.
See full details
02Fail
/llms.txt
+6 pts if fixed
Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
See full details
03Fail
Explicit AI bot rules
+5 pts if fixed
Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
See full details

Hand-off prompt for your coding agent8 issues

You are helping me raise my AIScan.site agent-readiness score.

Site: https://check-tin.asif.dev/
Platform: lovable (50% confidence)
AIScan score: 18/100 — Level 1 (Discoverable)
Rubric: v2026-06-08.1

Please implement the fixes below. Where a file already exists (e.g. `public/robots.txt`, `public/llms.txt`), edit it; otherwise create it. After each change, briefly explain what you did so I can verify in the next scan.

### Failing checks
- **[D1] robots.txt present & sane** — FAIL
  - Evidence: HTTP 404
  - Fix: Serve a non-blocking /robots.txt that references your Sitemap.
- **[C2] /llms.txt** — FAIL
  - Evidence: HTTP 404
  - Fix: Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
- **[B2] Explicit AI bot rules** — FAIL
  - Evidence: 0 known AI agent(s) addressed in robots.txt
  - Fix: Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
- **[D2] XML sitemap** — FAIL
  - Evidence: no /sitemap.xml or /sitemap_index.xml resolved
  - Fix: Publish /sitemap.xml and reference it in robots.txt.
- **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL
  - Evidence: h1: 1, title: true, meta description: true, JSON-LD: false
  - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.
- **[P1] API Catalog (RFC 9727)** — FAIL
  - Evidence: 404 at /.well-known/api-catalog
  - Fix: Publish /.well-known/api-catalog linking to your OpenAPI descriptions.
- **[P4] OAuth discovery metadata** — FAIL
  - Evidence: auth-server: 404, protected-resource: 404
  - Fix: Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
- **[D3] Link header for discovery** — FAIL
  - Evidence: no Link response header
  - Fix: Add a Link header with rel="api-catalog" or rel="describedby".

### Constraints
- Do not change visible UI or copy.
- Keep changes additive and reversible.
- Prefer static files in `public/` over server routes when possible.
- For `llms.txt`, generate a real index of the site's most important pages.

Discoverability

Can agents find your pages? robots, sitemaps, llms.txt.

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · D1
What we found
HTTP 404
How to fix it
Serve a non-blocking /robots.txt that references your Sitemap.
1.⚡ Fix automatically with AIScan
The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.
2.This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like `robots.txt`, `llms.txt`, and `.well-known/*` belong in the `public/` folder — they're served from the site root automatically.
3.Create /robots.txt
Place this file at the site root so it's served at `https://yoursite.com/robots.txt`.
4.Recommended contents
User-agent: * Allow: / Sitemap: https://example.com/sitemap.xml # Content Signals (Cloudflare proposal) Content-Signal: search=yes, ai-train=no, ai-input=yes # Explicit AI agent rules User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: / User-agent: Applebot-Extended Allow: /
5.Verify
After deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.
Fix in ChatGPT Fix in Claude
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · D2
What we found
no /sitemap.xml or /sitemap_index.xml resolved
How to fix it
Publish /sitemap.xml and reference it in robots.txt.
1.⚡ Fix automatically with AIScan
The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.
2.This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like `robots.txt`, `llms.txt`, and `.well-known/*` belong in the `public/` folder — they're served from the site root automatically.
3.Generate a sitemap
Most frameworks have a built-in sitemap generator (Next.js: `app/sitemap.ts`, TanStack: a route at `/sitemap.xml`). Publish all public URLs.
4.Reference it in robots.txt
Sitemap: https://yoursite.com/sitemap.xml
5.Verify
After deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.
Fix in ChatGPT Fix in Claude
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · D3
What we found
no Link response header
How to fix it
Add a Link header with rel="api-catalog" or rel="describedby".
1.⚡ Fix automatically with AIScan
The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.
2.This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like `robots.txt`, `llms.txt`, and `.well-known/*` belong in the `public/` folder — they're served from the site root automatically.
3.Add a Link response header
Set this header on your homepage and/or root document. Most CDNs (Cloudflare, Vercel, Netlify) support response-header rules.
4.Example
Link: </.well-known/api-catalog>; rel="api-catalog"
5.Verify
After deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.
Fix in ChatGPT Fix in Claude

Content

Can agents read your content cleanly? Markdown, structured data.

111

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · C2
What we found
HTTP 404
How to fix it
Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
1.⚡ Fix automatically with AIScan
The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.
2.This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like `robots.txt`, `llms.txt`, and `.well-known/*` belong in the `public/` folder — they're served from the site root automatically.
3.Create /llms.txt at the site root
Follows the llmstxt.org spec: a single H1, optional blockquote summary, then `##` sections of markdown links.
4.Template
# Example Co > One-line summary of what this site / product does. A short paragraph explaining the audience, what's here, and how to navigate it. ## Docs - [Getting started](/docs/quickstart): install, first call in 5 min - [API reference](/docs/api): all endpoints, params, examples ## Pages - [Pricing](/pricing): plans and limits - [Changelog](/changelog): recent releases ## Optional - [Brand assets](/press): logos and screenshots
5.Verify
After deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.
Fix in ChatGPT Fix in Claude

Bot Access

Are AI crawlers explicitly allowed or blocked?

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · B2
What we found
0 known AI agent(s) addressed in robots.txt
How to fix it
Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
1.⚡ Fix automatically with AIScan
The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.
2.This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like `robots.txt`, `llms.txt`, and `.well-known/*` belong in the `public/` folder — they're served from the site root automatically.
3.Add explicit User-agent blocks
Don't rely on `User-agent: *` alone. Address each major AI crawler so your policy is unambiguous.
4.Recommended block
User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: / User-agent: Applebot-Extended Allow: /
5.Verify
After deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.
Fix in ChatGPT Fix in Claude

Capabilities

Can agents do things? APIs, auth, MCP, Agent Skills.

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · P1
What we found
404 at /.well-known/api-catalog
How to fix it
Publish /.well-known/api-catalog linking to your OpenAPI descriptions.
1.⚡ Fix automatically with AIScan
The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.
2.This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like `robots.txt`, `llms.txt`, and `.well-known/*` belong in the `public/` folder — they're served from the site root automatically.
3.Publish an API catalog (RFC 9727)
# Add to your homepage HTTP response headers Link: </.well-known/api-catalog>; rel="api-catalog" # And serve a JSON document at /.well-known/api-catalog: { "links": [ { "href": "/openapi.json", "rel": "service-desc", "type": "application/openapi+json" } ] }
4.Verify
After deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.
Fix in ChatGPT Fix in Claude
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · P4
What we found
auth-server: 404, protected-resource: 404
How to fix it
Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
1.⚡ Fix automatically with AIScan
The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.
2.This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like `robots.txt`, `llms.txt`, and `.well-known/*` belong in the `public/` folder — they're served from the site root automatically.
3.Publish OAuth discovery metadata
If your API supports OAuth, serve RFC 8414 metadata at `/.well-known/oauth-authorization-server` and/or RFC 9728 at `/.well-known/oauth-protected-resource`.
4.Verify
After deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.
Fix in ChatGPT Fix in Claude

Showcase your grade

Embed your AIScan badge

Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of check-tin.asif.dev on AIScan.site.

HTML

<!-- AIScan.site agent-readiness badge -->
<a href="https://aiscan.site/?u=https%3A%2F%2Fcheck-tin.asif.dev%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade F (18/100) — AIScan.site">
  <img src="https://aiscan.site/api/public/badge.svg?score=18&grade=F&host=check-tin.asif.dev" alt="AIScan.site Grade F — 18/100" width="240" height="64" loading="lazy" />
</a>

Markdown

[![AIScan.site Grade F — 18/100](https://aiscan.site/api/public/badge.svg?score=18&grade=F&host=check-tin.asif.dev)](https://aiscan.site/?u=https%3A%2F%2Fcheck-tin.asif.dev%2F)

Track this over time

Coming soon: save sites, schedule re-scans, get email when something material changes. Standards land weekly — your tracker shouldn't be one-shot.

Free · No signup · ~20 seconds

Scan your own site

Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.

Scan your site

Or browse the community feed to see what others have scanned.

Lovable

Quick Wins

robots.txt present & sane

/llms.txt

Explicit AI bot rules

Discoverability

robots.txt present & sane

XML sitemap

Link header for discovery

Content

Markdown content negotiation

/llms.txt

Structured HTML (title, meta, JSON-LD, single H1)

Bot Access

Content Signals in robots.txt

Explicit AI bot rules

Web Bot Auth key directory

Capabilities

API Catalog (RFC 9727)

MCP Server Card

Agent Skills index

OAuth discovery metadata

Embed your AIScan badge

Track this over time

Scan your own site

Lovable

Quick Wins

robots.txt present & sane

/llms.txt

Explicit AI bot rules

robots.txt present & sane

XML sitemap

Link header for discovery

Markdown content negotiation

/llms.txt

Structured HTML (title, meta, JSON-LD, single H1)

Content Signals in robots.txt

Explicit AI bot rules

Web Bot Auth key directory

API Catalog (RFC 9727)

MCP Server Card

Agent Skills index

OAuth discovery metadata

Share as a social image

Embed your AIScan badge

Track this over time

Scan your own site