gwshutters.com
success
Claude Code · Haiku 4.50:54
intent
What does gwshutters.com do and who is it for? Explain it back to me.
15steps
54.5sduration
$1.1215cost
211,215tokens
20 steps5 reasoning steps6 searches
home
docs
/products
docs
/shutters
/customize
search
search
/about-us
/design
/designer
search
search
search
search
100%
on-site discovery
56%
reliability
44%
link following
path origin
- previous resource44%
- prior knowledge56%
insight
The agent successfully assembled a comprehensive overview of GW Shutters by combining sparse website content with web search results. The website itself was minimally navigable for this task—key pages like /about-us, /shutters, and /designer returned content but the agent relied heavily on search snippets and prior knowledge to construct the full picture. Pricing, service scope, and differentiation had to be pieced together from blog articles and external reviews rather than being clearly presented on the core site.
- ›Steps [1], [3], [7], [13], [14] returned HTML but were heavily truncated in the trajectory; the agent's final response cites blog articles (/blog/plantation-shutters-cost-2026, /blog/real-lead-time-for-custom-shutters) and the /about-us page explicitly, indicating these were the content-bearing fetches that supplied pricing ranges, lead time info, local manufacturing claim, and company history.
- ›The agent guessed at URL patterns (/pricing, /products, /design, /customize, /designer) with mixed success—many 404s—and had to rely on web search (steps [11], [12], [15], [16], [17], [18]) to discover actual pages like /blog/plantation-shutters-cost-2026 and /current-promotions-golden-west-shutters that contained substantive information.
- ›The website lacks transparent pricing on its main pages and does not publish a clear product matrix, service area definition, or how-it-works flow. Pricing had to be scraped from a blog article; differentiation claims ('locally manufactured', 'Polylux Hybrid', 'lifetime warranty') were not centrally documented. The /designer page at [14] loaded successfully but the agent could not extract what it does, indicating either poor introspection or that the tool itself requires interaction.
- ›The agent assembled a coherent business model summary without visiting the website's full navigation—roughly 56% of the final answer came from prior knowledge and the 44% from previous artifact (search results and blog fragments), suggesting the site's core pages do not self-document the business in an agent-readable way.
Want to run your own?
Join the waitlist for early access to point your own agents at any domain, with the intents you choose.
or talk to us about agent readiness →