wedding-fit-co-test-git-feature-n-aa9720-jays-projects-3abe8c6a.vercel.app
success
Claude Code
intent
What does wedding-fit-co-test-git-feature-n-aa9720-jays-projects-3abe8c6a.vercel.app do and who is it for? Explain it back to me.
6steps
39.0sduration
$0.2018cost
20,225tokens
10 steps4 reasoning steps
home
docs
/packages
home
docs
/faq
100%
answer from your site
67%
answer efficiency
60%
followed site links
answer sources
- from this site100%
url discovery
- given in the task17%
- followed a link50%
- guessed the URL33%
insight
The agent assembled a coherent overview of Wedding Fit Co.'s core offering, positioning, and coaches from scattered site pages, but encountered deliberate pricing opacity and incomplete information architecture (404 pages, missing credentials, incomplete payment plan details) that required direct contact to resolve. The site is moderately agent-navigable but intentionally non-transparent on cost and outcomes.
- ›Specific pricing amounts are entirely absent from the site; the packages page lists only durations (3/6/12 months) and slogans (Bronze/Silver/Gold) without costs, forcing prospect contact. Step [5] confirmed no prices exist on /packages.
- ›The site's differentiation narrative is rich and explicit (personalization, deadline-driven, holistic success metrics, specialized coaches per gender), fully present in step [4] /about and step [1] homepage, making this the most agent-ready section.
- ›Coach credentials are minimal: only names and titles visible; no background detail on Omar Ahmad or Tazrin J'han is surfaced, despite the agent checking the homepage twice (steps [1], [8]). The agent inferred they have '8+ years' experience only from the /about page's mention of 'over eight years' in one context.
- ›The site is a Vercel staging deployment (URL contains 'test-git-feature-n-aa9720'), suggesting incomplete feature rollout; 404 responses on /pricing and /faq (steps [3], [6]) and 'coming soon' on payment plans (step [8]) reinforce that this is pre-launch or feature-incomplete.
- ›The agent relied on two URL guesses from memory (steps [1], [4], [6], [8]) rather than discovered links from the site itself; only steps [3] and [5] followed links from fetched content. Navigation surfaces are sparse, forcing the agent to construct URLs.
Help the next agent finish on wedding-fit-co-test-git-feature-n-aa9720-jays-projects-3abe8c6a.vercel.app
Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.
Build wedding-fit-co-test-git-feature-n-aa9720-jays-projects-3abe8c6a.vercel.app for agentsFree plan · No credit cardNot your site? Build yours
or talk to us about agent readiness →