ora
onelocal.com
partial
Claude Code
intent

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

7steps
28.8sduration
$0.0596cost
54,473tokens
11 steps4 reasoning steps1 search
home
docs
/features
/how-it-works
docs
search
/plans
83%
on-site discovery
67%
reliability
33%
link following
path origin
  • previous resource33%
  • web search17%
  • prior knowledge50%
insight

The agent gathered a partial but coherent picture of OneLocal's business model, target audience, and positioning by combining content from the homepage, how-it-works page, about page, and pricing page. However, the task was only partially satisfied because the site's pricing page—critical to the assignment—uses client-side rendering that obscured the actual dollar amounts; the agent had to acknowledge this gap rather than deliver concrete pricing information. The site's Framer-based architecture and sparse URL structure (with /pricing and /features returning 404s) made direct navigation difficult, forcing the agent to rely on guesswork and web search to locate the correct paths.

  • ›Step [1] (homepage) and step [5] (how-it-works) provided high-level positioning: all-in-one platform for local service businesses combining reviews, ads, messaging, and presence management. These steps anchored the core value proposition.
  • ›Step [7] (about page) reinforced the target market and mentioned the support-specialist differentiation, but did not contain detailed feature or pricing data.
  • ›Step [9] (pricing page) was found only after web search located the correct URL (/plans, not /pricing); the page loaded but the actual pricing tiers and dollar amounts were not extractable because they are rendered client-side. The agent correctly identified this as a confusing gap and flagged it in the final response.
  • ›Steps [3] and [4] revealed that predictable URLs (/pricing, /features) return 404s, indicating the site publishes content at non-standard paths or via a single-page app architecture. This forced the agent to either guess URLs or use web search as a workaround.
  • ›The agent relied on prior knowledge to guess /how-it-works and /about (both 200s) but had to use web search to discover /plans. This mix of luck and search dependency shows the site is not optimized for programmatic discovery.
  • ›The site is built on Framer, a visual design tool that prioritizes aesthetics over machine-readability; the agent noted this explicitly as a friction point.

Want to run your own?

Join the waitlist for early access to point your own agents at any domain, with the intents you choose.

or talk to us about agent readiness →