earthvoyage.us
success
Claude Code
intent
What does earthvoyage.us do and who is it for? Explain it back to me.
13steps
65.6sduration
$0.8706cost
116,161tokens
15 steps2 reasoning steps7 searches
home
docs
docs
/faq
search
search
/company/earthvoyage
search
search
search
/postcard-app
search
search
67%
on-site discovery
100%
reliability
17%
link following
path origin
- previous resource17%
- web search33%
- prior knowledge50%
insight
The agent assembled a comprehensive explanation of Earth Voyage by combining fragments from the site's meta description and a third-party postcard app review. The site itself is a single-page application (SPA) with client-side rendering, making direct HTML fetching uninformative—all fetches returned identical truncated boilerplate. The agent worked around this inaccessibility by relying on the meta description tag and external sources to reconstruct what Earth Voyage does, who it's for, pricing, and differentiation.
- ›Step [1] (homepage) returned only meta tags and truncated HTML; the actual page content is rendered client-side. The meta description ('Create and send real physical postcards from your phone. Upload a photo, write a message, and we deliver it from anywhere in the world.') became the primary source of core product definition.
- ›Steps [2–4] (pricing, about, FAQ routes) all returned identical SPA boilerplate and were non-content-bearing—the site's architecture prevented the agent from accessing meaningful page-specific content despite correct HTTP 200 responses.
- ›Step [8] (LinkedIn company page) and Step [13] (third-party postcard app review) provided context and comparative framing, but LinkedIn returned boilerplate HTML and the review (duendebymadamzozo.com) appears to have been cited as a source despite no evidence it contained Earth Voyage-specific details in the fetched response.
- ›The pricing structure ($4.99 single, $9.99 for 3, $29.99 for 10) is stated in the agent's response but does not appear in any fetched step response—this was likely reconstructed from prior knowledge or inferred from web search snippets (step [6]) that were not included in the trajectory details.
- ›Site navigability: poor. The SPA architecture makes the site invisible to standard crawling. No structured data (JSON-LD, schema.org), no plaintext fallback, and no sitemap hints were evident. The agent could not fetch dynamic content and had to rely entirely on meta tags and external sources.
- ›The agent correctly identified significant gaps (delivery times, geographic coverage, refund policy, customer reviews, company background) that were not recoverable from the available fetches, indicating honest assessment of what the site failed to expose.
Help the next agent finish on earthvoyage.us
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 →