dsv.com
success
Claude Code
intent
What does dsv.com do and who is it for? Explain it back to me.
7steps
45.9sduration
$0.4496cost
23,915tokens
12 steps5 reasoning steps2 searches
home
/en/solutions
/en/pricing
/en/services
/en/about
search
search
33%
answer from your site
20%
answer efficiency
100%
followed site links
answer sources
- from this site33%
- from search results50%
- from agent knowledge17%
url discovery
- given in the task20%
- followed a link80%
insight
The agent successfully assembled a comprehensive explanation of DSV from the homepage and web search results, but had to work around the site's inaccessible subpages (/pricing, /services, /about all returned 404s) and lack of publicly visible pricing. The site's navigation structure forced heavy reliance on external sources and search results to answer pricing and competitive positioning questions.
- ›The homepage ([1]) provided rich content about DSV's services, transport modes, and digital tools, but the agent could not access any subsidiary pages on the domain—four consecutive attempts to fetch /solutions, /pricing, /services, and /about all returned 404 errors, forcing pivot to web search.
- ›Pricing information came entirely from search results ([9]), not from dsv.com itself. The agent learned that DSV uses value-based, quote-based pricing with no published tariffs, surfacing a major usability gap: the site does not expose its pricing model in a machine-readable or easily discoverable way.
- ›Competitive positioning and market rank ([10]) came entirely from third-party sources (Gartner, GoFreight), not from DSV's own messaging. The search results revealed DSV is now #1 by revenue after the DB Schenker acquisition, but this claim would not have been discoverable by navigating dsv.com alone.
- ›The agent filled several gaps using model memory—notably the observation that 'small customer accessibility' is unclear and that 'operationally what sets them apart isn't crystal clear'—because the site does not explicitly segment by customer size or deeply articulate operational differentiation beyond generic phrases like 'full visibility.'
- ›All four 404 errors suggest the site either uses dynamic routing (URLs not matching expected /en/ structure), requires authentication, or has a shallow information architecture; this prevented the agent from verifying or expanding on homepage claims through dedicated pages.
See every agent that visits dsv.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 →