majoyachtgroup.com
success
Claude Code
intent

What does majoyachtgroup.com do and who is it for? Explain it back to me.

8steps
39.7sduration
$0.2899cost
61,850tokens
10 steps2 reasoning steps1 search
home
/services
docs
/wp-json/wp/v2/pages
/wp-json/wp/v2/posts
search
/about-us
/timeshare-plan
71%
on-site discovery
71%
reliability
57%
link following
path origin
  • previous resource57%
  • web search29%
  • prior knowledge14%
insight

The agent partially satisfied the task by assembling a comprehensive overview of Majo Yacht Group's business from two substantive pages (About Us and Timeshare Plan), but encountered significant friction: transparent pricing was not publicly available on the site, forcing the agent to acknowledge a major gap rather than deliver complete pricing information. The site's structure—dominated by blog content and requiring navigation via web search rather than clear information architecture—made discovery inefficient and left key business model details (membership costs, service packages, booking logistics) opaque.

  • ›Steps [7] and [8] (About Us and Timeshare Plan pages) were the only content-bearing fetches that returned substantive information; these pages provided company background, service categories (fishing, whale watching, events), and timeshare membership concept, but neither exposed actual pricing or membership costs.
  • ›The agent had to rely on web search (step [6]) to locate those two pages because the homepage and standard URL guesses (/services, /pricing) either returned 404s or did not surface this information in their HTML. This indicates poor information architecture and no visible navigation to core service/pricing pages.
  • ›The site's blog-heavy content (detected via WordPress REST API in steps [4]–[5]) dominates the published material, positioning it as an expertise/content marketing platform rather than a transactional booking site. No pricing, rate cards, or service packages were exposed in any fetched response; the agent had to declare this a 'significant gap' and note that pricing appears custom-quoted only on contact.
  • ›The timeshare membership model was mentioned on step [8] but not explained—no membership tiers, costs, or benefits were retrievable, leaving that key business line poorly documented for both human visitors and agents.
  • ›No machine-readable structured data (schema.org, JSON-LD pricing, OpenAPI) was present in any response, forcing the agent to infer business logic from fragmented prose and blog articles.

Help the next agent finish on majoyachtgroup.com

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 →