Is bookxride.com AI agent ready? B · 75/100
Why we think this is Next.js (2 signals)
- · x-powered-by: Next.js
- · /_next/static/ asset
3 failed · 2 partial out of 13 that apply to your site.
Fix automatically with AIScan
5 open checks (3 failing) can be handed to an AI agent: D2, C3, P4, E3, E4. 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://bookxride.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://bookxride.com/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fbookxride.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://bookxride.com/. Individual checks that need a specific probe list it in their own guide.
Quick Wins
Top 3 fixes ranked by score impact
- 01Fail+4 pts if fixed
XML sitemap
See full detailsPublish /sitemap.xml and reference it in robots.txt.
- 02Fail+4 pts if fixed
OAuth discovery metadata
See full detailsPublish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
- 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://bookxride.com/ Platform: nextjs (99% confidence) AIScan score: 75/100 — Level 4 (Interactive) Rubric: v2026.08.2 ## Failing checks (sorted by weight) - **[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: true, JSON-LD: false - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD. - **[P4] OAuth discovery metadata** — FAIL - Evidence: auth-server: 404, protected-resource: 404 - Fix: Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints. - **[E3] Heading hierarchy & server-rendered text** — FAIL - Evidence: 5 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. - **[E4] HTTPS & canonical host** — PARTIAL - Evidence: final origin https://bookxride.com · http:// does NOT upgrade to https · www.bookxride.com serves its own copy (duplicate origin) · HSTS set - 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. ## 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 Next.js — 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): B3, P2, P3, 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
71Can 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 foundno /sitemap.xml or /sitemap_index.xml resolved
Measured againstHow to fix itPublish /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
Content
73Can 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 found5 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
100Are AI crawlers explicitly allowed or blocked?
Capabilities
64Can agents do things? APIs, auth, MCP, Agent Skills.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · P4
What we foundauth-server: 404, protected-resource: 404
Measured againstHow to fix itPublish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
Publish OAuth discovery metadata
If your API supports OAuth, serve RFC 8414 metadata at
/.well-known/oauth-authorization-serverand/or RFC 9728 at/.well-known/oauth-protected-resource.
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 bookxride.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fbookxride.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade B (75/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=75&grade=B&host=bookxride.com" alt="AIScan.site Grade B — 75/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fbookxride.com%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Dig deeper
Automate your AI-readiness
Plug AIScan into your agent stack or chat with it on the go.
Scan your own site
Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.