easyquran.fyi
partial
Claude Code
intent
What does easyquran.fyi do and who is it for? Explain it back to me.
27steps
143.7sduration
$1.6670cost
717,632tokens
34 steps7 reasoning steps12 searches
home
docs
docs
/features
/reader
/help
docs
search
search
search
/hmziqrs
search
search
search
search
/item
search
search
robots.txt
sitemap
/faq
/contact
/api/quran
search
.well-known
search
search
93%
on-site discovery
53%
reliability
60%
link following
path origin
- previous resource60%
- web search7%
- prior knowledge33%
insight
The agent partially completed the task by identifying EasyQuran's core value proposition (free, ad-free, minimal Quran reader) and multi-language support from the web manifest and sitemap, but could not fully explain differentiation from alternatives or confirm specific features because the site uses client-side rendering that hides content from server-side inspection and is intentionally hidden from search engines. The site's architecture and deliberate discoverability restrictions made it difficult to extract complete information.
- ›Step [29] (manifest.webmanifest) was the single most valuable content-bearing resource, providing the exact tagline ('Read the Quran. Free, no ads, and fast — nothing in the way of the text') and app structure (/app, /app/juz shortcuts) that anchored the entire answer.
- ›Step [22] (sitemap.xml) revealed multi-language support (25+ languages via hreflang alternates) and site structure, but the actual page content at those URLs was unreachable because pages are JavaScript-rendered—HTML fetches returned empty script-heavy shells without visible text.
- ›Steps [1], [3], [24], [25] were fetched but returned only HTML scaffolding with localStorage initialization and no readable DOM content, making the FAQ, About, and Contact pages functionally invisible to server-side inspection despite being listed in the sitemap.
- ›Steps [2], [4], [6], [7], [8], [27] returned 404s for common route guesses (/pricing, /features, /reader, /help, /docs, /api/quran), indicating the site either has minimal structure or deliberately removes these paths.
- ›Step [21] (robots.txt) showed the site allows crawling ('Disallow:' is empty) but does not opt into indexing—an unusual signal that contradicts typical discoverability, suggesting the creator intentionally keeps the project under-the-radar.
- ›Web searches [10–20], [28], [31–32] consistently returned results for different 'Easy Quran' products (easyquran.app, easyquran.ai, mobile apps) but almost nothing for easyquran.fyi itself, confirming the site has virtually no public presence or documentation.
- ›The site is agent-hostile: it uses a modern SvelteKit stack that requires JavaScript execution to render content, deliberately hides itself from search engines, has no pricing/features/docs pages, and provides no public API or structured data beyond the manifest—forcing the agent to assemble its answer from fragments (manifest + sitemap metadata + prior knowledge of Quran reader space).
Help the next agent finish on easyquran.fyi
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 →