AIScan.site
N
Detected framework · 99% confidence

Next.js

https://resend.com/
B77 / 100
Grade B · Level 4InteractiveGood — solid foundations, with room to polish.
Discoverability100
3/3 passing
Content100
3/3 passing
Bot Access50
1/3 passing
Capabilities64
2/4 passing
Score breakdown by dimension
Discoverability100
Content100
Bot Access50
Capabilities64
Why we think this is Next.js (3 signals)
  • · x-powered-by: Next.js
  • · hosted on Vercel
  • · /_next/static/ asset
2 checks need fixing

2 failed out of 9 that apply to your site.

See top fixes

Quick Wins

Top 2 fixes ranked by score impact

  • 01Fail

    Explicit AI bot rules

    +5 pts if fixed

    Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.

    See full details
  • 02Fail

    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 agent2 issues
# Agent-readiness remediation brief

Site: https://resend.com/
Platform: nextjs (99% confidence)
AIScan score: 77/100 — Level 4 (Interactive)
Rubric: v2026-06-08.1

## Failing checks (sorted by weight)
- **[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.
- **[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

100

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

3

Bot Access

50

Are AI crawlers explicitly allowed or blocked?

11

  • 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 found

    0 known AI agent(s) addressed in robots.txt

    How to fix it

    Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.

    1.⚡ Fix automatically with AIScan

    The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - 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 C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.

    2.Add explicit User-agent blocks

    Don't rely on `User-agent: *` alone. Address each major AI crawler so your policy is unambiguous.

    3.Recommended block
    User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: Applebot-Extended
Allow: /
    4.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

Capabilities

64

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

21

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

    1.⚡ Fix automatically with AIScan

    The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - 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 C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.

    2.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`.

    3.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 — resend.com graded B
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 resend.com on AIScan.site.

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

Track this over time

Coming soon: save sites, schedule re-scans, get email when something material changes. Standards land weekly — your tracker shouldn't be one-shot.

Free · No signup · ~20 seconds

Scan your own site

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

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