8 open checks (5 failing) can be handed to an AI agent: C1, C3, P1, P4, E1, E2, E3, E4. Pick one route — each returns the full, check-by-check instructions.

Option A — Agent Skill (any runtime)

npx add-skill https://aiscan.site/aiscan-skill.json

Then ask your agent: “Fix the failing AI readiness checks for https://hijabi.bd/”.

Option B — Claude Code (CLAUDE.md)

curl -o CLAUDE.md https://aiscan.site/CLAUDE.md

Drop it in your project root, then ask Claude Code to fix the failing AIScan checks.

Option C — MCP client

https://aiscan.site/api/mcp

Tools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://hijabi.bd/" }.

Option D — REST API

curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fhijabi.bd%2F'

Returns every check with its complete fix guide.

Verify: Re-scan at https://aiscan.site after applying fixes, or run npx aiscan-cli https://hijabi.bd/. Individual checks that need a specific probe list it in their own guide.

Quick Wins

Top 3 fixes ranked by score impact

01Partial
Markdown content negotiation
+4 pts if fixed
Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.
See full details
02Fail
API Catalog (RFC 9727)
+4 pts if fixed
Publish /.well-known/api-catalog linking to your OpenAPI descriptions.
See full details
03Fail
OAuth discovery metadata
+4 pts if fixed
Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
See full details

Hand-off prompt for your coding agent8 issues

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

Site: https://hijabi.bd/
Platform: lovable (80% confidence)
AIScan score: 53/100 — Level 3 (Governed)
Rubric: v2026.08.2

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** — PARTIAL
  - Evidence: Accept: text/markdown → 200 (text/markdown; charset=utf-8)
  - 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: 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.
- **[E1] Correct 404 handling** — FAIL
  - Evidence: GET /aiscan-404-probe-bk1dre → HTTP 200 (soft 404 — returns 200 for a missing page), 3395 bytes, text/html
  - Fix: Return a real HTTP 404 (not 200) for missing pages, with a body that names the site and links to your homepage, sitemap, and search so an agent can recover.
- **[E3] Heading hierarchy & server-rendered text** — FAIL
  - Evidence: 9 words of server-rendered text, 0 <h2>, 0 <h3>
  - Fix: Server-render your main copy and break it into a real heading outline (one h1, then descriptive h2/h3 sections). Agents that don't execute JavaScript only see the HTML you ship.
- **[E4] HTTPS & canonical host** — PARTIAL
  - Evidence: final origin https://hijabi.bd · http:// upgrades to https · www.hijabi.bd serves its own copy (duplicate origin) · HSTS set
  - Fix: Serve the site over HTTPS, 301-redirect http:// to https://, and redirect the www/apex variant to a single canonical host so agents don't index two copies of every URL.
- **[E2] Machine-readable API description** — FAIL
  - Evidence: no /openapi.json, /api/openapi.json or swagger document found
  - Fix: Publish an OpenAPI 3.1 document at /openapi.json and reference it from /.well-known/api-catalog as a service-desc link.

### 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.

How this score is calculated

Every check earns points against a weight. We divide the points you earned by the points that actually apply to a Lovable — so checks that don't apply never drag you down.

Essential

20 / 31 pts

Baseline every site should meet.

Recommended

13 / 28 pts

Strong signals most sites benefit from.

Bonus earned

1 signal

Emerging standards. Can only add points.

Not counted (4): B3, P2, P3, E5 — either not applicable to this site profile or optional and not yet adopted. Expand any check to see the exact evidence we based it on.

Discoverability

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

311

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · E1
What we found
GET /aiscan-404-probe-bk1dre → HTTP 200 (soft 404 — returns 200 for a missing page), 3395 bytes, text/html
Measured against
RFC 9110 §15.5.5 — 404 Not Found Google Search Central — soft 404s
How to fix it
Return a real HTTP 404 (not 200) for missing pages, with a body that names the site and links to your homepage, sitemap, and search so an agent can recover.
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.
Return a real 404 status
A missing page must answer 404 (or 410), never 200. A soft 404 makes agents index your error page as real content.
Make the body recoverable
The 404 body should name the site and link to the homepage, sitemap, docs, and search so an agent can find its way back instead of dead-ending.
Verify
curl -sI https://yoursite.com/this-page-does-not-exist-123 | head -n 1
Fix in ChatGPT Fix in Claude

Content

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

121

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · E3
What we found
9 words of server-rendered text, 0 <h2>, 0 <h3>
Measured against
HTML Living Standard — headings and outlines WCAG 2.2 SC 1.3.1 — Info and Relationships
How to fix it
Server-render your main copy and break it into a real heading outline (one h1, then descriptive h2/h3 sections). Agents that don't execute JavaScript only see the HTML you ship.
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.
Server-render your main copy
Agents that don't execute JavaScript see only the HTML you ship. Aim for at least 150 words of real, server-rendered text on the homepage.
Use a real heading outline
One <h1> for the page topic, then descriptive <h2> sections and <h3> sub-sections. Don't fake headings with styled <div>s.
Verify what a crawler sees
curl -s https://yoursite.com/ | sed 's/<[^>]*>/ /g' | tr -s ' ' | head -c 800
Fix in ChatGPT Fix in Claude

Bot Access

100

Are AI crawlers explicitly allowed or blocked?

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
Measured against
RFC 9727 — API Catalog RFC 9264 — Linkset
How to fix it
Publish /.well-known/api-catalog linking to your OpenAPI descriptions.
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.
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" } ] }
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
Measured against
RFC 9728 — OAuth 2.0 Protected Resource Metadata RFC 8414 — OAuth 2.0 Authorization Server Metadata
How to fix it
Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
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.
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.
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 · E2
What we found
no /openapi.json, /api/openapi.json or swagger document found
Measured against
OpenAPI Specification 3.1 RFC 9727 — `service-desc` link relation
How to fix it
Publish an OpenAPI 3.1 document at /openapi.json and reference it from /.well-known/api-catalog as a service-desc link.
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.
Publish an OpenAPI 3.1 description
Serve it at /openapi.json (or /openapi.yaml). Describe every public endpoint, its parameters, and its response schema.
Advertise it
Reference it from /.well-known/api-catalog as a service-desc link and from a Link response header.
Link: </openapi.json>; rel="service-desc"; type="application/json"
Content sites can skip this
If you expose no programmatic API, this check is informational and costs you nothing.
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 hijabi.bd on AIScan.site.

HTML

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

Markdown

[![AIScan.site Grade C — 53/100](https://aiscan.site/api/public/badge.svg?score=53&grade=C&host=hijabi.bd)](https://aiscan.site/?u=https%3A%2F%2Fhijabi.bd%2F)

Create a free account to track this site over time

Save scan history
See score trends
Re-scan anytime

Dig deeper

Scan any site from Telegram

Send a URL to @AISiteScanBot and get an instant AI-readiness score + top fixes.

Open in Telegram

Automate your AI-readiness

Plug AIScan into your agent stack or chat with it on the go.

Use the MCP server

One line in Claude Code or Cursor to scan any site from your agent.

Chat with the Telegram bot

Scan sites and get fixes right from @AISiteScanBot.

Free · No signup · ~20 seconds

Scan your own site

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

Re-test this site Scan your site

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

Is hijabi.bd AI agent ready? C · 53/100

hijabi.bd

Fix automatically with AIScan

Quick Wins

Markdown content negotiation

API Catalog (RFC 9727)

OAuth discovery metadata

How this score is calculated

robots.txt present & sane

XML sitemap

Link header for discovery

Correct 404 handling

This is a Lovable project

Return a real 404 status

Make the body recoverable

Verify

HTTPS & canonical host

Markdown content negotiation

/llms.txt

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

Heading hierarchy & server-rendered text

This is a Lovable project

Server-render your main copy

Use a real heading outline

Verify what a crawler sees

Content Signals in robots.txt

Explicit AI bot rules

Web Bot Auth key directory

API Catalog (RFC 9727)

This is a Lovable project

Publish an API catalog (RFC 9727)

MCP Server Card

Agent Skills index

OAuth discovery metadata

This is a Lovable project

Publish OAuth discovery metadata

Machine-readable API description

This is a Lovable project

Publish an OpenAPI 3.1 description

Advertise it

Content sites can skip this

Share as a social image

Embed your AIScan badge

Create a free account to track this site over time

Dig deeper

Automate your AI-readiness

Scan your own site