aviva.com
partial
Claude Code
intent
What does aviva.com do and who is it for? Explain it back to me.
4steps
21.3sduration
$0.0148cost
22,315tokens
8 steps4 reasoning steps1 search
home
/about-us
search
/faqs-about-aviva
0%
answer from your site
0%
answer efficiency
0%
followed site links
answer sources
- from search results80%
- from agent knowledge20%
url discovery
- found via web search33%
- guessed the URL67%
insight
The agent could not complete the task because aviva.com returned 403 on every direct fetch, so it worked around the block using a single search whose snippets quoted Aviva's site and third-party profiles. Pricing was not found and was filled by inference, so the task is only partially satisfied.
- ›All three first-party fetches (homepage, about-us, FAQ) returned HTTP 403, so the site was effectively unreadable to an automated agent.
- ›The agent guessed page URLs from memory rather than following links from a fetched page, since no page was ever readable to surface links.
- ›The single web search returned rich, usable summary content from Aviva's own pages via snippets, showing the substance was indexed even though direct access was blocked.
- ›Pricing, fees, and eligibility were never retrieved from any source, leaving the 'how it's priced' part of the task unanswered and inferred.
- ›Figures conflicted across sources (assets under management, customer counts), and the agent flagged this rather than resolving it.
Help the next agent finish on aviva.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 →