robots.txt reachable.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
Share SVG Badge
This website is not yet ready for AI search. AI Crawlability is solid, but AI Understanding needs improvement.
| Field | Value |
|---|---|
| Page title | Ezepay App |
| Meta description | Ezepay Generated Project |
| Dimension | Score | Weight |
|---|---|---|
| AI Crawlability | 16/20 | 20% |
| AI Understanding | 0/25 | 25% |
| AI Content Readiness | 1/20 | 20% |
| AI Citation Potential | 3/20 | 20% |
| Agent & Protocol Readiness | 15/25 | 25% |
| Trust & Security | 4/5 | 5% |
| Total | 39/100 | Grade: Poor |
robots.txt reachable.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
No sitemap declared.
No sitemap.xml was declared. AI crawlers cannot systematically discover all of your pages, so deeper content may remain unindexed.
GPTBot allowed in robots.txt.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
ClaudeBot allowed in robots.txt.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
Google-Extended allowed in robots.txt.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
Bytespider allowed in robots.txt.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
KimiBot allowed in robots.txt.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
No Organization/LocalBusiness schema.
No Organization / LocalBusiness schema was detected. AI engines rely on this markup to build accurate entity relationships and brand understanding, which directly affects citation quality.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Ezepay App",
"url": "https://ezepay.ai",
"logo": "https://ezepay.ai/logo.png"
}
</script>No Product schema.
No Product schema was detected. E-commerce or product content cannot be recognised and cited by AI as a structured entity, which costs you rich-result placement.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Ezepay App Product Name",
"image": ["https://ezepay.ai/logo.png"],
"description": "Brief product description",
"brand": { "@type": "Brand", "name": "Ezepay App" },
"offers": { "@type": "Offer", "priceCurrency": "USD", "price": "0" }
}
</script>
No FAQPage schema.
No FAQPage schema was detected. Common questions and answers cannot be cited directly by AI as authoritative answers, and you miss rich-result opportunities.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "Your first question?",
"acceptedAnswer": { "@type": "Answer", "text": "The authoritative answer." }
}]
}
</script>
No Article schema.
No Article schema was detected. Editorial content is less likely to be treated as an authoritative source by AI, and you miss rich-result placement.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Article title",
"author": { "@type": "Person", "name": "Author name" },
"publisher": { "@type": "Organization", "name": "Ezepay App" },
"datePublished": "2026-01-01",
"dateModified": "2026-01-01"
}
</script>
No Breadcrumb schema.
No Breadcrumb schema was detected. AI cannot infer the site hierarchy and breadcrumb relationships as easily, which affects internal-link context.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [{
"@type": "ListItem", "position": 1,
"name": "Home", "item": "https://ezepay.ai/"
},{
"@type": "ListItem", "position": 2,
"name": "Products", "item": "https://ezepay.ai/products"
}]
}
</script>
Entity fields covered: 0/11.
Brand entity coverage is insufficient. AI cannot build a complete entity profile (description, contact details, industry, sameAs social links, etc.), lowering the chance of accurate citations.
Homepage content depth: 1/5.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
No About page found.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
No Product page found.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
No FAQ page found.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
No Blog / Case page found.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
Thin content; little to cite.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
No blog or case section found.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
No author attribution detected.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
Brand entity present but not consistently surfaced.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
No authoritative external references.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
OpenAPI / Swagger descriptor found.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
MCP endpoint indicated.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
AI Actions declared.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
No API documentation link found.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
No RFC 8288 Link response header detected.
No RFC 8288 Link response header was found. Agents cannot discover your API, docs or AI feed from response headers.
No DNS-AID (SVCB/HTTPS) records detected.
No DNS-AID (SVCB/HTTPS) records were detected. Agents cannot discover your AI service endpoint directly from DNS.
No Markdown content negotiation (Accept: text/markdown) detected.
No Markdown content negotiation (Accept: text/markdown) was detected. Agents must parse HTML instead of clean Markdown.
No Content Signals directive (ai-train/search/ai-input) detected.
No Content Signals directive (ai-train / search / ai-input) was detected. You are not explicitly telling AI bots how they may use your content.
MCP Server Card exposed at .well-known/mcp/server-card.json.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
Agent Skills catalog declared (.well-known/agent-skills).
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
OAuth authorization server discovery present.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
Auth.md present for agent authentication guidance.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
Served over HTTPS.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
No contact info visible.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
HTTP status 200.
No automated fix snippet for this item — address it directly, or see Actionable Recommendations.
No Organization / LocalBusiness schema was detected. AI engines rely on this markup to build accurate entity relationships and brand understanding, which directly affects citation quality.
Dimension: AI Understanding
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Ezepay App",
"url": "https://ezepay.ai",
"logo": "https://ezepay.ai/logo.png"
}
</script>The page relies heavily on client-side rendering. With JavaScript disabled, only 2 words of visible text remain, so AI crawlers and LLM agents that do not execute JavaScript may index an empty page.
Dimension: AI Crawlability
# robots.txt — let AI crawlers see the pre-rendered version
User-agent: GPTBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: *
Allow: /
No llms.txt was found at the site root. LLMs and AI agents lack a machine-readable site guide to quickly discover key sections and entry points.
Dimension: AI Crawlability
# Ezepay App
> Ezepay App — AI-readable overview for LLMs and agents.
## Home
- [Home](https://ezepay.ai/): Main landing page for Ezepay App.
## Documentation
- [About](https://ezepay.ai/about): Company background and mission.
- [Products](https://ezepay.ai/products): Product and service overview.
- [Blog](https://ezepay.ai/blog): Insights, guides and case studies.
The homepage lacks semantic structure (header / main / article tags or a clear H1-H3 hierarchy), making it harder for AI to distinguish content, navigation and decorative elements.
Dimension: AI Understanding
<body>
<header>
<nav><!-- Site navigation --></nav>
</header>
<main>
<article>
<h1>Primary page title</h1>
<h2>Section heading</h2>
<p>Body content...</p>
</article>
</main>
<footer><!-- Footer --></footer>
</body>
Brand entity coverage is insufficient. AI cannot build a complete entity profile (description, contact details, industry, sameAs social links, etc.), lowering the chance of accurate citations.
Dimension: AI Understanding
No Product schema was detected. E-commerce or product content cannot be recognised and cited by AI as a structured entity, which costs you rich-result placement.
Dimension: AI Understanding
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Ezepay App Product Name",
"image": ["https://ezepay.ai/logo.png"],
"description": "Brief product description",
"brand": { "@type": "Brand", "name": "Ezepay App" },
"offers": { "@type": "Offer", "priceCurrency": "USD", "price": "0" }
}
</script>
No sitemap.xml was declared. AI crawlers cannot systematically discover all of your pages, so deeper content may remain unindexed.
Dimension: AI Crawlability
No RFC 8288 Link response header was found. Agents cannot discover your API, docs or AI feed from response headers.
Dimension: Agent
No Markdown content negotiation (Accept: text/markdown) was detected. Agents must parse HTML instead of clean Markdown.
Dimension: Agent
No FAQPage schema was detected. Common questions and answers cannot be cited directly by AI as authoritative answers, and you miss rich-result opportunities.
Dimension: AI Understanding
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "Your first question?",
"acceptedAnswer": { "@type": "Answer", "text": "The authoritative answer." }
}]
}
</script>
No Article schema was detected. Editorial content is less likely to be treated as an authoritative source by AI, and you miss rich-result placement.
Dimension: AI Understanding
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Article title",
"author": { "@type": "Person", "name": "Author name" },
"publisher": { "@type": "Organization", "name": "Ezepay App" },
"datePublished": "2026-01-01",
"dateModified": "2026-01-01"
}
</script>
No DNS-AID (SVCB/HTTPS) records were detected. Agents cannot discover your AI service endpoint directly from DNS.
Dimension: Agent
No Breadcrumb schema was detected. AI cannot infer the site hierarchy and breadcrumb relationships as easily, which affects internal-link context.
Dimension: AI Understanding
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [{
"@type": "ListItem", "position": 1,
"name": "Home", "item": "https://ezepay.ai/"
},{
"@type": "ListItem", "position": 2,
"name": "Products", "item": "https://ezepay.ai/products"
}]
}
</script>
No Content Signals directive (ai-train / search / ai-input) was detected. You are not explicitly telling AI bots how they may use your content.
Dimension: Agent
63 public reports