AIScan.site

Is facebook.com AI agent ready? C · 52/100

Re-test this site

facebook.com

Framework unknown
https://www.facebook.com/
C52 / 100
Grade C · Level 3GovernedFair — agents can find you, but a lot is left on the table.
Discoverability
48Content
59Bot Access
100Capabilities
—Commerce
0

Scan history · 7 public scans of facebook.com

WhenScoreGradeSnapshot
1 Sept 2026, 6:59 UTC75c584eb52/100CView →
17 Aug 2026, 10:35 UTCfc76a1dc64/100CView →
5 Jul 2026, 12:44 UTCf8c4cb9358/100CView →
3 Jul 2026, 12:53 UTC3bdcf97164/100CView →
2 Jul 2026, 20:44 UTCafcc702058/100CView →
29 Jun 2026, 11:41 UTC8abb59e358/100CView →
25 Jun 2026, 8:32 UTC4bd2642558/100CView →
7 checks need fixing

4 failed · 3 partial out of 11 that apply to your site.

See top fixes

Fix automatically with AIScan

7 open checks (4 failing) can be handed to an AI agent: D2, D3, C2, C3, M4, E1, E3. Pick one route — each returns the full, check-by-check instructions.

Option A — Agent Skill (any runtime)
npx add-skill https://aiscan.site/aiscan-skill.json

Then ask your agent: “Fix the failing AI readiness checks for https://www.facebook.com/”.

Option B — Claude Code (CLAUDE.md)
curl -o CLAUDE.md https://aiscan.site/CLAUDE.md

Drop it in your project root, then ask Claude Code to fix the failing AIScan checks.

Option C — MCP client
https://aiscan.site/api/mcp

Tools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://www.facebook.com/" }.

Option D — REST API
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fwww.facebook.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://www.facebook.com/. Individual checks that need a specific probe list it in their own guide.

Quick Wins

Top 3 fixes ranked by score impact

  • 01Fail

    Machine-readable pricing

    +6 pts if fixed

    Publish schema.org Offer / AggregateOffer JSON-LD on your pricing page with price, priceCurrency and the billing period, so an agent can answer "what does this cost?" without scraping prose.

    See full details
  • 02Fail

    XML sitemap

    +4 pts if fixed

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

    See full details
  • 03Fail

    Correct 404 handling

    +4 pts if fixed

    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.

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

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

## Failing checks (sorted by weight)
- **[C2] /llms.txt** — PARTIAL
  - Evidence: 200 OK, 433120 bytes
  - Fix: Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
- **[M4] Machine-readable pricing** — FAIL
  - Evidence: no JSON-LD Offer found on /pricing or the homepage
  - Fix: Publish schema.org Offer / AggregateOffer JSON-LD on your pricing page with price, priceCurrency and the billing period, so an agent can answer "what does this cost?" without scraping prose.
- **[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.
- **[E1] Correct 404 handling** — FAIL
  - Evidence: GET /aiscan-404-probe-f15k4c → HTTP 200 (soft 404 — returns 200 for a missing page), 433099 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: 79 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.
- **[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.

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.

Essential
17 / 37 pts

Baseline every site should meet.

Recommended
11 / 17 pts

Strong signals most sites benefit from.

Bonus earned
0 signals

Emerging standards. Can only add points.

Not counted (10): B1, B3, P1, P2, P3, P4, M1, M3, 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

48

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

23

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

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

    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"
    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 · E1

    What we found

    GET /aiscan-404-probe-f15k4c → HTTP 200 (soft 404 — returns 200 for a missing page), 433099 bytes, text/html

    How to fix it

    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.

    Return a real 404 status

    A missing page must answer 404 (or 410), never 200. 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
    Fix in ChatGPT Fix in Claude

Content

59

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

13

Bot Access

100

Are AI crawlers explicitly allowed or blocked?

1

Commerce

0

Can agents transact? Catalogs, checkout, agentic commerce.

1

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

    ID · M4

    What we found

    no JSON-LD Offer found on /pricing or the homepage

    How to fix it

    Publish schema.org Offer / AggregateOffer JSON-LD on your pricing page with price, priceCurrency and the billing period, so an agent can answer "what does this cost?" without scraping prose.

    Add Offer JSON-LD to your pricing page

    One block per plan (or one AggregateOffer covering the range) so an agent can answer "what does this cost?" without reading prose.

    Example

    <script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Pro",
  "offers": {
    "@type": "Offer",
    "price": "12.00",
    "priceCurrency": "USD",
    "priceSpecification": {
      "@type": "UnitPriceSpecification",
      "price": "12.00",
      "priceCurrency": "USD",
      "billingDuration": 1,
      "billingIncrement": 1,
      "unitCode": "MON"
    },
    "availability": "https://schema.org/InStock",
    "url": "https://example.com/pricing"
  }
}
</script>

    Keep it truthful

    The structured price must match the price a human sees; agents will quote it.

    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.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 (52/100) — AIScan.site">
  <img src="https://aiscan.site/api/public/badge.svg?score=52&grade=C&host=www.facebook.com" alt="AIScan.site Grade C — 52/100" width="240" height="64" loading="lazy" />
</a>
Markdown
[![AIScan.site Grade C — 52/100](https://aiscan.site/api/public/badge.svg?score=52&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 →

Dig deeper

Scan any site from Telegram
Open in Telegram

facebook.com is built on Custom / Unknown. AI-agent readiness for custom and unrecognised stacks walks through the same checks on that platform.

Scan any site from Telegram
Open in Telegram

This page always shows the most recent public scan for facebook.com.

Browse all public scansScan your site