goodlord.co
success
Claude Code
intent
What does goodlord.co do and who is it for? Explain it back to me.
15steps
72.9sduration
$1.1616cost
157,055tokens
23 steps8 reasoning steps8 searches
home
docs
/features
docs
home
search
search
search
/p/201845/goodlord
search
search
search
search
search
docs
71%
on-site discovery
86%
reliability
29%
link following
path origin
- previous resource29%
- web search29%
- prior knowledge43%
insight
The agent assembled a comprehensive explanation of Goodlord by relying heavily on web search results and third-party comparison articles, since the Goodlord website itself returned minimal readable content (all fetches were HTML shells without visible text). The task was satisfied—the agent provided clear, cited answers to all four questions (what, who, pricing, differentiation)—but only by working around the site's lack of agent-readable content and supplementing with external sources and prior knowledge.
- ›All direct fetches of goodlord.co (steps [1], [2], [3], [5], [6]) returned truncated HTML with no accessible body text, forcing the agent to rely entirely on web search and external sources. The site is not machine-readable as-fetched.
- ›Web searches (steps [8], [9], [14], [15], [20], [21]) returned link results with snippets and article titles, which signaled where information lived but did not embed the actual answers. The agent then selectively fetched comparison articles (step [17]) that contained competitive context and some feature details.
- ›The agent disclosed pricing opacity as a key finding: Goodlord does not publish pricing on their website, requiring quote-based demos. This was discovered indirectly (via search snippets and third-party reviews) rather than from the official site, which would have immediately signaled the answer if it had a pricing page.
- ›Differentiation and features (AI referencing, bundled insurance, professional guarantor service) were sourced entirely from web search results and third-party articles, not from the Goodlord website itself. The site's own platform page returned no readable content to fetch.
- ›The agent cited seven sources in the final response; only one (Goodlord's main site and platform/about pages) was a first-party URL, and those returned no readable content. The agent's answer was primarily built from third-party comparison articles and search snippets, with Goodlord's website functioning as a verification checkpoint rather than an information source.
See every agent that visits goodlord.co
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 →