9 open checks (3 failing) can be handed to an AI agent: D1, D2, D3, C2, C3, B3, P2, E1, E4. 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://syncfoods.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://syncfoods.com/" }.

Option D — REST API

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

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
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
03Fail
Link header for discovery
+3 pts if fixed
Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.
See full details

Hand-off prompt for your coding agent9 issues

# Agent-readiness remediation brief

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

## Failing checks (sorted by weight)
- **[D1] robots.txt present & sane** — PARTIAL
  - Evidence: 200 OK, 30184 bytes
  - Fix: Serve a non-blocking /robots.txt that references your Sitemap.
- **[C2] /llms.txt** — PARTIAL
  - Evidence: 200 OK, 28348 bytes
  - Fix: Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
- **[P2] MCP Server Card** — PARTIAL
  - Evidence: HTTP 200
  - Fix: Optional: publish /.well-known/mcp/server-card.json if you expose an MCP server.
- **[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: 1, title: true, meta description: true, 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-ibw524 → HTTP 200 (soft 404 — returns 200 for a missing page), 28348 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.
- **[E4] HTTPS & canonical host** — PARTIAL
  - Evidence: final origin https://syncfoods.com · http:// does NOT upgrade to https · www.syncfoods.com serves its own copy (duplicate origin) · no HSTS header
  - Fix: Serve the site over HTTPS, 301-redirect http:// to https://, and redirect the www/apex variant to a single canonical host so agents don't index two copies of every URL.
- **[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.
- **[B3] Web Bot Auth key directory** — PARTIAL
  - Evidence: HTTP 200
  - Fix: Optional: serve a JWKS-style key directory at /.well-known/http-message-signatures-directory.

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

18 / 31 pts

Baseline every site should meet.

Recommended

11 / 17 pts

Strong signals most sites benefit from.

Bonus earned

5 signals

Emerging standards. Can only add points.

Not counted (3): P4, 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

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

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
Measured against
Sitemaps XML protocol 0.9 RFC 9309 §2.2.3 (Sitemap directive)
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
Measured against
RFC 8288 — Web Linking RFC 9727 — API catalog link relation
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-ibw524 → HTTP 200 (soft 404 — returns 200 for a missing page), 28348 bytes, text/html
Measured against
RFC 9110 §15.5.5 — 404 Not Found Google Search Central — soft 404s
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

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

Bot Access

Are AI crawlers explicitly allowed or blocked?

Capabilities

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

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

HTML

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

Markdown

[![AIScan.site Grade B — 65/100](https://aiscan.site/api/public/badge.svg?score=65&grade=B&host=syncfoods.com)](https://aiscan.site/?u=https%3A%2F%2Fsyncfoods.com%2F)

Create a free account to track this site over time

Save scan history
See score trends
Re-scan anytime

Dig deeper

Scan any site from Telegram

Send a URL to @AISiteScanBot and get an instant AI-readiness score + top fixes.

Open in Telegram

Automate your AI-readiness

Plug AIScan into your agent stack or chat with it on the go.

Use the MCP server

One line in Claude Code or Cursor to scan any site from your agent.

Chat with the Telegram bot

Scan sites and get fixes right from @AISiteScanBot.

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 site Scan your site

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

Is syncfoods.com AI agent ready? B · 65/100

syncfoods.com

Fix automatically with AIScan

Quick Wins

XML sitemap

Correct 404 handling

Link header for discovery

How this score is calculated

robots.txt present & sane

XML sitemap

Generate a sitemap

Reference it in robots.txt

Link header for discovery

Add a Link response header

Example

Correct 404 handling

Return a real 404 status

Make the body recoverable

Verify

HTTPS & canonical host

Markdown content negotiation

/llms.txt

Structured HTML (title, meta, JSON-LD, single H1)

Heading hierarchy & server-rendered text

Content Signals in robots.txt

Explicit AI bot rules

Web Bot Auth key directory

API Catalog (RFC 9727)

MCP Server Card

Agent Skills index

OAuth discovery metadata

Machine-readable API description

Share as a social image

Embed your AIScan badge

Create a free account to track this site over time

Dig deeper

Automate your AI-readiness

Scan your own site