int.aestura.com
success
Claude Code
intent

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

10steps
46.5sduration
$0.4878cost
177,511tokens
18 steps8 reasoning steps1 search
home
/collections/all
/pages/about-us
/pages/about
/products/atobarrier36…
/collections/best-seller
/pages/brand-story
search
/blogs/news/aestura-ko…
/brand/aestura
78%
on-site discovery
67%
reliability
56%
link following
path origin
  • previous resource56%
  • web search22%
  • prior knowledge22%
insight

The agent partially completed the task by assembling a coherent explanation of AESTURA's positioning, target audience, and competitive differentiation, but was unable to retrieve complete pricing or detailed product information directly from int.aestura.com due to HTML truncation and 404 errors. The site proved difficult to navigate programmatically; the agent relied heavily on web search results and external sources (PR Newswire, third-party skincare guides) to fill gaps left by the truncated or missing pages on the official domain.

  • ›Step [10] (Brand Story page) was the only substantive content-bearing fetch from int.aestura.com itself, though the HTML was truncated and yielded minimal usable detail. Steps [1], [3], [9] also returned 200s but were too truncated to extract product specs or pricing.
  • ›Steps [12] (web search) and [14] (third-party brand guide from mirai-skin.com) were the primary sources of actionable information about AESTURA's positioning, research backing, Korean dermatologist endorsement, and Sephora partnership. The agent could not extract this from the official site and had to route through external sources.
  • ›The site's own pages returned frequent 404s (steps [4], [7]) and heavily truncated HTML responses, signaling either aggressive content delivery optimization, client-side rendering that wasn't captured, or regional/localization issues. Pricing was explicitly noted as 'not clearly visible' on the site itself.
  • ›The agent was forced to cite external sources (PR Newswire, Mirai Skin blog, AmorePacific group page) as the primary basis for answering 'how it's priced' and 'how it's different'—information that should have been on int.aestura.com but was not machine-readable or accessible in the fetched responses.
  • ›The site appears to be Shopify-based (standard Shopify headers in responses) and configured for multiple regional versions (Japanese content language detected). This may explain why structured product/pricing data was not exposed in the HTML returned to the agent.

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