safome.au
success
Claude Code
intent

What does safome.au do and who is it for? Explain it back to me.

26steps
107.6sduration
$1.0343cost
604,857tokens
41 steps15 reasoning steps4 searches
home
docs
/wp-json/wp/v2/pages/146
docs
docs
/product
/wp-json/wp/v2/pages
/wp-json/wp/v2/pages
/wp-json/wp/v2/pages
/wp-json/wp/v2/pages/2…
/wp-json/wp/v2/pages/194
search
/wp-json/wp/v2/pages/2…
/wp-json/wp/v2/pages/2…
/wp-json/wc/v3/products
/product/s7-mini-alway…
/wp-json/wp/v2/product…
search
search
/plans
/wp-json/wp/v2/product
/wp-json/wp/v2/posts
search
/wp-json/wp/v2/pages/2…
/faq
/wp-json/wp/v2/pages/2…
100%
on-site discovery
82%
reliability
91%
link following
path origin
  • previous resource91%
  • prior knowledge9%
insight

The agent assembled a working explanation of Saf O' Me by fetching the homepage, About, Products, FAQ, Services, and Contact pages via both HTML and WordPress JSON APIs, plus one specific product page. However, the task is only partially satisfied: the agent successfully explained what they do, who it's for, and how they differ from alternatives, but could not find pricing information—a dedicated 'Membership Pricing' page returned as empty, and no prices are listed on product pages or elsewhere on the site, forcing the agent to explicitly call out this critical gap rather than provide a complete explanation.

  • ›The site publishes core business information (mission, target audiences, product features, services) in Elementor-built pages, which rendered as HTML but the agent extracted cleaner structured data via WordPress JSON API endpoints (/wp-json/wp/v2/pages/{id}). This hybrid approach was agent-friendly for discovery but required guessing the correct endpoint pattern.
  • ›Pricing is deliberately or accidentally hidden: the /membership-pricing/ page exists but returns 'Empty membership group.' and the /pricing/ and /plans/ routes return 404s. The agent found no prices on the S7 Mini product page or anywhere else in fetched content, indicating either incomplete implementation or intentional gating (e.g., prices shown only in shopping cart or on contact).
  • ›The site's information architecture works against discovery—there is no public pricing, no explicit competitor comparison, no FAQ entry explaining subscription tiers, and no e-commerce API access (WooCommerce API returned 401). The agent had to assemble the explanation from scattered page content rather than from a centralized, machine-readable resource like a pricing table or structured data markup.
  • ›The agent relied heavily on prior knowledge of WordPress API patterns (9% prior knowledge, 91% artifact reuse) to identify and fetch the right endpoints after initial HTML fetches. This suggests the site is not optimized for agent crawling—there are no sitemaps, robots.txt hints, or JSON-LD structured data that would have helped an agent discover the API endpoints or missing pages automatically.

Help the next agent finish on safome.au

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 →