afacangumruk.com.tr
partial
Claude Code
intent

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

15steps
61.0sduration
$0.9548cost
181,408tokens
24 steps9 reasoning steps6 searches
home
home
/services
docs
docs
search
search
/about.asp
/technology.asp
/contact.asp
search
search
search
/afacangumrukleme
search
56%
on-site discovery
100%
reliability
11%
link following
path origin
  • previous resource11%
  • web search44%
  • prior knowledge44%
insight

The agent could not access readable content from Afacan's modern website and instead assembled an answer almost entirely from web search results and prior knowledge about Turkish customs brokerage. It successfully identified what Afacan does (customs consultancy), who it serves (import/export businesses), and how it differs (75+ year legacy), but could not retrieve pricing details or detailed service differentiation from the domain itself—all content-bearing steps were search results, not the target site.

  • ›The target site (afacangumruk.com.tr) returned valid HTTP 200 responses but only HTML skeleton with font definitions—no readable content. Every fetch of the domain structure [1,3,5,6,7] returned identical truncated markup with no differentiation between URLs, indicating either a single-page app that doesn't render server-side or a client-side rendering blocker.
  • ›The agent relied entirely on web search results [steps 9, 10, 16, 17, 19] to answer the core questions. Search snippets contained legacy info (est. 1951, founder details, sector experience, ZoomInfo company overview), and search result links pointed to outdated .asp versions of the site (about.asp, contact.asp) that the agent also could not read.
  • ›Pricing information came from a third-party Turkish government rate guide [step 17 search result: karacagumrukleme.com PDF on minimum tariffs], not from Afacan's own site. The agent explicitly noted 'could not find specific pricing on their website' and sourced regulatory minimums instead.
  • ›The site is not agent-ready for discovery tasks: it publishes no structured data (schema, JSON-LD), does not render readable text via HTTP fetch, and offers no alternative routes (API, sitemap, text-only version) to access content. The agent had to compensate using web search and prior knowledge.
  • ›All cited sources in the final response [steps 9, 10, 16, 17, 19] are search results or third-party sites, not content fetched from the target domain itself. The domain URL appears in citations only as the homepage, which provided no usable content.

Help the next agent finish on afacangumruk.com.tr

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 →