Website-Bericht: 1 gemessene Seite. Gesamtbewertung: Mangelhaft.
Site-Score · amazon.com
Verrechnet den Origin und 1 gemessene Seite. Der Bericht unten behandelt allein die Origin-Seite.
Bringe die Ergebnisse zu den Menschen, die sie beheben können. Kopiere eine fertige Zusammenfassung für Slack, Teams oder die nächste Planung.
Dieser Bericht ist öffentlich. Dein Team kann ihn ohne Konto öffnen.
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.
No JSON-LD structured data found
Add a <script type="application/ld+json"> block in your HTML <head> with schema.org structured data describing your site, organization, or person.
Server-rendered content detected (794 words, 4985 chars of visible text)
Low text-to-markup ratio (0.6%)
A very low text-to-markup ratio is a typical SPA-shell symptom. Inline more content directly into the HTML response.
Only 2 semantic landmark(s) found
Use semantic HTML tags so AI agents can understand page structure: <header>, <nav>, <main>, <article>, <section>, <footer>.
No <h1> heading found
Add a single <h1> describing the page. Agents and search engines treat the H1 as the primary topic indicator.
Only 15/20 <img> tags have alt attributes
Add descriptive alt="" to every <img>. Agents use alt text to understand images they cannot process visually.
148/150 interactive elements have an accessible name
2/2 form controls are labelled
6 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 tables have no header cells
Without <th>, a table is a grid of strings: an agent reading a price table cannot tell which column is the price. Add header cells, with scope on anything non-trivial.
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.
18/20 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.
Method note: this reads markup, not a rendered accessibility tree
<title> length 35 chars: "Amazon.com. Spend less. Smile more."
Meta description is long (366 chars)
Trim to 70-160 characters; longer descriptions get truncated.
Canonical URL: https://www.amazon.com/
<html lang="en-us">
UTF-8 charset declared
Missing or incomplete viewport meta tag
Add <meta name="viewport" content="width=device-width, initial-scale=1">. Helps mobile agents render the page correctly.
Kann ein Agent die Seite überhaupt abrufen?
Response compressed with gzip
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 is on the large side (897.4 KB decompressed)
Consider trimming inlined payloads to reduce crawl cost.
Roughly 1,246 tokens of content in 218,683 tokens of response (99% markup)
An agent pays to receive the markup and then discards it. Serving Markdown on Accept negotiation is the direct fix.
Homepage responded in 684ms
A missing page redirects (301) 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 after 1 redirect
HEAD requests are refused (405)
HEAD lets a client confirm a URL exists, or check Last-Modified, without downloading the page. Refusing it turns every existence check into a full transfer.
Content-Type: text/html with charset
GPTBot probe failed: Server error (HTTP 503)
The request did not complete, so access for this crawler is unknown. Re-run the audit; if it persists, check origin health for this user agent.
ClaudeBot probe failed: Server error (HTTP 503)
The request did not complete, so access for this crawler is unknown. Re-run the audit; if it persists, check origin health for this user agent.
Bytespider probe failed: Server error (HTTP 503)
The request did not complete, so access for this crawler is unknown. Re-run the audit; if it persists, check origin health for this user agent.
CCBot probe failed: Server error (HTTP 503)
The request did not complete, so access for this crawler is unknown. Re-run the audit; if it persists, check origin health for this user agent.
OAI-SearchBot probe failed: Server error (HTTP 503)
The request did not complete, so access for this crawler is unknown. Re-run the audit; if it persists, check origin health for this user agent.
Claude-SearchBot probe failed: Server error (HTTP 503)
The request did not complete, so access for this crawler is unknown. Re-run the audit; if it persists, check origin health for this user agent.
PerplexityBot probe failed: Server error (HTTP 503)
The request did not complete, so access for this crawler is unknown. Re-run the audit; if it persists, check origin health for this user agent.
ChatGPT-User probe failed: Server error (HTTP 503)
The request did not complete, so access for this crawler is unknown. Re-run the audit; if it persists, check origin health for this user agent.
8 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.
Site is served over HTTPS
HTTP requests redirect to HTTPS
HSTS max-age=47474747
HSTS includes subdomains
HSTS preload-eligible
Homepage is indexable
Google-Extended is disallowed, but this page is still eligible for AI Overviews
Google-Extended governs Gemini training and grounding in Gemini Apps and Vertex AI. AI Overviews and AI Mode follow Googlebot and the snippet directives instead. If the intent was to stay out of AI Overviews, use nosnippet or max-snippet. If the intent was to opt out of training, this is already correct.
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.
/robots.txt exists
10/12 core AI crawlers configured
Add explicit User-agent entries for the missing crawlers with Allow: / for each one.
33 AI crawler(s) explicitly blocked
These crawlers have "Disallow: /" rules. If you want AI agents to access your site, change to "Allow: /" for each blocked crawler.
8 assistant search crawler(s) blocked — your site cannot be cited by those assistants
Search crawlers build the index an assistant cites from; they are separate from the training crawlers. If the intent was to opt out of training only, allow these and block the training tokens instead.
17 training crawler(s) blocked — recorded as a deliberate policy choice
3 user-triggered fetcher(s) blocked in robots.txt that may ignore it
These clients fetch a page because a person asked for that URL, and their vendors document that robots.txt may not apply. Enforce at the edge if the block must hold.
5 robots.txt rule(s) target a retired or non-existent crawler token
These rules have no effect. Remove them so the file reflects your actual policy.
No Sitemap directive found
Add a Sitemap directive to your robots.txt: Sitemap: https://your-site.com/sitemap.xml
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.
33/57 known AI crawlers have explicit rules
No sitemap found
Publish an XML sitemap at /sitemap.xml and reference it from robots.txt with: Sitemap: https://your-site.com/sitemap.xml
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:url, og:type
Add these meta tags: <meta property="og:title" content="...">, <meta property="og:url" content="...">, <meta property="og:type" content="...">.
Twitter Card required tags missing: twitter:card, twitter:title, twitter:description
Add these meta tags: <meta name="twitter:card" content="...">, <meta name="twitter:title" content="...">, <meta name="twitter:description" content="...">.
6/7 security headers present
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.
Was kann ein Agent aufrufen?
/.well-known/agent-card.json not found
This site offers something an agent could call, but nothing tells an agent what. Publish an A2A Agent Card at /.well-known/agent-card.json. A minimal 1.0 card needs name, description, version, capabilities, supportedInterfaces, defaultInputModes, defaultOutputModes and skills. Spec: https://a2a-protocol.org/latest/specification/
API surface present but no machine-readable description found
The API exists; nothing describes it in a form an agent can read, so using it requires a human to read your documentation first. Serve an OpenAPI description at /openapi.json and advertise it with Link: </openapi.json>; rel="service-desc". For several APIs, publish an RFC 9727 catalog.
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.
No Agent Skills published
This site has documentation, so it has procedures worth teaching. A skill is a SKILL.md an agent installs and follows: setup steps, argument shapes, the mistakes to avoid. Publish one per task at /.well-known/agent-skills/{name}/SKILL.md and list them in /.well-known/agent-skills/index.json.
Site sells something but publishes no agent-readable commerce profile
Publish a Universal Commerce Protocol profile at /.well-known/ucp so an agent can find your catalog, cart and checkout without a human. Note that the alternatives are not discoverable by design: the OpenAI and Stripe Agentic Commerce Protocol defines no manifest, and AP2 advertises itself through an A2A card extension.
2 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 MCP server — MCP discovery does not apply to this site
Nothing on this site requires authorization — auth discovery does not apply
Welche Nutzungsrechte sind erklärt?
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.
/.well-known/security.txt exists
Required field "Contact" present
Required field "Expires" missing (RFC 9116)
Add "Expires:" to your security.txt. Use an ISO 8601 date, e.g., Expires: 2026-12-31T23:59:59.000Z
2/5 optional fields present
Vollständige Berichte, priorisierte Korrekturen und Überwachung helfen deinem Team, Verbesserungen über das nächste Release hinaus zu erhalten.