Why we think this is Lovable (2 signals)
- · gpt-engineer marker (legacy Lovable)
- · 'lovable' string in JS bundle
4 failed · 1 partial out of 9 that apply to your site.
Quick Wins
Top 3 fixes ranked by score impact
- 01Fail+8 pts if fixed
Markdown content negotiation
See full detailsServe text/markdown when the client sends Accept: text/markdown, or publish /index.md.
- 02Fail+4 pts if fixed
API Catalog (RFC 9727)
See full detailsPublish /.well-known/api-catalog linking to your OpenAPI descriptions.
- 03Fail+4 pts if fixed
OAuth discovery metadata
See full detailsPublish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
You are helping me raise my AIScan.site agent-readiness score. Site: https://aihrbd.com/ Platform: lovable (99% confidence) AIScan score: 48/100 — Level 2 (Readable) 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 - **[C1] Markdown content negotiation** — FAIL - Evidence: no response - Fix: Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md. - **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL - Evidence: h1: 0, title: true, meta description: true, JSON-LD: true - 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 header or <link> tag - Fix: Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag. ### 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
77Can 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 · D3
What we foundno Link header or <link> tag
How to fix itAdd a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.
⚡ Fix automatically with AIScan
Option A — Agent Skill (any agent runtime)
Install the AIScan skill in one command:
```
npx add-skill https://aiscan.site/aiscan-skill.json
```
Or download it directly: https://aiscan.site/aiscan-skill.json
Then ask your agent: "Fix the failing AI readiness checks for <your-url>"Option B — Claude Code skill (CLAUDE.md)
- Download
CLAUDE.mdfrom https://aiscan.site/CLAUDE.md and place it in your project root. - Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.
Option C — MCP (Claude Desktop, Cursor, or any MCP client)
- Endpoint:
https://aiscan.site/api/mcp - Tools:
scan_website,get_fixes,get_grade - Call
get_fixeswith your URL for machine-readable fix instructions.
Option D — REST API
```
GET https://aiscan.site/api/public/scan?url=YOUR_URL
```
Returns the full report with all checks and fix details.Re-scan at https://aiscan.site to verify after applying fixes.
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 thepublic/folder — they're served from the site root automatically.Add a Link response header
Set this header on your homepage and/or root document. Most CDNs (Cloudflare, Vercel, Netlify) support response-header rules.
Example
Link: </.well-known/api-catalog>; rel="api-catalog"
Verify
After deploying, re-scan at https://aiscan.site. You can also test with
curl -Iorcurldirectly.- Download
Content
50Can agents read your content cleanly? Markdown, structured data.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · C1
What we foundno response
How to fix itServe text/markdown when the client sends Accept: text/markdown, or publish /index.md.
⚡ Fix automatically with AIScan
Option A — Agent Skill (any agent runtime)
Install the AIScan skill in one command:
```
npx add-skill https://aiscan.site/aiscan-skill.json
```
Or download it directly: https://aiscan.site/aiscan-skill.json
Then ask your agent: "Fix the failing AI readiness checks for <your-url>"Option B — Claude Code skill (CLAUDE.md)
- Download
CLAUDE.mdfrom https://aiscan.site/CLAUDE.md and place it in your project root. - Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.
Option C — MCP (Claude Desktop, Cursor, or any MCP client)
- Endpoint:
https://aiscan.site/api/mcp - Tools:
scan_website,get_fixes,get_grade - Call
get_fixeswith your URL for machine-readable fix instructions.
Option D — REST API
```
GET https://aiscan.site/api/public/scan?url=YOUR_URL
```
Returns the full report with all checks and fix details.Re-scan at https://aiscan.site to verify after applying fixes.
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 thepublic/folder — they're served from the site root automatically.Serve text/markdown on Accept negotiation
When a client sends
Accept: text/markdown, return a markdown rendering of the same content. The simplest path is to publish parallel.mdfiles (e.g./about→/about.md) and rewrite based on the Accept header.Test it
curl -H "Accept: text/markdown" https://yoursite.com/
Verify
After deploying, re-scan at https://aiscan.site. You can also test with
curl -Iorcurldirectly.- Download
Bot Access
100Are AI crawlers explicitly allowed or blocked?
Capabilities
0Can 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 found404 at /.well-known/api-catalog
How to fix itPublish /.well-known/api-catalog linking to your OpenAPI descriptions.
⚡ Fix automatically with AIScan
Option A — Agent Skill (any agent runtime)
Install the AIScan skill in one command:
```
npx add-skill https://aiscan.site/aiscan-skill.json
```
Or download it directly: https://aiscan.site/aiscan-skill.json
Then ask your agent: "Fix the failing AI readiness checks for <your-url>"Option B — Claude Code skill (CLAUDE.md)
- Download
CLAUDE.mdfrom https://aiscan.site/CLAUDE.md and place it in your project root. - Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.
Option C — MCP (Claude Desktop, Cursor, or any MCP client)
- Endpoint:
https://aiscan.site/api/mcp - Tools:
scan_website,get_fixes,get_grade - Call
get_fixeswith your URL for machine-readable fix instructions.
Option D — REST API
```
GET https://aiscan.site/api/public/scan?url=YOUR_URL
```
Returns the full report with all checks and fix details.Re-scan at https://aiscan.site to verify after applying fixes.
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 thepublic/folder — they're served from the site root automatically.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" } ] }Verify
After deploying, re-scan at https://aiscan.site. You can also test with
curl -Iorcurldirectly.- Download
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 foundauth-server: 404, protected-resource: 404
How to fix itPublish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
⚡ Fix automatically with AIScan
Option A — Agent Skill (any agent runtime)
Install the AIScan skill in one command:
```
npx add-skill https://aiscan.site/aiscan-skill.json
```
Or download it directly: https://aiscan.site/aiscan-skill.json
Then ask your agent: "Fix the failing AI readiness checks for <your-url>"Option B — Claude Code skill (CLAUDE.md)
- Download
CLAUDE.mdfrom https://aiscan.site/CLAUDE.md and place it in your project root. - Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.
Option C — MCP (Claude Desktop, Cursor, or any MCP client)
- Endpoint:
https://aiscan.site/api/mcp - Tools:
scan_website,get_fixes,get_grade - Call
get_fixeswith your URL for machine-readable fix instructions.
Option D — REST API
```
GET https://aiscan.site/api/public/scan?url=YOUR_URL
```
Returns the full report with all checks and fix details.Re-scan at https://aiscan.site to verify after applying fixes.
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 thepublic/folder — they're served from the site root automatically.Publish OAuth discovery metadata
If your API supports OAuth, serve RFC 8414 metadata at
/.well-known/oauth-authorization-serverand/or RFC 9728 at/.well-known/oauth-protected-resource.Verify
After deploying, re-scan at https://aiscan.site. You can also test with
curl -Iorcurldirectly.- Download
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of aihrbd.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Faihrbd.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade D (48/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=48&grade=D&host=aihrbd.com" alt="AIScan.site Grade D — 48/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Faihrbd.com%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Scan your own site
Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.