AIScan.site
Checking…
Re-test this site

facebook.com

Framework unknown
https://www.facebook.com/
C58 / 100
Grade C · Level 3GovernedFair — agents can find you, but a lot is left on the table.
Discoverability
31Content
67Bot Access
100Capabilities
—Commerce
—
5 checks need fixing

2 failed · 3 partial out of 7 that apply to your site.

See top fixes

Quick Wins

Top 3 fixes ranked by score impact

  • 01Fail

    XML sitemap

    +4 pts if fixed

    Publish /sitemap.xml and reference it in robots.txt.

    See full details
  • 02Fail

    Link header for discovery

    +3 pts if fixed

    Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.

    See full details
  • 03Partial

    /llms.txt

    +3 pts if fixed

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

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

Site: https://www.facebook.com/
Platform: unknown (0% confidence)
AIScan score: 58/100 — Level 3 (Governed)
Rubric: v2026-06-08.1

## Failing checks (sorted by weight)
- **[D1] robots.txt present & sane** — PARTIAL
  - Evidence: 200 OK, 20482 bytes
  - Fix: Serve a non-blocking /robots.txt that references your Sitemap.
- **[C2] /llms.txt** — PARTIAL
  - Evidence: 200 OK, 418875 bytes
  - Fix: Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
- **[D2] XML sitemap** — FAIL
  - Evidence: no /sitemap.xml or /sitemap_index.xml resolved
  - Fix: Publish /sitemap.xml and reference it in robots.txt.
- **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL
  - Evidence: h1: 0, title: true, meta description: false, JSON-LD: false
  - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.
- **[D3] Link header for discovery** — FAIL
  - Evidence: no Link header or <link> tag
  - Fix: Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.

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

31

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

12

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

    ID · D2

    What we found

    no /sitemap.xml or /sitemap_index.xml resolved

    How to fix it

    Publish /sitemap.xml and reference it in robots.txt.

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

    Generate a sitemap

    Most frameworks have a built-in sitemap generator (Next.js: app/sitemap.ts, TanStack: a route at /sitemap.xml). Publish all public URLs.

    Reference it in robots.txt

    Sitemap: https://yoursite.com/sitemap.xml

    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 · D3

    What we found

    no Link header or <link> tag

    How to fix it

    Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.

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

    Add a Link response header

    Set this header on your homepage and/or root document. Most CDNs (Cloudflare, Vercel, Netlify) support response-header rules.

    Example

    Link: </.well-known/api-catalog>; rel="api-catalog"

    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

Content

67

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

12

Bot Access

100

Are AI crawlers explicitly allowed or blocked?

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

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