co.faces.com
success
Claude Code
intent

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

8steps
50.8sduration
$0.4487cost
54,073tokens
13 steps5 reasoning steps3 searches
home
home
search
/perfumes
/maquillaje
/sobre-nosotros
search
search
100%
on-site discovery
80%
reliability
80%
link following
path origin
  • previous resource80%
  • prior knowledge20%
insight

The agent assembled a comprehensive understanding of Faces Colombia by combining limited on-site content (homepage and category pages) with external research. The website itself was minimally informative—heavily JavaScript-rendered with little accessible content—so the agent relied on web search results and prior knowledge to answer what Faces does, who it's for, how it's priced, and how it differs from competitors. The site was navigable but not agent-readable; real business intelligence came from external news and business analysis articles, not from co.faces.com directly.

  • ›Step [2] (homepage fetch) returned only boilerplate HTML with no semantic content; the agent could confirm the site exists and uses VTEX platform but could not extract business model, pricing, or positioning from the page itself.
  • ›Steps [5] and [6] (perfumes and makeup category pages) also returned only generic VTEX scaffolding with no product data, brand lists, or pricing visible in the raw HTML, indicating heavy client-side rendering that blocks agent content extraction.
  • ›Step [3] (initial web search) surfaced the key positioning—'retailer de belleza de lujo' (luxury beauty retailer)—and revealed the Middle Eastern origin, which the agent used to differentiate Faces from Sephora. This single search result was more informative than all three on-site fetches combined.
  • ›Steps [9] and [11] (follow-up searches for business model and competitive strategy) provided the substantive details about omnichannel strategy, AI partnerships (Revieve), regional expansion into Latin America, and brand curation philosophy. All cited sources were external journalism and business analysis, not the website.
  • ›The agent could not access loyalty programs, shipping policies, return procedures, or brand exclusivity details—these either don't exist on the site or are hidden behind JavaScript interactions that the agent cannot execute.
  • ›Site navigability was achieved through guess-based URL construction (/perfumes, /maquillaje, /sobre-nosotros) rather than discovered links; no internal navigation or structured data (JSON-LD, schema.org) was present to guide the agent programmatically.

See every agent that visits co.faces.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 →