Is sharfuzzaman.com AI agent ready? B · 79/100
Why we think this is Astro (2 signals)
- · /_astro/ asset path
- · astro-island / data-astro attribute
Scan history · 4 public scans of sharfuzzaman.com
2 failed out of 14 that apply to your site.
Fix automatically with AIScan
2 open checks (2 failing) can be handed to an AI agent: P4, M4. 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://sharfuzzaman.com/”.
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://sharfuzzaman.com/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fsharfuzzaman.com%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://sharfuzzaman.com/. Individual checks that need a specific probe list it in their own guide.
Quick Wins
Top 2 fixes ranked by score impact
- 01Fail+6 pts if fixed
Machine-readable pricing
See full detailsPublish schema.org Offer / AggregateOffer JSON-LD on your pricing page with price, priceCurrency and the billing period, so an agent can answer "what does this cost?" without scraping prose.
- 02Fail+4 pts if fixed
OAuth discovery metadata
See full detailsPublish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
# Agent-readiness remediation brief Site: https://sharfuzzaman.com/ Platform: astro (99% confidence) AIScan score: 79/100 — Level 4 (Interactive) Rubric: v2026.08.2 ## Failing checks (sorted by weight) - **[M4] Machine-readable pricing** — FAIL - Evidence: no pricing page found and no JSON-LD Offer on the homepage - Fix: Publish schema.org Offer / AggregateOffer JSON-LD on your pricing page with price, priceCurrency and the billing period, so an agent can answer "what does this cost?" without scraping prose. - **[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. ## 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 Astro — 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 (6): B3, P2, P3, M1, M3, 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
100Can agents find your pages? robots, sitemaps, llms.txt.
Content
100Can agents read your content cleanly? Markdown, structured data.
Bot Access
100Are AI crawlers explicitly allowed or blocked?
Capabilities
64Can 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 · 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.
Commerce
0Can agents transact? Catalogs, checkout, agentic commerce.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · M4
What we foundno pricing page found and no JSON-LD Offer on the homepage
Measured againstHow to fix itPublish schema.org Offer / AggregateOffer JSON-LD on your pricing page with price, priceCurrency and the billing period, so an agent can answer "what does this cost?" without scraping prose.
Add Offer JSON-LD to your pricing page
One block per plan (or one AggregateOffer covering the range) so an agent can answer "what does this cost?" without reading prose.
Example
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Product", "name": "Pro", "offers": { "@type": "Offer", "price": "12.00", "priceCurrency": "USD", "priceSpecification": { "@type": "UnitPriceSpecification", "price": "12.00", "priceCurrency": "USD", "billingDuration": 1, "billingIncrement": 1, "unitCode": "MON" }, "availability": "https://schema.org/InStock", "url": "https://example.com/pricing" } } </script>Keep it truthful
The structured price must match the price a human sees; agents will quote it.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of sharfuzzaman.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fsharfuzzaman.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade B (79/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=79&grade=B&host=sharfuzzaman.com" alt="AIScan.site Grade B — 79/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fsharfuzzaman.com%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Dig deeper
sharfuzzaman.com is built on Astro. AI-agent readiness for Astro walks through the same checks on that platform.
This page always shows the most recent public scan for sharfuzzaman.com.