xtiles.com
success
Claude Code
intent

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

7steps
44.1sduration
$0.5134cost
43,620tokens
12 steps5 reasoning steps3 searches
home
/lander
search
/en
/en/pricing
search
search
50%
on-site discovery
100%
reliability
25%
link following
path origin
  • previous resource25%
  • web search50%
  • prior knowledge25%
insight

The agent successfully evaluated xTiles by discovering and assembling information from web search results and third-party review sites, since the primary domain (xtiles.com) was parked on GoDaddy and the actual service lives at xtiles.app. The agent provided a comprehensive explanation of what xTiles does, who it's for, pricing tiers, and how it compares to alternatives — but had to work around poor site discoverability and reliance on external sources rather than xTiles' own structured documentation.

  • ›The xtiles.com domain redirected to a GoDaddy sales page ([1], [2]), creating immediate friction. The agent pivoted to web search and discovered the actual service at xtiles.app through search results ([4]).
  • ›Direct fetches of xtiles.app ([6], [7]) returned HTML but no extracted content snippets were visible in the trajectory — the agent relied entirely on web search results and third-party review aggregators (Research.com, SaaSworthy, thebusinessdive.com) to answer pricing, features, and competitive positioning. The actual xTiles pricing page was fetched ([7]) but did not surface extractable data in the shown response.
  • ›Web searches ([4], [9], [10]) returned third-party articles and xTiles' own blog comparisons (e.g., 'Why I Left Notion and Obsidian for xTiles', 'xTiles vs Obsidian & Miro'), which became the primary sources. The agent had to assemble the final answer from fragments across multiple external sources rather than a single authoritative, structured resource on xTiles.app.
  • ›The agent explicitly noted confusion points: the domain/service mismatch, lack of AI feature documentation, absence of competitor pricing tables on the site, and unclear enterprise tier details ([8]). These gaps indicate xTiles' own site does not comprehensively expose its positioning and pricing in machine-readable form.
  • ›The agent successfully cited sources ([7], [9], [10] fetches plus review aggregators) but 50% of source discovery came from web search, not direct site navigation — a sign that xTiles.app does not surface comparison content or detailed pricing in a way that independent agent crawling would readily uncover.

See every agent that visits xtiles.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 →