AIScan.site
Docs
Checking…
Re-test this site

quotway.com

Next.js · 60% confidence
https://www.quotway.com/
C55 / 100
Grade C · Level 3GovernedFair — agents can find you, but a lot is left on the table.
Discoverability
100Content
56Bot Access
100Capabilities
0Commerce
—
Why we think this is Next.js (2 signals)
  • · hosted on Vercel
  • · /_next/static/ asset
3 checks need fixing

3 failed out of 9 that apply to your site.

See top fixes

Quick Wins

Top 3 fixes ranked by score impact

  • 01Fail

    Markdown content negotiation

    +8 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 agent3 issues
# Agent-readiness remediation brief

Site: https://www.quotway.com/
Platform: nextjs (60% confidence)
AIScan score: 55/100 — Level 3 (Governed)
Rubric: v2026-06-08.1

## Failing checks (sorted by weight)
- **[C1] Markdown content negotiation** — FAIL
  - Evidence: Accept: text/markdown → 200 (text/html; charset=utf-8)
  - Fix: Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.
- **[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.

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

100

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

3

Content

56

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

21

  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · C1

    What we found

    Accept: text/markdown → 200 (text/html; charset=utf-8)

    How to fix it

    Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.

    ⚡ 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)

    1. Download CLAUDE.md from https://aiscan.site/CLAUDE.md and place it in your project root.
    2. 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_fixes with 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.

    Serve text/markdown on Accept negotiation

    When a client sends Accept: text/markdown, return a markdown rendering of the same content. The simplest path is to publish parallel .md files (e.g. /about → /about.md) and rewrite based on the Accept header.

    Test it

    curl -H "Accept: text/markdown" https://yoursite.com/

    Verify

    After deploying, re-scan at https://aiscan.site. You can also test with curl -I or curl directly.

    Fix in ChatGPT Fix in Claude

Bot Access

100

Are AI crawlers explicitly allowed or blocked?

1

Capabilities

0

Can agents do things? APIs, auth, MCP, Agent Skills.

2

  • 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

    How to fix it

    Publish /.well-known/api-catalog linking to your OpenAPI descriptions.

    ⚡ 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)

    1. Download CLAUDE.md from https://aiscan.site/CLAUDE.md and place it in your project root.
    2. 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_fixes with 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.

    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" }
  ]
}

    Verify

    After deploying, re-scan at https://aiscan.site. You can also test with curl -I or curl directly.

    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

    How to fix it

    Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.

    ⚡ 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)

    1. Download CLAUDE.md from https://aiscan.site/CLAUDE.md and place it in your project root.
    2. 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_fixes with 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.

    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.

    Verify

    After deploying, re-scan at https://aiscan.site. You can also test with curl -I or curl directly.

    Fix in ChatGPT Fix in Claude
Share the result

Share as a social image

Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.

AIScan share card — www.quotway.com graded C
Post on X Share on LinkedIn Share on Facebook

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.

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 www.quotway.com on AIScan.site.

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

Create a free account to track this site over time

  • Save scan history
  • See score trends
  • Re-scan anytime
Sign up free Already have an account? Sign in →
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 siteScan your site
Or browse the community feed to see what others have scanned.