Is mamayaan.com AI agent ready? C · 62/100
Scan history · 2 public scans of mamayaan.com
3 failed · 3 partial out of 10 that apply to your site.
Fix automatically with AIScan
6 open checks (3 failing) can be handed to an AI agent: C2, C3, B2, E1, E3, E4. 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://mamayaan.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://mamayaan.com/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fmamayaan.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://mamayaan.com/. Individual checks that need a specific probe list it in their own guide.
Quick Wins
Top 3 fixes ranked by score impact
- 01Fail+5 pts if fixed
Explicit AI bot rules
See full detailsAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
- 02Fail+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.
- 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://mamayaan.com/ Platform: unknown (0% confidence) AIScan score: 62/100 — Level 3 (Governed) Rubric: v2026.08.2 ## Failing checks (sorted by weight) - **[C2] /llms.txt** — PARTIAL - Evidence: 200 OK, 1013 bytes - Fix: Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links. - **[B2] Explicit AI bot rules** — FAIL - Evidence: 0 known AI agent(s) addressed in robots.txt - Fix: Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc. - **[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. - **[E1] Correct 404 handling** — FAIL - Evidence: GET /aiscan-404-probe-tnnzj1 → HTTP 200 (soft 404 — returns 200 for a missing page), 1013 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** — PARTIAL - Evidence: 69 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://mamayaan.com · http:// upgrades to https · www.mamayaan.com 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. ## 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 site like yours — 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 (7): B1, B3, P2, P3, P4, E2, 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
76Can 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 · E1
What we foundGET /aiscan-404-probe-tnnzj1 → HTTP 200 (soft 404 — returns 200 for a missing page), 1013 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
55Can 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.
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>
Bot Access
0Are AI crawlers explicitly allowed or blocked?
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · B2
What we found0 known AI agent(s) addressed in robots.txt
Measured againstHow to fix itAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
Add explicit User-agent blocks
Don't rely on
User-agent: *alone. Address each major AI crawler so your policy is unambiguous.Recommended block
User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: / User-agent: Applebot-Extended Allow: /
Capabilities
100Can agents do things? APIs, auth, MCP, Agent Skills.
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 mamayaan.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fmamayaan.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade C (62/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=62&grade=C&host=mamayaan.com" alt="AIScan.site Grade C — 62/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fmamayaan.com%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Dig deeper
mamayaan.com is built on Custom / Unknown. AI-agent readiness for custom and unrecognised stacks walks through the same checks on that platform.
This page always shows the most recent public scan for mamayaan.com.