screenly.io
success
Claude Code
intent

What does screenly.io do and who is it for? Explain it back to me.

4steps
46.5sduration
$0.0207cost
27,715tokens
5 steps1 reasoning step1 search
home
docs
/features
search
67%
answer from your site
100%
answer efficiency
100%
followed site links
answer sources
  • from this site67%
  • from search results17%
  • from agent knowledge17%
url discovery
  • given in the task33%
  • followed a link67%
insight

The agent successfully gathered a comprehensive overview of Screenly's offering, pricing, and market position by fetching the homepage, pricing page, and features page directly, then augmented with third-party comparison data via web search. The site was navigable and published key information in fetchable form, though it omitted explicit competitor comparisons and left some product relationships unclear.

  • ›Step [0] (homepage) and Step [1] (pricing page) were directly accessible and provided core facts: what Screenly does, its target sectors, pricing tiers, and feature breakdowns. The site's information architecture made these resources easy to find via links.
  • ›Step [2] (features page) reinforced positioning and security claims but explicitly stated 'No competitor comparisons' — the agent correctly noted the site names no competitors, forcing reliance on external sources.
  • ›Step [3] (web search) was necessary to answer the 'how it's different from alternatives' part of the task; the site itself supplied no comparative data. The agent properly cited third-party blogs (Brix Signage, BuzzBlender, DigitalSignage.com, CrownTV) as sources for competitor pricing and features.
  • ›The agent identified three genuine gaps: (a) Enterprise pricing listed as custom-quoted on-site vs. $38/screen in one search result, which it flagged and did not reconcile; (b) a Monthly/Annually toggle on the pricing page that yielded only annual prices in the fetched content, suggesting truncation or missing implementation; (c) overlapping product names (Player, Player Max, ScreenlyOS, Anywhere) that the site did not clearly distinguish.
  • ›The agent did NOT fetch or cite details from /docs/, /security/, /enterprise/, /players/, or /os/ pages despite their presence in the homepage link list. The response is complete without them, indicating the primary pages (/, /pricing/, /features/) contained sufficient facts to answer the task.

See every agent that visits screenly.io

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 →