ahrweb.de
Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
ahrweb.de
Preparing the stored Is Agentic score
ahrweb.de
These checks describe whether an ordinary agent can enter, read, and operate the public site.
Agents can reach the site
Crawler access and bot defenses.
Core content is available
Useful content remains accessible without a fragile browser-only path.
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
Controls are understandable
Forms and interactive controls expose usable names and structure.
The public website is always evaluated. Optional surfaces appear when the scan finds positive evidence that they apply.
Strong
Weighted across 16 applicable checks
Critical access gaps come first, followed by other applicable readiness gaps.
Make sure your own domain ranks in the top results when people search your brand together with your main product (for example "Acme payments API"). If it does not, your brand may be too generic, conflict with a more established term, or not yet indexed. Strengthen it by describing your main product clearly in your homepage title and headings, earning press mentions that link to your domain, and avoiding redirect chains that mask your main domain in search results.
Checks are grouped by relevance for Business sites.
11242 chars, semantic headings (1 H1 + 7 H2s + 10 H3s), 35.5% content ratio
Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
No meta-refresh stubs, JavaScript-redirect stubs, or cross-domain hops across 6 checked pages
All 5 sampled pages are publicly readable (5 with substantive content)
Canonical URL serves text/markdown and text/html via Accept negotiation with Vary: Accept
Nonexistent paths return HTTP 404 with markdown guidance for agents - the strongest 404 contract
ahrweb.de was not in the top 10 for "ahrweb" (searched your brand name alone: no main product term from your homepage qualified)
How to pass
Make sure your own domain ranks in the top results when people search your brand together with your main product (for example "Acme payments API"). If it does not, your brand may be too generic, conflict with a more established term, or not yet indexed. Strengthen it by describing your main product clearly in your homepage title and headings, earning press mentions that link to your domain, and avoiding redirect chains that mask your main domain in search results.
No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search.
Valid sitemap found at https://ahrweb.de/sitemap.xml with 41 entries
Rich JSON-LD identity: LocalBusiness with name, description, url, and sameAs/logo/address (1 block)
All metadata signals present: canonical URL, lang="de-DE", og:image, og:type
Organization schema complete with contactPoint and address
All trust anchor pages verified: About, Contact, Privacy
All 7 measured pages fit an agent context budget (largest ~3K tokens)
ARD catalog valid at /.well-known/ai-catalog.json (spec 1.0) - 3/3 entries - served at the legacy path; the canonical ARD path is /.well-known/ard.json (ARD v0.91)
Valid AI Catalog at /.well-known/ai-catalog.json (spec 1.0) - 3/3 entries
All 3 entries valid with domain-anchored urn:air identifiers (catalog at /.well-known/ai-catalog.json)
Rich agent mode view at ?mode=agent with 4 agent signals and navigation links
RFC 8288 Link header advertises: sitemap, describedby
Full markdown fallback support. Homepage (https://ahrweb.de/index.md) and all 3 sampled content pages return markdown: https://ahrweb.de/ahrweb-hilft.md, https://ahrweb.de/impressum-handwerksbetrieb.md, https://ahrweb.de/ueber.md
100% of 41 sampled sitemap entries carry lastmod; newest is 1 day(s) old
Found the llms.txt at https://ahrweb.de/llms.txt.
The llms.txt is well-formatted with markdown links, but at 71,784 characters it exceeds the 30,000-character recommendation for a navigation index.
How to pass
Format your llms.txt as a navigation index: start with a markdown heading, include markdown links to deeper resources, and keep it under 30,000 characters. If you have more to say, move long-form content into /llms-full.txt or per-section files (e.g. /docs/llms.txt, /api/llms.txt) and link to them from the main index.
Pricing structured data (schema.org/Offer) found
When-to-use guidance found in llms.txt
Rich schema vocabulary: ProfessionalService, LocalBusiness, Service, FAQPage
All 5 probed llms.txt links resolve to real content
Markdown alternate advertised and verified: https://ahrweb.de/index.md serves markdown
Frontmatter with title + description, canonical, and last-updated on /index.md
Code fences balanced across 1 markdown document
Path-suffix markdown docs served with text/markdown content-type: /index.md
Imperative WebMCP API detected (document.modelContext.registerTool in script bundle /assets/webmcp.js).
Server HTML is a well-structured document (main=true, landmarks=4/4, h1=1, maxHeadingSkip=1).
115 native controls, 0 non-native div-soup affordances (100% native).
115/115 interactive elements have a computable accessible name (100%).
16/16 form controls have an associated label (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does ahrweb.de do and who is it for? Explain it back to me.
Sign me up for Vercel product updates and marketing emails.
Unsubscribe anytime. Privacy Notice
Source: Ora API
What does ahrweb.de do and who is it for? Explain it back to me.
3 steps1 reasoning step
The agent successfully assembled a comprehensive overview of ahrweb's offerings, pricing, and positioning by fetching the homepage and llms.txt file, but encountered multiple internally inconsistent claims (VAT status, text inclusion, hosting costs, care-plan tiers) that suggest the site publishes conflicting or incomplete information rather than the agent failing to find clarity.