rer.sa
success
Claude Code
intent

What does rer.sa do and who is it for? Explain it back to me.

17steps
94.8sduration
$0.8505cost
149,848tokens
28 steps11 reasoning steps7 searches
home
/en
docs
docs
/ar
/services
search
/en/rer-services
search
/blogs/understanding-s…
search
search
search
search
/en/about-us
/en/rega-services/plat…
search
60%
on-site discovery
50%
reliability
40%
link following
path origin
  • previous resource40%
  • web search40%
  • prior knowledge20%
insight

The agent partially satisfied the task by assembling a coherent explanation of RER from fragmented sources, but had to rely heavily on web search and external articles rather than the rer.sa site itself, which proved difficult to navigate and incomplete. The agent successfully explained what RER does, who it serves, and how it differs from alternatives, but could not find clear pricing information on the official site and had to note this as a gap.

  • ›Step [1] (homepage) and step [8] (services page) returned truncated HTML that didn't load full content—the site is JavaScript-heavy and doesn't serve machine-readable content in baseline fetches. The agent could extract only meta descriptions and structural hints, not actual page content.
  • ›Steps [13] and [16] (About page and REGA government page) were the most content-bearing for understanding RER's role and mission, but even the About page returned incomplete content. The agent had to infer positioning from meta tags and HTML structure rather than readable prose.
  • ›Step [19] (external article from Diligencia Group) was the only source that provided substantive, readable explanation of the deed-based vs. title-based system shift and RER's differentiation—this came from outside the rer.sa domain entirely. The site itself does not articulate its competitive advantage clearly.
  • ›Multiple direct guesses at common routes (/pricing, /about, /en, /ar) returned 'Request Rejected' errors (steps [3–7]), suggesting the site has aggressive URL filtering or routing that blocks agent exploration. Only searches and prior knowledge could find valid URLs.
  • ›Pricing information was not published on rer.sa at all. The agent noted this explicitly as missing and had to synthesize estimates from third-party sources (transaction taxes, agent commissions, legal fees). The core RER service fees remain opaque.
  • ›The site is government-backed and monopolistic (no competitors in Saudi Arabia), which eliminates a key discovery/comparison dimension. The agent had to explain differentiation relative to the previous paper-based system rather than alternatives.

Help the next agent finish on rer.sa

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 →