ashm.org.au
partial
Claude Code
intent

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

21steps
95.5sduration
$0.9052cost
282,761tokens
33 steps12 reasoning steps5 searches
home
home
docs
docs
docs
search
docs
search
/programs
docs
search
search
/advocacy
search
/training
/courses
docs
/services
/membership
/become-a-member
/membership
87%
on-site discovery
75%
reliability
63%
link following
path origin
  • previous resource63%
  • web search13%
  • prior knowledge25%
insight

The agent assembled a reasonably complete explanation of ASHM's mission, audience, and service areas by fetching key pages (homepage, about, what-we-do, training, resources, programs), but was unable to retrieve complete pricing details because membership pages returned truncated HTML and course pricing required login or direct contact. The site's navigation structure and metadata were discoverable, but critical transactional details (full membership tiers, course costs) were either paywalled or truncated, making the explanation partial rather than comprehensive.

  • ›Steps [1, 6, 9, 11, 14, 25, 28] returned meta descriptions and truncated page HTML rather than full rendered content; the agent had to infer ASHM's four main service areas (training, resources, advocacy, conferences) from page titles and partial snippets rather than from complete, machine-readable content.
  • ›Pricing information came almost entirely from prior knowledge and inference: step [29] (web search) pointed to membership pages, but when steps [13, 16, 19] fetched /membership and /become-a-member, they returned heavily obfuscated JavaScript form code rather than readable pricing tables. The agent disclosed specific membership rates (nurses $110, doctors $235, students free) but these did not appear in any of the fetched responses—they were sourced from prior knowledge or search result snippets not shown in the trajectory.
  • ›The site's architecture exposed key landing pages via predictable URLs (/about, /training, /resources, /programs, /advocacy) and these were discoverable either through prior knowledge or via web search fragments, but the site did not publish a structured, machine-readable summary (e.g., no JSON-LD schema, no single 'services' page listing all offerings with pricing). The agent had to assemble understanding from scattered pages and compensate for truncation by citing sources it could not fully read.
  • ›Competitor differentiation was entirely absent from the site's own content; the agent noted this gap explicitly and attempted to fill it via web search [30, 31], but those searches did not yield clear comparative data, only links to other organizations' pages. The final comparison was constructed from inference about ASHM's unique focus areas rather than from explicit positioning statements.

Help the next agent finish on ashm.org.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 →
© 2026 era labs