Is nexora-agency-landin-3d8q.bolt.host AI agent ready? C · 52/100
nexora-agency-landin-3d8q.bolt.host
Why we think this is Bolt (1 signals)
- · Bolt marker
Scan history · 2 public scans of nexora-agency-landin-3d8q.bolt.host
6 failed · 4 partial out of 13 that apply to your site.
Fix automatically with AIScan
12 open checks (6 failing) can be handed to an AI agent: D1, D2, D3, C2, C3, B3, P2, P4, E1, E2, 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://nexora-agency-landin-3d8q.bolt.host/”.
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://nexora-agency-landin-3d8q.bolt.host/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fnexora-agency-landin-3d8q.bolt.host%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://nexora-agency-landin-3d8q.bolt.host/. 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
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.
# Task: raise AIScan agent-readiness score Site: https://nexora-agency-landin-3d8q.bolt.host/ Platform: bolt (50% confidence) AIScan score: 52/100 — Level 3 (Governed) Rubric: v2026.08.2 Implement the fixes below in this repository. Make atomic commits per check id. After all edits, run the build to confirm nothing breaks. ## Failing checks - **[D1] robots.txt present & sane** — PARTIAL - Evidence: 200 OK, 2630 bytes - Fix: Serve a non-blocking /robots.txt that references your Sitemap. - **[C2] /llms.txt** — PARTIAL - Evidence: 200 OK, 794 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: 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: 200, protected-resource: 200 - Fix: Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints. - **[E1] Correct 404 handling** — FAIL - Evidence: GET /aiscan-404-probe-0akdj7 → HTTP 200 (soft 404 — returns 200 for a missing page), 794 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: 8 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://nexora-agency-landin-3d8q.bolt.host · http:// does NOT upgrade to https · www.nexora-agency-landin-3d8q.bolt.host 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. - **[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. - **[E2] Machine-readable API description** — FAIL - Evidence: no /openapi.json, /api/openapi.json or swagger document found - Fix: Publish an OpenAPI 3.1 document at /openapi.json and reference it from /.well-known/api-catalog as a service-desc link. ## Notes - Treat `public/` (or framework equivalent) as the source for `robots.txt`, `llms.txt`, and `.well-known/` files. - For Markdown content negotiation, respond to `Accept: text/markdown` and `?format=md` on canonical content URLs. - For MCP / Agent Skills, drop card files under `.well-known/` even if the server isn't live yet — discovery matters first.
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 Bolt — 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 (1): 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
29Can 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
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 foundno Link header or <link> tag
Measured againstHow to fix itAdd 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"
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-0akdj7 → HTTP 200 (soft 404 — returns 200 for a missing page), 794 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
59Can 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 found8 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
85Are AI crawlers explicitly allowed or blocked?
Capabilities
47Can 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: 200, protected-resource: 200
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.Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · E2
What we foundno /openapi.json, /api/openapi.json or swagger document found
Measured againstHow to fix itPublish an OpenAPI 3.1 document at /openapi.json and reference it from /.well-known/api-catalog as a service-desc link.
Publish an OpenAPI 3.1 description
Serve it at
/openapi.json(or/openapi.yaml). Describe every public endpoint, its parameters, and its response schema.Advertise it
Reference it from
/.well-known/api-catalogas aservice-desclink and from aLinkresponse header.Link: </openapi.json>; rel="service-desc"; type="application/json"
Content sites can skip this
If you expose no programmatic API, this check is informational and costs you nothing.
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 nexora-agency-landin-3d8q.bolt.host on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fnexora-agency-landin-3d8q.bolt.host%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=nexora-agency-landin-3d8q.bolt.host" alt="AIScan.site Grade C — 52/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fnexora-agency-landin-3d8q.bolt.host%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Dig deeper
This page always shows the most recent public scan for nexora-agency-landin-3d8q.bolt.host.