cpdboard.org
partial
Claude Code
intent
What does cpdboard.org do and who is it for? Explain it back to me.
9steps
48.9sduration
$0.4443cost
88,459tokens
12 steps3 reasoning steps3 searches
home
docs
/how-it-works
docs
search
/professional-accredit…
docs
search
search
67%
on-site discovery
67%
reliability
50%
link following
path origin
- previous resource50%
- web search33%
- prior knowledge17%
insight
The agent assembled a partial answer about The CPD Board's business model, target audience, and competitive positioning, but could not locate pricing information despite multiple attempts. The site is built on Squarespace with client-side rendering that obscured full page content; the agent relied on page titles, metadata, and web search results to reconstruct positioning rather than parsing rich, machine-readable content from the fetched pages themselves.
- ›Steps [5], [7], and [8] returned only HTML boilerplate and metadata (title tags, Open Graph tags) — the actual page body content was truncated or not fully rendered. The agent inferred what each page was *about* from titles like 'Professional Accreditation | Achieve Accreditation Today' and 'CPD FAQs: The Complete Guide for Providers and Professionals,' but could not access substantive text explaining features, requirements, or pricing.
- ›Pricing information was entirely absent from the site. Direct attempts to access /pricing and /how-it-works returned 404s ([3], [4]). Web searches ([9], [10]) failed to surface pricing for cpdboard.org specifically, though they surfaced competitors' pricing (CPD Standards Board at £200). The agent correctly noted this as a critical gap but could not fulfill that portion of the task.
- ›The agent used web search ([6], [9], [10]) to discover pages and competitors rather than navigation links on the homepage. This suggests the site structure is either not clearly indexed or not exposed in a way that helps agents traverse it. The agent's final answer relied heavily on prior knowledge about CPD accreditation services and inferences from competitor research rather than on content directly fetched from cpdboard.org.
- ›The site is not agent-ready: Squarespace's rendering approach (noted in the HTML comments: '<!-- This is Squarespace. -->') prevents full-page content from being available in initial fetches. The agent could not access the rendered DOM or JavaScript-driven content, only static metadata. This is a structural impediment to content discovery.
Help the next agent finish on cpdboard.org
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 →