AX Rush

KI-Bereitschaft von grovemade.com

Website-Bericht: 1 gemessene Seite. Gesamtbewertung: Befriedigend.

Site-Score · grovemade.com

Verrechnet den Origin und 1 gemessene Seite. Der Bericht unten behandelt allein die Origin-Seite.

grovemade.com

Mangelhaft · 35 bestandene Prüfungen, 44 Warnungen, 7 Fehlschläge · 8,2s

Teile diesen Bericht mit deinem Technikteam

Bringe die Ergebnisse zu den Menschen, die sie beheben können. Kopiere eine fertige Zusammenfassung für Slack, Teams oder die nächste Planung.

E-Mail

Dieser Bericht ist öffentlich. Dein Team kann ihn ohne Konto öffnen.

Inhalt

71/100

Gibt es Substanz, die ein Agent lesen kann?

  • Homepage does not serve Markdown via content negotiation

    Serve a Markdown representation of your pages when agents request "Accept: text/markdown". Agents like Claude Code and Cursor ask for it, and Markdown cuts token usage by roughly 80% against HTML. Cloudflare ("Markdown for Agents") and Vercel can enable this without code changes.

  • No <link rel="alternate" type="text/markdown"> fallback found on the homepage

    If you cannot enable content negotiation, advertise a Markdown version with <link rel="alternate" type="text/markdown" href="/index.md"> so agents can discover it.

  • 162/162 interactive elements have an accessible name

  • 11 link(s) lead nowhere without JavaScript

    A link with no destination cannot be followed by a fetch-only agent and cannot be opened in a new tab by a browsing one. Give it a real href, or make it a <button> if it is an action rather than a destination.

  • 1/1 iframes have no title

    An untitled frame is an opaque region. A title tells an agent whether it is worth entering.

  • Heading hierarchy skips 1 level(s)

    Agents outline a page from its headings. A skipped level puts a section under the wrong parent, so a summary attributes it to the wrong topic.

  • 161/163 images, frames or videos have no declared dimensions

    Undeclared dimensions shift the layout as media loads. An agent working from a screenshot clicks where the button was a moment ago. Set width and height, or aspect-ratio.

  • No lang attribute on <html>

    Agents route, translate and pick a voice from this. Add lang="en" or whichever applies.

  • Method note: this reads markup, not a rendered accessibility tree

  • 1 JSON-LD block(s) found

  • @context references schema.org

  • No @graph array (single-entity only)

    Use an @graph array to define multiple entities in one JSON-LD block: { "@context": "https://schema.org", "@graph": [...] }

  • Only 1 key type found: Organization

    Add more entity types to your @graph. AI agents use these to understand site structure. Common types: Person, Organization, WebSite, WebPage.

  • No BreadcrumbList found

    Add a BreadcrumbList entity to help AI agents understand your site navigation hierarchy.

  • No author declared in structured data

    An assistant deciding whether to cite a page weighs where it came from. Add author as a Person or Organization, not a bare string.

  • 3 sameAs link(s) tie your entity to external identifiers

  • No dateModified or datePublished in structured data

    Assistants weigh recency when they answer time-sensitive questions, and a page with no date cannot be weighed at all. Add dateModified to anything that changes.

  • Server-rendered content detected (2137 words, 13025 chars of visible text)

  • Markup-heavy page (text is 3.3% of structural markup)

    The visible text clears the content thresholds, so agents can read this page. Trimming wrapper markup would still make it cheaper to consume.

  • Only 1 semantic landmark(s) found

    Use semantic HTML tags so AI agents can understand page structure: <header>, <nav>, <main>, <article>, <section>, <footer>.

  • 2 <h1> headings found (recommend exactly 1)

    Use a single <h1> per page to clearly mark the primary topic. Demote secondary headings to <h2>+.

  • 162/164 <img> tags have alt attributes

  • <title> length 62 chars: "Modern Desk Organization &amp; Office Accessories | Grovemade®"

  • Meta description length 111 chars

  • Canonical URL: https://grovemade.com/

  • <html lang="..."> is missing

    Set the document language: <html lang="en">. Multilingual agents rely on this to pick the right summarization model and avoid mixed-language ranking.

  • UTF-8 charset declared

  • Viewport meta present: "width=device-width"

Zugang

83/100

Kann ein Agent die Seite überhaupt abrufen?

  • Response compressed with Brotli (br)

  • No ETag or Last-Modified header — conditional requests unsupported

    Send an ETag or Last-Modified header so crawlers can revalidate with If-None-Match / If-Modified-Since and receive a cheap 304 Not Modified instead of the full body.

  • Homepage size is reasonable (423.0 KB decompressed)

  • Roughly 3,256 tokens of content in 108,267 tokens of response (97% markup)

    An agent pays to receive the markup and then discards it. Serving Markdown on Accept negotiation is the direct fix.

  • Homepage responded in 285ms

  • GPTBot receives a Cloudflare challenge instead of the page

    Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.

  • ClaudeBot receives a Cloudflare challenge instead of the page

    Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.

  • Meta-ExternalAgent receives a Cloudflare challenge instead of the page

    Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.

  • Amazonbot receives a Cloudflare challenge instead of the page

    Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.

  • Bytespider receives a Cloudflare challenge instead of the page

    Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.

  • CCBot receives a Cloudflare challenge instead of the page

    Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.

  • OAI-SearchBot receives a Cloudflare challenge instead of the page

    Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.

  • Claude-SearchBot receives a Cloudflare challenge instead of the page

    Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.

  • PerplexityBot receives a Cloudflare challenge instead of the page

    Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.

  • ChatGPT-User receives a Cloudflare challenge instead of the page

    Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.

  • 10 crawler probe(s) could not be settled from outside

    ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.

  • A missing page redirects (308) instead of returning 404

    A redirect on a nonexistent path hides the error. Return 404 or 410 so a client can tell the difference.

  • Homepage answers without a redirect

  • HEAD requests are supported

  • Content-Type: text/html with charset

  • Site is served over HTTPS

  • HTTP requests redirect to HTTPS

  • No Strict-Transport-Security header

    Add: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload. This locks browsers and many agents to HTTPS for 1 year.

  • Homepage is indexable

  • No directive restricts how AI assistants may use this page

Auffindbarkeit

49/100

Findet ein Agent, was Sie veröffentlichen?

  • /llms.txt not found

    Create a /llms.txt file at your site root following the llmstxt.org specification. It should be a Markdown file starting with "# Your Site Name" and include a description, sections, and links.

  • No AI meta tags (ai:*) found

    Add AI meta tags to your HTML <head>: <meta name="ai:summary" content="Brief description">, <meta name="ai:content_type" content="website">, <meta name="ai:author" content="Your Name">.

  • No rel="alternate" link to llms.txt in HTML

    Add to your <head>: <link rel="alternate" type="text/plain" href="/llms.txt" title="LLM-optimized content">

  • No rel="alternate" link to the Agent Card in HTML

    Add to your <head>: <link rel="alternate" type="application/json" href="/.well-known/agent-card.json" title="Agent Card">

  • No rel="me" identity links found

    Add rel="me" links to verify your identity across platforms: <link rel="me" href="https://github.com/yourname">, <link rel="me" href="https://twitter.com/yourname">.

  • OpenGraph required tags missing: og:title, og:description, og:url, og:type

    Add these meta tags: <meta property="og:title" content="...">, <meta property="og:description" content="...">, <meta property="og:url" content="...">, <meta property="og:type" content="...">.

  • No Twitter Card meta tags found

    Add twitter:card, twitter:title, twitter:description, and twitter:image so X / Threads / Bluesky / Discord agents render link previews correctly.

  • /robots.txt exists

  • No core AI crawlers explicitly configured

    Add User-agent entries for core AI crawlers in your robots.txt. For each crawler, add: User-agent: <name> followed by Allow: / on the next line.

  • Sitemap directive present

  • No Content-Signal directive found (optional)

    Declare how crawlers may use your content after access with the Content Signals Policy, e.g.: Content-Signal: search=yes, ai-train=no. Known signals: search, ai-input, ai-train, plus the optional use=immediate|reference|full. Generate yours at contentsignals.org.

  • 0/57 known AI crawlers have explicit rules

    Add explicit User-agent entries for more AI crawlers to maximize discoverability.

  • Missing critical header: Strict-Transport-Security

    Add the Strict-Transport-Security response header to your server configuration. This is a critical security header.

  • Missing critical header: X-Content-Type-Options

    Add the X-Content-Type-Options response header to your server configuration. This is a critical security header.

  • Only 0/7 security headers present

    Add security headers like Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy to your server response.

  • No Link header for AI discovery (llms.txt, Agent Card)

    Add a Link response header pointing to your AI discovery files: Link: </llms.txt>; rel="alternate"; type="text/plain", </.well-known/agent-card.json>; rel="alternate"; type="application/json"

  • No machine-readable discovery relations beyond llms.txt and the Agent Card

    Advertise what you publish with Link relations so agents stop guessing paths. Add the ones that apply, for example: Link: </llms.txt>; rel="describedby", </.well-known/api-catalog>; rel="api-catalog". Informational in 3.x: this does not affect your score.

  • Sitemap located: https://grovemade.com/sitemap.xml

  • Content-Type is XML (application/xml)

  • 340 URL(s) declared

  • 100% of URLs have <lastmod>

  • Newest <lastmod> is recent (3 day(s) ago)

Protokolle

50/100

Was kann ein Agent aufrufen?

  • No agent resource catalog found

    A catalog is one document listing everything an agent can call here — agent cards, MCP servers, APIs, skills — so a client stops probing four conventions to find out. Worth publishing once you have more than one of those. Informational: both ai-catalog.json and ard.json are still drafts, so this never affects your score.

  • 12 form(s) on the page, none declared as agent tools

    A declared form is called by an agent rather than driven pixel by pixel. Add toolname and tooldescription to the forms worth automating — search, filter, subscribe — and toolparamdescription to each field.

  • No agent-facing surface — an Agent Card does not apply to this site

  • No API surface — API discovery does not apply to this site

  • No MCP server — MCP discovery does not apply to this site

  • No developer-facing surface — skills do not apply to this site

  • No commerce surface — agentic-commerce discovery does not apply to this site

  • Nothing on this site requires authorization — auth discovery does not apply

Richtlinien

18/100

Welche Nutzungsrechte sind erklärt?

  • /.well-known/security.txt not found

    Create a /.well-known/security.txt file per RFC 9116. At minimum, include Contact: and Expires: fields. See https://securitytxt.org/ for a generator.

  • No RSL license discovery found

    Declare machine-readable licensing terms for your content with Really Simple Licensing. Add to robots.txt: License: https://your-site.com/license.xml — then publish the RSL document. See https://rslstandard.org.

  • No machine-readable usage policy declared

    State your terms where they can be read without a lawyer. The lowest-effort option is a Content-Signal line in robots.txt: Content-Signal: search=yes, ai-input=yes, ai-train=no. Absence is neutral, not permission — but it also gives you nothing to point at.

Technische Details

Engine
axrush-engine@6.0.0
Gescannt
10.09.2026, 19:01:41 UTC
Dauer
8.217 ms
Ausgeführte Checks
26

Aus diesem Bericht werden dauerhafte Verbesserungen

Vollständige Berichte, priorisierte Korrekturen und Überwachung helfen deinem Team, Verbesserungen über das nächste Release hinaus zu erhalten.

Diesen Bericht über die API oder den MCP-Server lesen