saveonpropfirms.com
success
Claude Code
intent

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

16steps
64.1sduration
$0.7288cost
186,262tokens
25 steps9 reasoning steps4 searches
home
docs
docs
/comparisons
docs
/prop-firms
/faq
/prop-firms/funded-next
search
docs
/review/saveonpropfirm…
search
search
/promos
/giveaways
search
67%
on-site discovery
50%
reliability
25%
link following
path origin
  • previous resource25%
  • web search33%
  • prior knowledge42%
insight

The agent successfully assembled a comprehensive explanation of SaveOnPropFirms by combining direct site fetches with web search context. The homepage [1] and promo page [20] provided surface-level structure; the blog article [14] explained the underlying prop firm concept; and the giveaways page [21] revealed additional value props. However, the site's heavy JavaScript rendering prevented the agent from accessing the core interactive comparison table and specific discount amounts, forcing reliance on prior knowledge and search results to fill critical gaps about pricing and differentiation.

  • ›The homepage [1] and promo page [20] loaded successfully but returned only HTML scaffolding with no visible content data—the comparison table and discount details are JavaScript-rendered and not machine-readable in the fetched responses.
  • ›The blog article [14] (what-is-a-prop-firm) was the only fully content-bearing page, providing explanation of prop firm mechanics but not SaveOnPropFirms' own value proposition or business model.
  • ›The agent had to rely on web search results and prior knowledge to answer critical questions about pricing model (affiliate-based), discount amounts (20-90%), and competitive differentiation—none of which appeared in the fetched HTML.
  • ›Individual prop firm detail pages returned 404s or error states [11], indicating the site's URL structure is incomplete or dynamically routed in ways the agent could not discover through direct navigation.
  • ›The site is not agent-ready: core product information (comparison data, promo codes, specific discounts) exists only in client-rendered JavaScript, making it invisible to static fetches. The agent successfully worked around this via search supplementation, but had to acknowledge what it 'couldn't find' in multiple sections of the final answer.

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