rte.ie
success
Claude Code
intent

What does rte.ie do and who is it for? Explain it back to me.

14steps
71.9sduration
$0.9169cost
149,376tokens
16 steps2 reasoning steps6 searches
home
docs
search
/our-services
about.home
search
/how-rte-is-funded-2
search
/player/en_ie/profile/…
search
search
search
docs
/player
62%
on-site discovery
88%
reliability
50%
link following
path origin
  • previous resource50%
  • web search38%
  • prior knowledge13%
insight

The agent successfully assembled a comprehensive explanation of RTÉ by combining web search results with fetches from about.rte.ie and external sources—because rte.ie itself does not prominently surface 'what we are' information. The main rte.ie domain is structured as a news/content site rather than an institutional explanation portal, forcing the agent to rely on the separate about.rte.ie subdomain, Wikipedia, external streaming guides, and TV licensing sites to answer what RTÉ does, who it's for, how it's priced, and how it differs from competitors.

  • ›Step [4] (about.rte.ie/our-services) and step [10] (about.rte.ie/how-rte-is-funded-2) were the only first-party resources that directly addressed RTÉ's services, mandate, and funding model—but these pages live on a subdomain separate from the main rte.ie domain and are not discoverable from the homepage without search.
  • ›Steps [12] and [13] (web searches) returned third-party content about TV licensing costs (€160/year), radio station names, and comparative context—information that should have been available on rte.ie itself but was not, forcing reliance on external sources like selectra.ie and Wikipedia.
  • ›Step [7] (about.rte.ie/) confirmed the About subdomain exists but provided only metadata; the agent had to drill into subpages to extract substance, indicating poor information architecture.
  • ›The agent did not successfully parse RTÉ Player subscription pricing from the site itself (RTÉ Player International at €8.99/month appeared only in prior knowledge and external sources, not in fetched steps), signaling that commercial/subscription details are not prominently published.
  • ›rte.ie/news (step [5]) and www.rte.ie/player (step [6]) returned SPA shells with minimal text content, requiring the agent to rely on meta tags and external context rather than readable page content.
  • ›The agent correctly identified and called out the disconnect between rte.ie (news hub) and RTÉ Player (streaming service) as a UX problem—this fragmentation is a direct consequence of the site's information architecture.

See every agent that visits rte.ie

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 →