andrewmcgehee.com
success
Claude Code
intent

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

5steps
20.2sduration
$0.1392cost
29,251tokens
6 steps1 reasoning step
home
/projects
/writing
docs
/rss.xml
100%
on-site discovery
80%
reliability
60%
link following
path origin
  • previous resource60%
  • prior knowledge40%
insight

The agent successfully synthesized an understanding of andrewmcgehee.com by visiting the homepage, projects, and writing sections, then supplemented with RSS feed metadata to confirm the site's purpose and content focus. However, the agent had to work around truncated HTML responses and missing page content — it could not actually view the full project list or detailed project descriptions, and instead relied heavily on prior knowledge and RSS feed titles to construct its answer about what Andrew McGehee does.

  • ›Step [0] (homepage) and steps [1–2] (projects and writing section landing pages) returned HTML with meaningful structure and metadata but were truncated in the fetch responses, preventing the agent from extracting full page content. The agent had to infer structure and purpose from partial metadata and navigation hints.
  • ›Step [4] (RSS feed) was the most content-bearing: it returned feed metadata ('Notes and essays from Andrew's public notebook') and recent article titles ('Baby Terminator learns to crawl' suggesting AI focus), allowing the agent to confirm the site's knowledge-sharing intent and topic areas — this single artifact corroborated claims made in the final response.
  • ›The agent relied on prior knowledge (40% of sourcing) to fill gaps left by truncated HTML — it asserted Andrew is 'a senior SAP consultant in Germany' without retrieving that information from the site, suggesting either that context was inferred from domain name / RSS metadata or supplied from training data. The site did not publish a clear 'about' page (step [3] returned 404), forcing reliance on contextual inference.
  • ›The site is poorly agent-ready: it lacks a structured data schema (JSON-LD, microdata), no dedicated about/bio endpoint, and pagination/list views returned truncated HTML rather than machine-readable content. The RSS feed was the only semi-structured machine-readable artifact the agent could access.
  • ›The agent acknowledged three significant knowledge gaps: unclear project list, missing contact/hire information, and limited detail on portfolio depth. Despite marking the task as 'success,' the agent actually delivered a partial answer built from fragments and inference rather than complete, directly-retrieved information.

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