A
Detected framework · 99% confidence

Astro

https://www.klaviyo.com/uk/
C53 / 100
Grade C · Level 3GovernedFair — agents can find you, but a lot is left on the table.
Why we think this is Astro (3 signals)
  • · HubSpot script/asset
  • · /_astro/ asset path
  • · astro-island / data-astro attribute
4 checks need fixing

4 failed out of 9 that apply to your site.

See top fixes

Quick Wins

Top 3 fixes ranked by score impact

  • 01Fail

    Markdown content negotiation

    +8 pts if fixed

    Serve text/markdown when the client sends Accept: text/markdown, or expose /path/index.md.

    See full details
  • 02Fail

    API Catalog (RFC 9727)

    +4 pts if fixed

    Publish /.well-known/api-catalog linking to your OpenAPI descriptions.

    See full details
  • 03Fail

    OAuth discovery metadata

    +4 pts if fixed

    Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.

    See full details
Hand-off prompt for your coding agent4 issues
# Agent-readiness remediation brief

Site: https://www.klaviyo.com/uk/
Platform: astro (99% confidence)
AIScan score: 53/100 — Level 3 (Governed)
Rubric: v2026-06-08.1

## Failing checks (sorted by weight)
- **[C1] Markdown content negotiation** — FAIL
  - Evidence: Accept: text/markdown → 200 (text/html; charset=UTF-8)
  - Fix: Serve text/markdown when the client sends Accept: text/markdown, or expose /path/index.md.
- **[P1] API Catalog (RFC 9727)** — FAIL
  - Evidence: 404 at /.well-known/api-catalog
  - Fix: Publish /.well-known/api-catalog linking to your OpenAPI descriptions.
- **[P4] OAuth discovery metadata** — FAIL
  - Evidence: auth-server: 403, protected-resource: 403
  - Fix: Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
- **[D3] Link header for discovery** — FAIL
  - Evidence: no Link response header
  - Fix: Add a Link header with rel="api-catalog" or rel="describedby".

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

Discoverability

77

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

21
  • 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 response header

    How to fix it

    Add a Link header with rel="api-catalog" or rel="describedby".

    1.⚡ Fix automatically with AIScan

    The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.

    2.Add a Link response header

    Set this header on your homepage and/or root document. Most CDNs (Cloudflare, Vercel, Netlify) support response-header rules.

    3.Example
    Link: </.well-known/api-catalog>; rel="api-catalog"
    4.Verify

    After deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.

Content

56

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

21
  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · C1

    What we found

    Accept: text/markdown → 200 (text/html; charset=UTF-8)

    How to fix it

    Serve text/markdown when the client sends Accept: text/markdown, or expose /path/index.md.

    1.⚡ Fix automatically with AIScan

    The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.

    2.Serve text/markdown on Accept negotiation

    When a client sends `Accept: text/markdown`, return a markdown rendering of the same content. The simplest path is to publish parallel `.md` files (e.g. `/about` → `/about.md`) and rewrite based on the Accept header.

    3.Test it
    curl -H "Accept: text/markdown" https://yoursite.com/
    4.Verify

    After deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.

Bot Access

100

Are AI crawlers explicitly allowed or blocked?

2

Capabilities

0

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

2
  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · P1

    What we found

    404 at /.well-known/api-catalog

    How to fix it

    Publish /.well-known/api-catalog linking to your OpenAPI descriptions.

    1.⚡ Fix automatically with AIScan

    The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.

    2.Publish an API catalog (RFC 9727)
    # Add to your homepage HTTP response headers
    Link: </.well-known/api-catalog>; rel="api-catalog"
    
    # And serve a JSON document at /.well-known/api-catalog:
    {
      "links": [
        { "href": "/openapi.json", "rel": "service-desc", "type": "application/openapi+json" }
      ]
    }
    3.Verify

    After deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.

  • 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 found

    auth-server: 403, protected-resource: 403

    How to fix it

    Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.

    1.⚡ Fix automatically with AIScan

    The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.

    2.Publish OAuth discovery metadata

    If your API supports OAuth, serve RFC 8414 metadata at `/.well-known/oauth-authorization-server` and/or RFC 9728 at `/.well-known/oauth-protected-resource`.

    3.Verify

    After deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.

Share the result

Share as a social image

Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.

AIScan share card — www.klaviyo.com graded C

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.

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

AIScan.site grade C
HTML
<!-- AIScan.site agent-readiness badge -->
<a href="https://aiscan.site/?u=https%3A%2F%2Fwww.klaviyo.com%2Fuk%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade C (53/100) — AIScan.site">
  <img src="https://aiscan.site/api/public/badge.svg?score=53&grade=C&host=www.klaviyo.com" alt="AIScan.site Grade C — 53/100" width="240" height="64" loading="lazy" />
</a>
Markdown
[![AIScan.site Grade C — 53/100](https://aiscan.site/api/public/badge.svg?score=53&grade=C&host=www.klaviyo.com)](https://aiscan.site/?u=https%3A%2F%2Fwww.klaviyo.com%2Fuk%2F)

Track this over time

Coming soon: save sites, schedule re-scans, get email when something material changes. Standards land weekly — your tracker shouldn't be one-shot.

Free · No signup · ~20 seconds

Scan your own site

Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.

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