Is 8xrevenue.com AI agent ready? B · 77/100
Scan history · 3 public scans of 8xrevenue.com
2 failed · 2 partial out of 12 that apply to your site.
Fix automatically with AIScan
6 open checks (2 failing) can be handed to an AI agent: C3, B3, P2, M4, E1, E3. Pick one route — each returns the full, check-by-check instructions.
npx add-skill https://aiscan.site/aiscan-skill.jsonThen ask your agent: “Fix the failing AI readiness checks for https://8xrevenue.com/”.
curl -o CLAUDE.md https://aiscan.site/CLAUDE.mdDrop it in your project root, then ask Claude Code to fix the failing AIScan checks.
https://aiscan.site/api/mcpTools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://8xrevenue.com/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2F8xrevenue.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://8xrevenue.com/. Individual checks that need a specific probe list it in their own guide.
Quick Wins
Top 3 fixes ranked by score impact
- 01Partial+4 pts if fixed
Machine-readable pricing
See full detailsPublish 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.
- 02Fail+4 pts if fixed
Correct 404 handling
See full detailsReturn 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.
- 03Fail+4 pts if fixed
Heading hierarchy & server-rendered text
See full detailsServer-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.
# Agent-readiness remediation brief
Site: https://8xrevenue.com/
Platform: unknown (0% confidence)
AIScan score: 77/100 — Level 4 (Interactive)
Rubric: v2026.08.2
## Failing checks (sorted by weight)
- **[M4] Machine-readable pricing** — PARTIAL
- Evidence: JSON-LD offer on https://8xrevenue.com/pricing (no price fields, price 0 only — paid plans not described): { "@context": "https://schema.org", "@type": "Service", "serviceType": "B2B Lead Generation", "provider": { "@type": "Organization", "name": "8XRevenue", "url": "https://8xrevenue.
- 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.
- **[P2] MCP Server Card** — PARTIAL
- Evidence: HTTP 200
- Fix: Optional: publish /.well-known/mcp/server-card.json if you expose an MCP server.
- **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL
- Evidence: h1: 0, title: true, meta description: true, JSON-LD: true
- Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.
- **[E1] Correct 404 handling** — FAIL
- Evidence: GET /aiscan-404-probe-gy4fsu → HTTP 200 (soft 404 — returns 200 for a missing page), 21810 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** — FAIL
- Evidence: 9 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.
- **[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.
Baseline every site should meet.
Strong signals most sites benefit from.
Emerging standards. Can only add points.
Not counted (4): B1, P4, M3, E2 — 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
81Can 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 · E1
What we foundGET /aiscan-404-probe-gy4fsu → HTTP 200 (soft 404 — returns 200 for a missing page), 21810 bytes, text/html
Measured againstHow to fix itReturn 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(or410), never200. 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
Content
80Can agents read your content cleanly? Markdown, structured data.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · E3
What we found9 words of server-rendered text, 0 <h2>, 0 <h3>
Measured againstHow to fix itServer-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.
Server-render your main copy
Agents that don't execute JavaScript see only the HTML you ship. Aim for at least 150 words of real, server-rendered text on the homepage.
Use a real heading outline
One
<h1>for the page topic, then descriptive<h2>sections and<h3>sub-sections. Don't fake headings with styled<div>s.Verify what a crawler sees
curl -s https://yoursite.com/ | sed 's/<[^>]*>/ /g' | tr -s ' ' | head -c 800
Bot Access
75Are AI crawlers explicitly allowed or blocked?
Capabilities
75Can agents do things? APIs, auth, MCP, Agent Skills.
Commerce
64Can agents transact? Catalogs, checkout, agentic commerce.
Share as a social image
Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.
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.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of 8xrevenue.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2F8xrevenue.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade B (77/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=77&grade=B&host=8xrevenue.com" alt="AIScan.site Grade B — 77/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2F8xrevenue.com%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Dig deeper
8xrevenue.com is built on Custom / Unknown. AI-agent readiness for custom and unrecognised stacks walks through the same checks on that platform.
This page always shows the most recent public scan for 8xrevenue.com.