keepsakemessages.com
partial
Claude Code
intent

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

15steps
97.9sduration
$1.1002cost
186,147tokens
21 steps6 reasoning steps8 searches
home
/demo
/why-us
search
search
search
home
search
search
search
/sign-in
search
search
home
home
100%
on-site discovery
100%
reliability
86%
link following
path origin
  • previous resource86%
  • prior knowledge14%
insight

The agent gathered a substantial but incomplete picture of Keepsake Messages by accessing the homepage, demo page, and why-us page, which provided core concepts (digital audio guestbook, QR-code-based, no hardware rental, audio enhancement) and confirmed Canadian pricing starting at $39 CAD. However, the site's HTML was heavily truncated in responses, and search engines returned no indexed content from keepsakemessages.com itself, forcing the agent to rely on prior knowledge and competitive context rather than direct product documentation. The agent fulfilled the exploratory task scope—explaining what they do, who it's for, basic pricing, and differentiation—but could not access detailed pricing tiers, feature specifications, or guest-facing mechanics due to site inaccessibility.

  • ›Steps [1], [3], [4] returned HTML stubs that were truncated to ~4400 characters each, preventing extraction of full page content. The agent could not read actionable text from the fetched pages themselves; it reconstructed the narrative from page titles, URL structure, and prior knowledge instead.
  • ›Web searches [6]–[19] returned results for competitors (LifeOnRecord, After The Tone, FêteFone) but found no indexed pages from keepsakemessages.com in search results, indicating the site is either newly launched, not yet indexed, or robots.txt-blocked. The agent's description of features (audio enhancement, QR codes, immediate availability, no app) and pricing ($39 CAD for 100 recordings) came from prior knowledge, not from parsing fetched or indexed content.
  • ›The site uses a Next.js frontend with client-side rendering (evident from truncated HTML structure and preloaded font/script chunks). No structured data (schema.org, JSON-LD), plain-text meta descriptions, or static landing page content was accessible to the agent—only the bare HTML shell. This design pattern severely constrains agent discoverability and comprehension.
  • ›The agent explicitly cited three URLs in its final Sources section but did not quote specific text from them, indicating the citations are aspirational rather than grounded in retrieved content. No pricing page, feature breakdown, or competitive comparison page was accessible.
  • ›The site is navigable in the sense that URLs resolve (200 status codes), but content is not extractable—a critical distinction. The agent had to bridge this gap using general knowledge about the audio guestbook market rather than product-specific documentation.

Help the next agent finish on keepsakemessages.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 →