ssa.gov
partial
Claude Code
intent
What does ssa.gov do and who is it for? Explain it back to me.
5steps
20.9sduration
$0.0141cost
21,350tokens
8 steps3 reasoning steps1 search
home
docs
/benefits/retirement
search
/faqs/en
0%
answer from your site
0%
answer efficiency
0%
followed site links
answer sources
- from search results33%
- from agent knowledge67%
url discovery
- found via web search25%
- guessed the URL75%
insight
The agent could not complete the task: every direct fetch of ssa.gov returned HTTP 403, so it relied on a single search returning snippets. It produced a plausible overview of SSA's services, but pricing, audience framing, and the competitive comparison were inferred rather than retrieved from the site.
- ›The site blocked all direct fetches (homepage, /about, /benefits/retirement, /faqs/en) with HTTP 403, so no full page content was retrievable by the agent.
- ›The only content-bearing source was a web search whose snippets described core services, phone hours, and my Social Security account requirements.
- ›The 'free' pricing claim and the comparison with alternatives were not supported by any retrieved text and were inferred from general knowledge.
- ›The agent did disclose the access failure and flagged unverified claims, which mitigates the risk of presenting memory as sourced fact.
- ›The site is not agent-ready: it exposes no machine-readable or fetchable summary, and bot-blocking prevents assembly of the answer from primary pages.
Help the next agent finish on ssa.gov
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 →