fox8.com
10/100 Closed by policy
Audited October 17, 2026 — fox8.com has since dropped out of the panel, so this is the last audit we ran rather than today's from public surfaces only. Can AI agents discover, read, and act on fox8.com? Check by check:
GPTBot: blocked ClaudeBot: blocked Claude-User: partial PerplexityBot: blocked Google-Extended: blocked CCBot: blocked
| Check | Finding | Points | Result |
|---|---|---|---|
| A1 | llms.txt for AI readers No /llms.txt found — AI readers get no curated entry point. |
0/15 | fail |
| A2 | AI crawler access policy robots.txt blocks: GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot. |
0/15 | fail |
| A3 | Content readable without a browser A bot challenge page blocks plain fetches — agents see a wall, not your content. |
0/25 | fail |
| A4 | Structured data (schema.org JSON-LD) No machine-readable entity markup on the homepage. |
0/15 | fail |
| A5 | Sitemap discoverable Sitemap advertised in robots.txt or served at /sitemap.xml. |
10/10 | pass |
| A6 | Everyday agent tasks reachable from the homepage None of pricing, support, docs, or legal are linked from the homepage. |
0/20 | fail |
| B1 | MCP server advertised No MCP advertisement (bonus check — most sites skip this). |
0/5 | skip |
| B2 | OpenAPI description published No OpenAPI document (bonus check — only relevant for APIs). |
0/5 | skip |
What fox8.com would have to change
5 checks cost fox8.com points. Each one below is the specific remedy for what we measured, not general advice.
- llms.txt for AI readers0/15
Serve a plain-text file at
https://fox8.com/llms.txtlisting the pages an agent most often needs — pricing, docs, support, account management — each as a one-line description and an absolute URL. It is read by an agent arriving cold with no idea of your structure. Fifteen points, and most teams ship it in an afternoon. - AI crawler access policy0/15
Your
robots.txtcurrently refuses GPTBot, ClaudeBot, Claude-User, PerplexityBot, Google-Extended, CCBot. If that is deliberate, this score is the cost and the trade is yours to make. If it is inherited from an old rule or a security plugin — which is the commonest cause we see — those agents cannot read fox8.com on a user's behalf at all. - Content readable without a browser0/25
A bot challenge page blocks plain fetches — agents see a wall, not your content. An agent fetches the page and reads what comes back; it does not run your JavaScript. Server-render the main content, or serve the same text to a plain request. This is the heaviest check on the board at 25 points, and the one that most often decides whether an agent can use a site at all.
- Structured data (schema.org JSON-LD)0/15
Add schema.org JSON-LD to the homepage —
Organizationat minimum, plusProductorArticlewhere they apply. It is how an agent learns what fox8.com is without inferring it from prose. - Everyday agent tasks reachable from the homepage0/20
An agent could not reach pricing, support/contact, docs/api, legal/privacy from the fox8.com homepage. These are what agents are sent to find most often. Each needs a plain link an agent can follow from the homepage in one hop — not behind a menu that only appears once JavaScript runs, and not solely in a logged-in view.
- MCP server advertised0/5
Optional, and rare — only a handful of the sites we track run one. An MCP server lets an agent act on fox8.com through a defined interface instead of scraping it. Advertise it at
/.well-known/mcp/server-card.json. - OpenAPI description published0/5
Optional. If fox8.com has a public API, publishing an OpenAPI document at
/openapi.jsonlets an agent call it correctly without a human reading your docs first.
Put this score on your site
The badge reads live from this page, so it updates itself when the score changes. Free, no attribution required beyond the link it already carries.
HTML
Markdown