The agent successfully assembled a comprehensive explanation of ListMySaaS by combining fragments from the site's llms.txt artifact (which provided core positioning), a comparison page fetched directly, an external review site, and a third-party SaaS directory guide. The site's heavy reliance on client-side rendering made most pages inaccessible as structured content; the agent worked around this by finding the llms.txt file and supplementing with web search and prior knowledge.

• ›Step [11] (llms.txt) was the primary content-bearing resource from the site itself—a machine-readable summary that clearly stated ListMySaaS's value prop ('free SaaS directory for founders, makers, and indie hackers'), positioning vs. competitors (BetaList, Product Hunt), and key features (dofollow links, verified badges). This artifact is agent-optimized and surfaced the most directly useful information.
• ›Steps [1], [3], [5], [9], [14], [16] returned HTML rendered by Next.js with no visible text content in the responses—the agent could not extract pricing, FAQs, or methodology details from the site's own pages due to client-side rendering. The agent explicitly noted this limitation in its final answer ('couldn't fully access the actual content').
• ›Steps [15] (vs/betalist comparison page) and [21] (external SaaS guide) and [24] (third-party review) provided contextual and comparative information, but the site's own comparison page [15] was also client-side rendered and did not yield extractable text. The agent had to rely on external sources and prior knowledge (46% of fetches) to fill gaps the site left inaccessible.
• ›The agent could not confirm exact pricing tiers or all plan features from the site itself; it inferred '$19 Premium' and 'Submission Service' details from search results and external reviews rather than from listmysaas.xyz's own pricing page, indicating the site does not publish pricing in a machine-readable or easily scrapable form.
• ›The site is poorly optimized for agent discovery of key business information: pricing is gated behind client-side rendering, comparison pages are not text-accessible, and the only truly agent-ready artifact is llms.txt. The FAQ and methodology pages existed but were unreachable as text.