Website-Bericht: 1 gemessene Seite. Gesamtbewertung: Gut.
Site-Score · whitehouse.gov
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.
176/176 interactive elements have an accessible name
3/3 form controls are labelled
14 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.
Method note: this reads markup, not a rendered accessibility tree
Server-rendered content detected (710 words, 4869 chars of visible text)
Low text-to-markup ratio (1.6%)
A very low text-to-markup ratio is a typical SPA-shell symptom. Inline more content directly into the HTML response.
Semantic landmarks present (main, header, footer, nav)
<h1> is empty
Add meaningful text inside your <h1> element so agents can identify the page topic.
23/23 <img> tags have alt attributes
<title> is too short (15 chars): "The White House"
Lengthen the title to 20-70 characters with a clear topic indicator.
Meta description is long (251 chars)
Trim to 70-160 characters; longer descriptions get truncated.
Canonical URL: https://www.whitehouse.gov/
<html lang="en-US">
UTF-8 charset declared
Viewport meta present: "width=device-width, initial-scale=1"
2 JSON-LD block(s) found
@context references schema.org
@graph array present (multi-entity structured data)
Key types found: Organization, WebSite, WebPage
BreadcrumbList present
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.
4 sameAs link(s) tie your entity to external identifiers
Content last dated 2026-07-22 (44 days ago)
Structured-data headings appear in the visible text
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 (292.9 KB decompressed)
Roughly 1,217 tokens of content in 74,987 tokens of response (98% markup)
An agent pays to receive the markup and then discards it. Serving Markdown on Accept negotiation is the direct fix.
Homepage responded in 27ms
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 supported
Content-Type: text/html with charset
ClaudeBot is rate limited on a single request
One probe should not hit a rate limit. A limit this tight will stall any crawl. Always answer 429 with a Retry-After header so well-behaved crawlers back off correctly instead of giving up.
Bytespider is rate limited on a single request
One probe should not hit a rate limit. A limit this tight will stall any crawl. Always answer 429 with a Retry-After header so well-behaved crawlers back off correctly instead of giving up.
2 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=31536000
HSTS includes subdomains
HSTS preload-eligible
Homepage is indexable
max-snippet:-1 — no limit on snippet length
No directive restricts how AI assistants may use this page
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 present (og:title, og:description, og:url, og:type)
Twitter Card required tags present (twitter:card, twitter:title, twitter:description)
/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.
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.
Sitemap located: https://www.whitehouse.gov/sitemap_index.xml
Content-Type is XML (text/xml)
Sitemap-index references 23 child sitemap(s)
3/3 sample child sitemap(s) reachable
Sample yielded 2093 URL(s) across 3 child(ren)
Newest <lastmod> is recent (0 day(s) ago)
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.
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 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
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.
Vollständige Berichte, priorisierte Korrekturen und Überwachung helfen deinem Team, Verbesserungen über das nächste Release hinaus zu erhalten.