The agent successfully synthesized an explanation of Strikingly's purpose, pricing, and positioning by combining direct site fetches with third-party review searches. The strikingly.com domain itself is poorly navigable for agents—key informational pages (/about, /features) redirect to inaccessible subdomains, and the homepage and pricing pages returned heavily JavaScript-obfuscated HTML with minimal plaintext content. The agent had to rely on prior knowledge and external search results to construct most of the final answer.

• ›Step [1] (homepage) and step [2] (pricing) returned valid 200 responses but contained mostly JavaScript configuration and no readable feature/pricing data in the HTML payload—agent could not extract concrete pricing tiers or differentiators from these pages alone.
• ›Steps [3], [4], [5], [6] (about/features pages) returned 404 redirects to about.mystrikingly.com and features.mystrikingly.com, both of which failed with 403 CloudFront blocks. This completely blocked access to Strikingly's official positioning and feature documentation.
• ›Steps [10], [11], [12] (web searches) were content-bearing: search results linked to third-party review sites (olitt.com, websitebuilderexpert.com, forbes.com, findstack.com, litextension.com) that contained the pricing tiers, feature comparisons, and competitive positioning. The agent cited all three search queries' result links in the final source list, indicating reliance on aggregator content rather than primary sources.
• ›The site is extremely agent-unfriendly: it requires JavaScript rendering to display content, has no plaintext /pricing page, blocks access to /about and /features, and provides no structured data (JSON-LD, microdata) in the HTML head that would let agents parse the offering.
• ›The agent explicitly disclosed accessibility gaps (inability to reach about/features pages, unclear e-commerce details, missing enterprise tier documentation), which were real navigation failures rather than knowledge gaps.