2 failed out of 7 that apply to your site.
Quick Wins
Top 2 fixes ranked by score impact
- 01Fail+4 pts if fixed
Structured HTML (title, meta, JSON-LD, single H1)
See full detailsEnsure a single <h1>, <title>, meta description, and schema.org JSON-LD.
- 02Fail+3 pts if fixed
Link header for discovery
See full detailsAdd a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.
# Agent-readiness remediation brief Site: https://dubaicabs.com/ Platform: unknown (0% confidence) AIScan score: 80/100 — Level 4 (Interactive) Rubric: v2026-06-08.1 ## Failing checks (sorted by weight) - **[P2] MCP Server Card** — PARTIAL - Evidence: HTTP 200 - Fix: Optional: publish /.well-known/mcp/server-card.json if you expose an MCP server. - **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — FAIL - Evidence: h1: 0, title: false, meta description: false, JSON-LD: false - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD. - **[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. ## General guidance - Static-first: `robots.txt`, `llms.txt`, `/.well-known/*` JSON cards. - Markdown negotiation: serve `text/markdown` when requested via `Accept` header or `?format=md`. - Bot access: explicit allow/deny per AI user-agent (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, Bytespider, Amazonbot, CCBot, meta-externalagent, cohere-ai, Diffbot). - Capabilities: publish an MCP server card and (optionally) an Agent Skills manifest even if the runtime isn't live — discovery first. - Re-scan at aiscan.site after deploying.
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.
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
78Can 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 · C3
What we foundh1: 0, title: false, meta description: false, JSON-LD: false
How to fix itEnsure a single <h1>, <title>, meta description, and schema.org JSON-LD.
⚡ 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.
Single H1
Each page should have exactly one
<h1>describing the page topic.Title + meta description
Set a unique
<title>(≤60 chars) and<meta name="description">(≤160 chars) per page.Add JSON-LD
Embed schema.org structured data so agents can extract entities reliably.
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Organization", "name": "Example Co", "url": "https://example.com", "logo": "https://example.com/logo.png" } </script>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
75Can agents do things? APIs, auth, MCP, Agent Skills.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of dubaicabs.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fdubaicabs.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade A (80/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=80&grade=A&host=dubaicabs.com" alt="AIScan.site Grade A — 80/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fdubaicabs.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.