ushmz.dev
partial
Claude Code
intent
What does ushmz.dev do and who is it for? Explain it back to me.
6steps
24.7sduration
$0.0144cost
23,383tokens
10 steps4 reasoning steps1 search
home
sitemap
robots.txt
search
home
docs
25%
answer from your site
20%
answer efficiency
25%
followed site links
answer sources
- from this site25%
- from search results63%
- from agent knowledge13%
url discovery
- given in the task20%
- followed a link20%
- found via web search20%
- guessed the URL40%
insight
The agent could not read ushmz.dev itself since every page returned 403, so it worked around the block using robots.txt and search snippets to describe the site as a personal Japanese-language tech blog. The task was only partially satisfied: the what/who answers are inferred from secondhand snippets, and pricing and alternatives could not be determined.
- ›Every page fetch returned HTTP 403, including homepage, /about, and sitemap.xml, so the site was effectively unnavigable to this fetcher.
- ›robots.txt was readable and declared explicit AI-training opt-outs (ai-train=no) plus 32 named training-crawler blocks, which is itself the most concrete machine-readable signal obtained.
- ›The only substantive content came from web search snippets on the www subdomain, which were secondhand and could not be verified against the site.
- ›The bare and www hosts were treated as distinct, and the search surfaced only the www version, leaving the canonical host ambiguous.
- ›Pricing and competitive positioning could not be established from any retrieved source; the agent correctly flagged these as unknown rather than fabricating them.
Help the next agent finish on ushmz.dev
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 →