brownthomas.com
success
Claude Code
intent

What does brownthomas.com do and who is it for? Explain it back to me.

18steps
66.5sduration
$0.8936cost
216,270tokens
28 steps10 reasoning steps5 searches
home
/en_ie/about-us
/en_ie/customer-service
/en_ie/footer
/en_ie/shop/women
/en_ie/help
/help/shipping-delivery
search
search
/en_ie/shopping-online
/sale
/en_ie/brands
search
/ni/inner-circle-by-br…
docs
search
/customer-service/disp…
search
69%
on-site discovery
31%
reliability
38%
link following
path origin
  • previous resource38%
  • web search31%
  • prior knowledge31%
insight

The agent assembled a comprehensive overview of Brown Thomas by combining homepage fetch, successful retrieval of the Inner Circle membership page, dispatch/delivery page, and multiple web searches about the brand and its benefits. The site proved largely inaccessible via direct navigation (most /en_ie/ paths returned 410 errors), forcing heavy reliance on search results and prior knowledge; the agent worked around this by guessing alternate URL patterns and supplementing with external sources, ultimately satisfying the task despite poor direct discoverability.

  • ›Step [1] (homepage) and [15] (sale page, 200) were the only successful direct fetches of main site URLs; all /en_ie/ paths returned 410 errors, indicating routing or locale issues that blocked standard navigation.
  • ›Step [21] (Inner Circle membership page) and [26] (dispatch/delivery page) succeeded and contained concrete pricing (€350/year membership, free delivery benefits) and service details—these were essential to answering the 'how it's priced' and 'what's different' questions.
  • ›Steps [11], [12], [18], [24] (web searches) supplied most of the qualitative positioning, heritage context, and competitive framing; the site itself does not expose these positioning claims in a machine-readable way.
  • ›The agent could not access product listings, specific shipping costs, or return policy details because the site is JavaScript-rendered and direct help center pages were blocked (step [23] returned Cloudflare 403), leaving gaps in transactional and operational details.
  • ›The agent's final response is well-structured but built from fragments: homepage metadata (inferred from truncated fetches), search result titles and links, two successfully fetched content pages, and prior knowledge about the parent company (Selfridges Group). This is a 'heavy bridge' outcome because the site's own infrastructure did not readily serve the discovery intent.

Help the next agent finish on brownthomas.com

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 →