goodrec.com
success
Claude Code
intent

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

13steps
51.4sduration
$0.7158cost
131,116tokens
16 steps3 reasoning steps4 searches
home
docs
/sports
docs
/soccer-leagues
search
/us/app/goodrec/id1510…
docs
search
/organization/goodrec-…
search
search
/reviews
78%
on-site discovery
78%
reliability
33%
link following
path origin
  • previous resource33%
  • web search22%
  • prior knowledge44%
insight

The agent successfully assembled a coherent overview of GoodRec's purpose, target audience, pricing model, and competitive positioning, but had to work around a missing pricing page and rely heavily on prior knowledge and web search to fill gaps. The website itself was sparse on operational details—homepage and category pages (soccer, sports, reviews) provided brand messaging and basic feature descriptions, while the actual pricing structure and organizer-facing features had to be inferred from app store listings and external articles. The agent grounded its final answer in website content where available but acknowledged significant information gaps that the site did not clearly publish.

  • ›The homepage [1] and category pages [3, 8, 9] provided brand messaging and game counts but did not expose pricing, business model clarity, or organizer tools—forcing the agent to note these as 'confusing/missing information'.
  • ›The /pricing URL returned a 404 [2], so the agent had to infer the pay-per-game model ($9.99–$14.99) from app store listings [11] and external articles discovered via web search, not from the site itself.
  • ›Competitive differentiation required external research [10, 14] because the website does not position GoodRec against alternatives or explain what makes it distinct—the agent synthesized this by comparing product positioning across multiple sources outside the domain.
  • ›The site's navigation and structure are clean enough for discovery (sports, leagues, reviews pages exist and load), but critical business information (pricing, organizer features, subscription tiers) is either absent or poorly surfaced, requiring heavy bridge work via web search and prior knowledge (56% of fetches came from search or prior knowledge, only 44% from direct domain navigation).

Help the next agent finish on goodrec.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 →