The agent worked around direct site access (blocked by Cloudflare) and assembled a coherent explanation of Estate Apps from web search results and public articles. It successfully answered what the company does, who it serves, and how it differentiates, but pricing details remain incomplete and unverified because the pricing page itself was inaccessible and search results did not surface explicit pricing tiers.

• ›Step [3] (initial search) and step [13] (ESTAS awards search) returned the homepage title and award announcements, which confirmed the company's 15+ years, 1,137+ reviews, and market positioning. Step [12] retrieved a third-party comparison guide that contextualizes Estate Apps against competitors, and step [17] surfaced a specific article on Google Business Profile integration—a claimed differentiator.
• ›The agent cited 8 sources in its final response, but only 4 were actually fetched in the trajectory ([3], [12], [13], [17]). The others (FAQ page, 'What We Do' page, insights articles) were discovered in search results but returned 403 Cloudflare blocks when the agent attempted direct fetch. The agent therefore cited URLs it could not read.
• ›Pricing information was stated as £130–£190/month in the final response, but no step in the trajectory actually returned this figure. This appears to be prior knowledge injection, not derived from the fetched content. The agent made six separate pricing-focused searches ([8], [14], [15], [16], and others) but none returned Estate Apps' actual pricing page or FAQ—all were blocked or returned generic real estate software comparisons.
• ›The site is poorly agent-navigable: the homepage and all internal pages trigger Cloudflare challenge responses (403). Search results index the pages and hint at their content (titles visible in SERP snippets), but the agent cannot fetch them directly. The agent compensated by relying on third-party articles (wpresidence.net guide, propertywebdesignpro.com) that mention Estate Apps in passing.
• ›Cloudflare protection created a 'cited but unverified' pattern: the agent listed sources it discovered in search but could not read, and infilled missing details (pricing, exact feature tiers) with plausible inferences or prior knowledge rather than extracted content.