Is zakatcal.lovable.app AI agent ready? A · 84/100
Why we think this is Lovable (2 signals)
- · host: zakatcal.lovable.app
- · 'lovable' string in JS bundle
Fix this with Claude
Add the AIScan connector and ask Claude to walk you through each failing check for this site.
Scan history · 5 public scans of zakatcal.lovable.app
2 failed · 2 partial out of 14 that apply to your site.
Fix automatically with AIScan
4 open checks (2 failing) can be handed to an AI agent: M4, E1, E3, E4. Pick one route — each returns the full, check-by-check instructions.
npx add-skill https://aiscan.site/aiscan-skill.jsonThen ask your agent: “Fix the failing AI readiness checks for https://zakatcal.lovable.app/”.
curl -o CLAUDE.md https://aiscan.site/CLAUDE.mdDrop it in your project root, then ask Claude Code to fix the failing AIScan checks.
https://aiscan.site/api/mcpTools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://zakatcal.lovable.app/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fzakatcal.lovable.app%2F'Returns every check with its complete fix guide.
Verify: Re-scan at https://aiscan.site after applying fixes, or run npx aiscan-cli https://zakatcal.lovable.app/. Individual checks that need a specific probe list it in their own guide.
Quick Wins
Top 3 fixes ranked by score impact
- 01Fail+4 pts if fixed
Correct 404 handling
See full detailsReturn a real HTTP 404 (not 200) for missing pages, with a body that names the site and links to your homepage, sitemap, and search so an agent can recover.
- 02Fail+4 pts if fixed
Heading hierarchy & server-rendered text
See full detailsServer-render your main copy and break it into a real heading outline (one h1, then descriptive h2/h3 sections). Agents that don't execute JavaScript only see the HTML you ship.
- 03Partial+3 pts if fixed
Machine-readable pricing
See full detailsPublish schema.org Offer / AggregateOffer JSON-LD on your pricing page with price, priceCurrency and the billing period, so an agent can answer "what does this cost?" without scraping prose.
You are helping me raise my AIScan.site agent-readiness score.
Site: https://zakatcal.lovable.app/
Platform: lovable (99% confidence)
AIScan score: 84/100 — Level 4 (Interactive)
Rubric: v2026.08.2
Please implement the fixes below. Where a file already exists (e.g. `public/robots.txt`, `public/llms.txt`), edit it; otherwise create it. After each change, briefly explain what you did so I can verify in the next scan.
### Failing checks
- **[M4] Machine-readable pricing** — PARTIAL
- Evidence: JSON-LD offer on https://zakatcal.lovable.app/pricing (price, priceCurrency, price 0 only — paid plans not described): { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://zakatcal.com/#org", "name": "ZakatCal.com", "url": "https://zakatcal.com", "logo": "https
- Fix: Publish schema.org Offer / AggregateOffer JSON-LD on your pricing page with price, priceCurrency and the billing period, so an agent can answer "what does this cost?" without scraping prose.
- **[E1] Correct 404 handling** — FAIL
- Evidence: GET /aiscan-404-probe-pcnd5r → HTTP 200 (soft 404 — returns 200 for a missing page), 5114 bytes, text/html
- Fix: Return a real HTTP 404 (not 200) for missing pages, with a body that names the site and links to your homepage, sitemap, and search so an agent can recover.
- **[E3] Heading hierarchy & server-rendered text** — FAIL
- Evidence: 47 words of server-rendered text, 0 <h2>, 0 <h3>
- Fix: Server-render your main copy and break it into a real heading outline (one h1, then descriptive h2/h3 sections). Agents that don't execute JavaScript only see the HTML you ship.
- **[E4] HTTPS & canonical host** — PARTIAL
- Evidence: final origin https://zakatcal.lovable.app · http:// upgrades to https · www.zakatcal.lovable.app serves its own copy (duplicate origin) · HSTS set
- Fix: Serve the site over HTTPS, 301-redirect http:// to https://, and redirect the www/apex variant to a single canonical host so agents don't index two copies of every URL.
### Constraints
- Do not change visible UI or copy.
- Keep changes additive and reversible.
- Prefer static files in `public/` over server routes when possible.
- For `llms.txt`, generate a real index of the site's most important pages.
How this score is calculated
Every check earns points against a weight. We divide the points you earned by the points that actually apply to a Lovable — so checks that don't apply never drag you down.
Baseline every site should meet.
Strong signals most sites benefit from.
Emerging standards. Can only add points.
Not counted (6): B3, P2, P3, M1, M3, E5 — either not applicable to this site profile or optional and not yet adopted. Expand any check to see the exact evidence we based it on.
Discoverability
76Can agents find your pages? robots, sitemaps, llms.txt.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · E1
What we foundGET /aiscan-404-probe-pcnd5r → HTTP 200 (soft 404 — returns 200 for a missing page), 5114 bytes, text/html
Measured againstHow to fix itReturn a real HTTP 404 (not 200) for missing pages, with a body that names the site and links to your homepage, sitemap, and search so an agent can recover.
This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like
robots.txt,llms.txt, and.well-known/*belong in thepublic/folder — they're served from the site root automatically.Return a real 404 status
A missing page must answer
404(or410), never200. A soft 404 makes agents index your error page as real content.Make the body recoverable
The 404 body should name the site and link to the homepage, sitemap, docs, and search so an agent can find its way back instead of dead-ending.
Verify
curl -sI https://yoursite.com/this-page-does-not-exist-123 | head -n 1
Content
82Can agents read your content cleanly? Markdown, structured data.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · E3
What we found47 words of server-rendered text, 0 <h2>, 0 <h3>
Measured againstHow to fix itServer-render your main copy and break it into a real heading outline (one h1, then descriptive h2/h3 sections). Agents that don't execute JavaScript only see the HTML you ship.
This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like
robots.txt,llms.txt, and.well-known/*belong in thepublic/folder — they're served from the site root automatically.Server-render your main copy
Agents that don't execute JavaScript see only the HTML you ship. Aim for at least 150 words of real, server-rendered text on the homepage.
Use a real heading outline
One
<h1>for the page topic, then descriptive<h2>sections and<h3>sub-sections. Don't fake headings with styled<div>s.Verify what a crawler sees
curl -s https://yoursite.com/ | sed 's/<[^>]*>/ /g' | tr -s ' ' | head -c 800
Bot Access
100Are AI crawlers explicitly allowed or blocked?
Capabilities
100Can agents do things? APIs, auth, MCP, Agent Skills.
Commerce
50Can agents transact? Catalogs, checkout, agentic commerce.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of zakatcal.lovable.app on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fzakatcal.lovable.app%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade A (84/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=84&grade=A&host=zakatcal.lovable.app" alt="AIScan.site Grade A — 84/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fzakatcal.lovable.app%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Dig deeper
zakatcal.lovable.app is built on Lovable. AI-agent readiness for Lovable apps walks through the same checks on that platform.
This page always shows the most recent public scan for zakatcal.lovable.app.