fightsignal.com
success
Claude Code
intent

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

16steps
67.6sduration
$1.1947cost
130,146tokens
22 steps6 reasoning steps10 searches
home
docs
docs
/features
search
docs
search
search
search
app.home
search
search
search
search
search
search
83%
on-site discovery
50%
reliability
50%
link following
path origin
  • previous resource50%
  • web search17%
  • prior knowledge33%
insight

The agent partially satisfied the task by assembling a coherent explanation of FightSignal's core offering (AI-powered UFC predictions using sentiment analysis and expert weighting), target audience, and claimed differentiation, but could not fulfill a critical part of the request: specific pricing information. The homepage and blog were the only content-bearing pages the agent could fetch; traditional navigation (pricing, features, about pages) returned 404s, forcing the agent to rely heavily on web search context and prior knowledge to fill gaps. The site proved difficult to navigate via standard URL guessing, with most key information either JavaScript-rendered on the homepage or inaccessible through typical SaaS page structures.

  • ›Step [1] (homepage) and [12] (blog) were the only directly fetched pages that returned 200 and contained actual content; both appear to be Next.js-rendered and returned truncated HTML, limiting what the agent could extract without executing JavaScript.
  • ›Steps [3], [4], [5] (attempts to fetch /pricing, /about, /features) all returned 404s, indicating the site does not publish these as static pages—a major navigation friction point for both humans and agents seeking standard SaaS information.
  • ›Step [13] (app.fightsignal.com) also returned truncated HTML, suggesting the app is client-rendered and not crawlable for content extraction.
  • ›The agent's final answer about pricing relied entirely on web search results (steps [10], [17]) and a promotional code mention found in search snippets—no actual pricing page was ever successfully fetched or cited as a source, confirming the information gap the agent identified.
  • ›Web searches (steps [7], [8], [15], [16], [18], [19], [20]) were routed back to the homepage repeatedly and to competitor sites (PicksWise, DRatings), but never surfaced a dedicated pricing or feature breakdown resource hosted on FightSignal's domain.
  • ›The agent's differentiation analysis (sentiment analysis, credibility weighting, visual interface) was assembled from fragmentary homepage marketing copy and prior knowledge, not from a formal features or comparison page; the site does not appear to publish this structured comparison.

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