N
Detected framework · 99% confidence

Next.js

https://www.airtable.com/
D42 / 100
Grade D · Level 2ReadableWeak — agents will struggle with most tasks here.
Why we think this is Next.js (3 signals)
  • · x-powered-by: Next.js
  • · hosted on Vercel
  • · /_next/static/ asset
6 checks need fixing

4 failed · 2 partial 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 expose /path/index.md.

    See full details
  • 02Fail

    /llms.txt

    +6 pts if fixed

    Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.

    See full details
  • 03Fail

    Explicit AI bot rules

    +5 pts if fixed

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

    See full details
Hand-off prompt for your coding agent6 issues
# Agent-readiness remediation brief

Site: https://www.airtable.com/
Platform: nextjs (99% confidence)
AIScan score: 42/100 — Level 2 (Readable)
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 expose /path/index.md.
- **[C2] /llms.txt** — FAIL
  - Evidence: HTTP 404
  - 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)** — PARTIAL
  - Evidence: h1: 1, title: true, meta description: true, JSON-LD: false
  - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.
- **[P1] API Catalog (RFC 9727)** — FAIL
  - Evidence: 404 at /.well-known/api-catalog
  - Fix: Publish /.well-known/api-catalog linking to your OpenAPI descriptions.
- **[D3] Link header for discovery** — PARTIAL
  - Evidence: Link: </_next/static/chunks/0.nrh~p3d_the.css?dpl=dpl_7HJgHnaQF92JdtgGp4xfXqv7Xh5b>; rel=preload; as="style", </_next/static/chunks/0oxaf--cl7esr.css?dpl=dpl_7HJgHnaQF92JdtgGp4xfXqv7Xh5b>; rel=preload; as="
  - Fix: Add a Link header with rel="api-catalog" or rel="describedby".

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

85

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

21

Content

17

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

12
  • 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 expose /path/index.md.

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

    3.Test it
    curl -H "Accept: text/markdown" https://yoursite.com/
    4.Verify

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

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

    ID · C2

    What we found

    HTTP 404

    How to fix it

    Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.

    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.Create /llms.txt at the site root

    Follows the llmstxt.org spec: a single H1, optional blockquote summary, then `##` sections of markdown links.

    3.Template
    # Example Co
    > One-line summary of what this site / product does.
    
    A short paragraph explaining the audience, what's here, and how
    to navigate it.
    
    ## Docs
    - [Getting started](/docs/quickstart): install, first call in 5 min
    - [API reference](/docs/api): all endpoints, params, examples
    
    ## Pages
    - [Pricing](/pricing): plans and limits
    - [Changelog](/changelog): recent releases
    
    ## Optional
    - [Brand assets](/press): logos and screenshots
    
    4.Verify

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

Bot Access

0

Are AI crawlers explicitly allowed or blocked?

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

Capabilities

50

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

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

    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 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" }
      ]
    }
    3.Verify

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

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.airtable.com graded D

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

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