adkin.agency
success
Claude Code
intent

What does adkin.agency do and who is it for? Explain it back to me.

14steps
63.2sduration
$0.5290cost
127,650tokens
23 steps9 reasoning steps3 searches
home
docs
/services
/services
docs
search
docs
home
search
/wp-json/wp/v2/pages
search
docs
/contact
/case-studies
100%
on-site discovery
64%
reliability
55%
link following
path origin
  • previous resource55%
  • prior knowledge45%
insight

The agent assembled a partial but incomplete understanding of Adkin Agency by fetching the homepage, services, and about pages directly. It successfully identified what they do (Perth-based web performance studio), who they serve (local businesses), and their core value proposition, but could not find pricing information—a key part of the task. The site's HTML was truncated in all responses, making it impossible to extract complete content; the agent worked around this limitation by relying on meta descriptions and prior knowledge rather than full page rendering.

  • ›All content-bearing fetches ([1], [4], [5], [20]) returned truncated HTML (4400 chars max) with only meta descriptions and head metadata visible—no body content was surfaced. The agent's final answer about services relied entirely on meta description snippets like 'Your website might look great and attract visitors, but is it ranking above your competitors?' rather than actual page body content.
  • ›The site does not publish pricing publicly—no /pricing page exists (404 in step [3]), no pricing tier information appears in meta tags or schema.org data, and the agent's web search ([7], [13], [17]) found nothing. The agent correctly flagged this as a gap but could not fulfill this part of the task.
  • ›The site is minimally structured for agent navigation: it has only 5 accessible pages (homepage, services, about, contact, plus 404s for pricing/blog/case-studies), and the agent had to guess URLs rather than discover them via sitemap or navigation links. The homepage truncation prevented the agent from seeing internal link structure that might have led to other content.
  • ›The agent's final response is heavily caveated with 'I couldn't find' statements for team composition, case studies, testimonials, and specific service packages—indicating the site does not expose these materials in a machine-readable or accessible form.
  • ›Prior knowledge sourcing (45%) and artifact reuse (55%) together account for most content; only 0% came from web search results, suggesting the site has poor external discoverability and the agent had to rely on direct URL guessing and meta data.

Help the next agent finish on adkin.agency

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 →