headspace.com
This is how AI agents (not browsers) experience headspace.com. The score weights five categories of machine-readability; the ticks on the arc are the 31 individual checks behind it.
Top fixes
Checks tagged “emerging” are 2026 agent-protocol standards most of the web hasn’t adopted yet — adopting early is an edge, not a defect.
No HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.
Fix: Emit `Link:` headers for canonical, alternate-language, and describedby relations. Agents that fetch HEAD-only or stream-render rely on these.
Visible text is 1.4% of HTML weight (7533/556963 bytes). Low. Markup may be crowding out agent-usable text.
Fix: Heavy ad or navigation markup crowds out agent-usable text. Aim for a text-to-DOM ratio above 15%.
Browser pass unavailable; HTML looks like a JS-shell (e.g. #__next / #root). Likely JS-dependent.
Fix · Next.js: Render primary content on the server: use Server Components (App Router) or getServerSideProps/SSG (Pages Router). Avoid fetching above-the-fold content in a client useEffect, since agents don’t run it.
Heading issues: no <h1>; 2 skipped level(s).
Fix: Use a single H1 and avoid skipping heading levels (H1 → H3).
Consent modal detected (cookielaw.org); content still visible. Verify the modal does not block first-paint for screenshot agents.
Fix: Defer cookie consent overlay until after content is visible, or render behind the primary content. Agents without JS or with ad-blocking profiles see a blank page otherwise.
No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.
Fix: Add `Content-Signal:` directives to your robots.txt. This is the emerging standard (Cloudflare-driven) for declaring fine-grained AI usage policy beyond a binary allow/disallow.
Get it in your inbox now — and a heads-up whenever headspace.com’s agent-readiness score changes. Free, unsubscribe anytime.
This scan shows whether an agent can read the site. One free probe asks a real assistant a real buying question and records who it cited.
This graded your homepage. Your pricing, docs, and checkout live on other pages — the ones assistants actually quote when they recommend you — and a 73/100 here means agents are already missing things on the page you polish most. The $29 Deep Scan audits the whole site against all 31 checks, then emails a PDF with every failing check and its exact fix, ranked by what costs you the most visibility. One-time, delivered in minutes, no subscription.
Right now, only you know this score. Your buyers ask AI before they buy — certification is how you show them, and anyone comparing you to a competitor, that assistants can actually read, quote, and use your site.
- A public verification URL you can drop into a sales deck, a procurement questionnaire, or a partner review — anyone can check it, dated and signed.
- An embeddable badge for your site — the visible version of a property competitors can’t claim without earning the score.
- Weekly re-checks for a full year. A deploy that breaks agent access gets caught before it costs you recommendations — and before the certificate would lapse.
Sites under 70 can’t buy this at any price — that’s what makes displaying it mean something.
Certify headspace.com — $199/year →What the agent receives
Show your score
Embed this badge on your site. It links back to this live scan and updates on every rescan.
<a href="https://agentspeed.com/scan/headspace.com"><img src="https://agentspeed.com/badge/headspace.com" alt="AgentSpeed agent-readiness score" height="56"></a>Track this score
Get this report by email, then a heads-up when headspace.com’s agent-readiness actually changes — a check regressing, or the composite dropping.
Two things never trigger an email: a score change caused by us publishing a new rubric, because that is a different instrument rather than a change to your site, and movement explained only by timing-derived checks, which shift run to run on a site nobody touched.
Want it on your own schedule, with Slack or a webhook instead of email? Score-drift monitoring is on every paid plan.
This score says whether an AI agent could read headspace.com. AI traffic analytics says whether one actually came — and which pages turned it away.
Full breakdown
Running AI agents of your own? AgentSpeed also monitors them in production — every run, its latency, cost, and failures, with alerts when something breaks. Free for 10,000 events a month, no credit card.