hassanahmed.me
partial
Claude Code
intent

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

22steps
100.7sduration
$1.3785cost
224,627tokens
35 steps13 reasoning steps12 searches
home
/work
/services
search
search
sitemap
/projects
docs
/projects/londinium-es…
/shopify-vape-migration
search
search
search
search
search
/projects/londinium-ch…
/api
search
search
search
search
search
100%
on-site discovery
70%
reliability
70%
link following
path origin
  • previous resource70%
  • prior knowledge30%
insight

The agent assembled a partial but incomplete picture of Hassan Ahmed's consulting practice by combining sitemap discovery, search results, and inferred knowledge. The site itself is not agent-navigable—it is a client-side React application that returns only HTML scaffolding with no rendered content in fetched responses. The agent relied almost entirely on web search snippets and prior knowledge to construct an answer, filling critical gaps (pricing, engagement model, service scope) with inference rather than primary source material.

  • ›Step [8] (sitemap.xml) was the only structural artifact the site published; it listed pages (/projects, /blog, /shopify-vape-migration, etc.) but the agent could not extract text content from any of them because they are Next.js client-side rendered.
  • ›Steps [9], [20], [27], [29] were web searches that returned Google snippets mentioning Hassan Ahmed's blog and a discount engine, but not the actual content of those pages. The agent cited search result titles as sources (e.g., 'Blog — Shopify Plus, Functions & Laravel Field Notes') without ever retrieving the rendered content.
  • ›Step [12] (hassanahmed.me/blog) returned a 200 status with only HTML boilerplate (~4400 chars of Next.js scaffolding); no blog posts, pricing, or service descriptions were present in the response body.
  • ›Critical information gaps remain unfilled: pricing/rates are explicitly absent; the engagement model is unclear; the relationship between Hassan Ahmed, the Londinium platform, and the Discount Engine is inferred rather than stated; and there is no visible contact/booking interface on pages the agent could access.
  • ›The site is hostile to crawlers and agents—it publishes no semantic data (no JSON-LD, structured data, or meta descriptions with substantive content) and relies entirely on client-side rendering, making it impossible for an agent to extract information without a JavaScript interpreter.
  • ›The agent compensated by using search engines and prior knowledge (70% of fetches via artifact/memory), effectively working around the site's lack of agent-readiness rather than extracting information from it directly.

Help the next agent finish on hassanahmed.me

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 →