kappler.au
partial
Claude Code
intent

What does kappler.au do and who is it for? Explain it back to me.

23steps
102.2sduration
$1.3668cost
155,356tokens
29 steps6 reasoning steps13 searches
home
home
/work
docs
search
docs
/services
/contact
docs
/case-studies
search
search
/index.html
search
search
search
search
search
search
search
search
search
search
100%
on-site discovery
30%
reliability
20%
link following
path origin
  • previous resource20%
  • prior knowledge80%
insight

The agent gathered substantial information about Kappler's positioning, service tiers, and differentiation strategy, but could not find publicly accessible pricing information. The homepage (steps 1, 3, 20) was the only content-bearing resource; it contained meta description and schema data revealing core messaging (booking engines, headless platforms, conversion-first, senior-built), but the actual full page content was truncated in fetches, forcing the agent to rely heavily on prior knowledge and search snippets to construct a complete answer. The site is minimally navigable — a single-page application with no internal navigation structure, no dedicated pricing page, and no detailed case studies or technical documentation.

  • ›The homepage meta description (steps 1, 3, 20) was the primary content-bearing source, explicitly stating Kappler 'designs and builds booking engines, headless platforms and client portals' and emphasizing 'conversion-first' and 'senior-built.' This single snippet anchored the entire answer about what they do and who they serve.
  • ›All attempts to navigate to typical informational pages (/work, /about, /pricing, /services, /contact, /blog, /case-studies) returned 404 errors, signaling a single-page application with no conventional site structure. The agent had to rely on prior knowledge (80% of fetches) and search results (20%) rather than following on-site links.
  • ›Pricing information was entirely absent from accessible resources. The agent inferred a '$$$ ' price tier from schema data but could not retrieve actual figures. Search results repeatedly returned unrelated Kappler Inc. (chemical protective clothing) pricing pages, not kappler.au. The agent explicitly acknowledged this gap in the final response.
  • ›Service tier naming showed ambiguity—the agent references both 'Origin/Plus' and 'Evolution' in searches but could not definitively confirm which naming is current, revealing incomplete or outdated indexing of the site's content.
  • ›The site lacks agent-readable structured data for pricing, service comparison, or case studies. All meaningful differentiation claims ('own everything,' 'no vendor lock-in,' 'senior-built,' 'scope before building') were gleaned from the homepage meta description and prior knowledge, not from detailed pages or JSON-LD markup.
  • ›The agent was unable to verify specific technical stack, process timelines, or past work examples—information typically found on dedicated work/case-study pages or service detail sections, none of which exist or are discoverable on kappler.au.

Help the next agent finish on kappler.au

Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.

or talk to us about agent readiness →