Is zakatcal.lovable.app AI agent ready? A · 84/100

zakatcal.lovable.app

Lovable · 99% confidence
https://zakatcal.lovable.app/
A84 / 100
Grade A · Level 4InteractiveExcellent — agents can find, read, and act on your site.
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.

Add to Claude
4 checks need fixing

2 failed · 2 partial out of 14 that apply to your site.

See top fixes

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.

Option A — Agent Skill (any runtime)
npx add-skill https://aiscan.site/aiscan-skill.json

Then ask your agent: “Fix the failing AI readiness checks for https://zakatcal.lovable.app/”.

Option B — Claude Code (CLAUDE.md)
curl -o CLAUDE.md https://aiscan.site/CLAUDE.md

Drop it in your project root, then ask Claude Code to fix the failing AIScan checks.

Option C — MCP client
https://aiscan.site/api/mcp

Tools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://zakatcal.lovable.app/" }.

Option D — REST API
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

    Correct 404 handling

    +4 pts if fixed

    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.

    See full details
  • 02Fail

    Heading hierarchy & server-rendered text

    +4 pts if fixed

    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.

    See full details
  • 03Partial

    Machine-readable pricing

    +3 pts if fixed

    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.

    See full details
Hand-off prompt for your coding agent4 issues
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.

Essential
25 / 37 pts

Baseline every site should meet.

Recommended
28 / 28 pts

Strong signals most sites benefit from.

Bonus earned
1 signal

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

76

Can agents find your pages? robots, sitemaps, llms.txt.

311
  • 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 found

    GET /aiscan-404-probe-pcnd5r → HTTP 200 (soft 404 — returns 200 for a missing page), 5114 bytes, text/html

    How to fix it

    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.

    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 the public/ folder — they're served from the site root automatically.

    Return a real 404 status

    A missing page must answer 404 (or 410), never 200. 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

82

Can agents read your content cleanly? Markdown, structured data.

31
  • 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 found

    47 words of server-rendered text, 0 <h2>, 0 <h3>

    How to fix it

    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.

    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 the public/ 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

100

Are AI crawlers explicitly allowed or blocked?

2

Capabilities

100

Can agents do things? APIs, auth, MCP, Agent Skills.

3

Commerce

50

Can agents transact? Catalogs, checkout, agentic commerce.

1
Share the result

Share as a social image

Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.

AIScan share card — zakatcal.lovable.app graded A

Tip: for X and LinkedIn, upload the downloaded PNG with your post so the card shows in the feed. Posts that include just the link will still preview AIScan.site.

Showcase your grade

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 grade A
HTML
<!-- 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>
Markdown
[![AIScan.site Grade A — 84/100](https://aiscan.site/api/public/badge.svg?score=84&grade=A&host=zakatcal.lovable.app)](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

Scan any site from Telegram
Open in Telegram
Free · No signup · ~20 seconds

Scan your own site

Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.

Or browse the community feed to see what others have scanned.