Is beautybooth.com.bd AI agent ready? C · 63/100
Why we think this is Next.js (2 signals)
- · x-powered-by: Next.js
- · /_next/static/ asset
4 failed · 1 partial out of 13 that apply to your site.
Fix automatically with AIScan
5 open checks (4 failing) can be handed to an AI agent: D3, C2, P1, P4, E1. Pick one route — each returns the full, check-by-check instructions.
npx add-skill https://aiscan.site/aiscan-skill.jsonThen ask your agent: “Fix the failing AI readiness checks for https://beautybooth.com.bd/”.
curl -o CLAUDE.md https://aiscan.site/CLAUDE.mdDrop it in your project root, then ask Claude Code to fix the failing AIScan checks.
https://aiscan.site/api/mcpTools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://beautybooth.com.bd/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fbeautybooth.com.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://beautybooth.com.bd/. Individual checks that need a specific probe list it in their own guide.
Quick Wins
Top 3 fixes ranked by score impact
- 01Fail+4 pts if fixed
API Catalog (RFC 9727)
See full detailsPublish /.well-known/api-catalog linking to your OpenAPI descriptions.
- 02Fail+4 pts if fixed
OAuth discovery metadata
See full detailsPublish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
- 03Fail+4 pts if fixed
Correct 404 handling
See full detailsReturn 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.
# Agent-readiness remediation brief Site: https://beautybooth.com.bd/ Platform: nextjs (99% confidence) AIScan score: 63/100 — Level 3 (Governed) Rubric: v2026.08.2 ## Failing checks (sorted by weight) - **[C2] /llms.txt** — PARTIAL - Evidence: 200 OK, 193186 bytes - Fix: Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links. - **[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-7ttv72 → HTTP 200 (soft 404 — returns 200 for a missing page), 193852 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. - **[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.
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 Next.js — so checks that don't apply never drag you down.
Baseline every site should meet.
Strong signals most sites benefit from.
Emerging standards. Can only add points.
Not counted (5): B1, 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
67Can 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
Measured againstHow to fix itAdd a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.
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"
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 foundGET /aiscan-404-probe-7ttv72 → HTTP 200 (soft 404 — returns 200 for a missing page), 193852 bytes, text/html
Measured againstHow to fix itReturn 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.
Return a real 404 status
A missing page must answer
404(or410), never200. 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
Content
86Can agents read your content cleanly? Markdown, structured data.
Bot Access
100Are AI crawlers explicitly allowed or blocked?
Capabilities
27Can 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
Measured againstHow to fix itPublish /.well-known/api-catalog linking to your OpenAPI descriptions.
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" } ] }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
Measured againstHow to fix itPublish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
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.
Share as a social image
Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.
Tip: for X and LinkedIn, upload the downloaded PNG with your post so the card shows in the feed. Posts that include just the link will still preview AIScan.site.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of beautybooth.com.bd on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fbeautybooth.com.bd%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade C (63/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=63&grade=C&host=beautybooth.com.bd" alt="AIScan.site Grade C — 63/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fbeautybooth.com.bd%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Dig deeper
Automate your AI-readiness
Plug AIScan into your agent stack or chat with it on the go.
Scan your own site
Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.