Is cardscan.site AI agent ready? A · 83/100
Why we think this is Lovable (1 signals)
- · lovable host reference in JS bundle
Scan history · 16 public scans of cardscan.site
| When | Score | Grade | Snapshot |
|---|---|---|---|
| 1 Sept 2026, 3:15 UTC356355b6 | 83/100 | A | View → |
| 5 Jul 2026, 1:00 UTC2983346e | 89/100 | A | View → |
| 4 Jul 2026, 0:00 UTCf2b0840b | 89/100 | A | View → |
| 2 Jul 2026, 23:00 UTC63a5ff13 | 89/100 | A | View → |
| 1 Jul 2026, 22:00 UTCa8d6359a | 89/100 | A | View → |
| 30 Jun 2026, 21:00 UTCfffe4e2a | 89/100 | A | View → |
| 29 Jun 2026, 20:14 UTCff6255d6 | 89/100 | A | View → |
| 25 Jun 2026, 6:56 UTCf4fdb0d6 | 89/100 | A | View → |
| 24 Jun 2026, 14:12 UTC94327fa2 | 66/100 | B | View → |
| 24 Jun 2026, 14:12 UTC297c44b2 | 66/100 | B | View → |
| 24 Jun 2026, 13:36 UTC19ed3334 | 66/100 | B | View → |
| 24 Jun 2026, 13:20 UTC5dff6f03 | 66/100 | B | View → |
| 24 Jun 2026, 13:20 UTC435ecb25 | 66/100 | B | View → |
| 24 Jun 2026, 13:16 UTC93280036 | 66/100 | B | View → |
| 23 Jun 2026, 11:49 UTCe3f1d1d7 | 71/100 | B | View → |
| 23 Jun 2026, 10:49 UTC56f1111b | 71/100 | B | View → |
1 failed · 2 partial out of 14 that apply to your site.
Fix automatically with AIScan
5 open checks (1 failing) can be handed to an AI agent: B3, P2, M4, E1, 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://cardscan.site/”.
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://cardscan.site/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fcardscan.site%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://cardscan.site/. 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.
- 02Partial+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.
- 03Partial+1 pts if fixed
HTTPS & canonical host
See full detailsServe 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.
You are helping me raise my AIScan.site agent-readiness score.
Site: https://cardscan.site/
Platform: lovable (70% confidence)
AIScan score: 83/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://cardscan.site/pricing (price, priceCurrency, price 0 only — paid plans not described): { "@context": "https://schema.org", "@type": "WebApplication", "name": "CardScan", "url": "https://cardscan.site", "description": "AI-powered business card scanner that converts ca
- 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.
- **[P2] MCP Server Card** — PARTIAL
- Evidence: HTTP 200
- Fix: Optional: publish /.well-known/mcp/server-card.json if you expose an MCP server.
- **[E1] Correct 404 handling** — FAIL
- Evidence: GET /aiscan-404-probe-wdpnp1 → HTTP 200 (soft 404 — returns 200 for a missing page), 11658 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.
- **[E4] HTTPS & canonical host** — PARTIAL
- Evidence: final origin https://cardscan.site · http:// upgrades to https · www.cardscan.site serves its own copy (duplicate origin) · no HSTS header
- 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.
- **[B3] Web Bot Auth key directory** — PARTIAL
- Evidence: HTTP 200
- Fix: Optional: serve a JWKS-style key directory at /.well-known/http-message-signatures-directory.
### 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 (2): 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-wdpnp1 → HTTP 200 (soft 404 — returns 200 for a missing page), 11658 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
100Can agents read your content cleanly? Markdown, structured data.
Bot Access
85Are AI crawlers explicitly allowed or blocked?
Capabilities
84Can agents do things? APIs, auth, MCP, Agent Skills.
Commerce
73Can agents transact? Catalogs, checkout, agentic commerce.
Share as a social image
Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.
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.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of cardscan.site on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fcardscan.site%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade A (83/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=83&grade=A&host=cardscan.site" alt="AIScan.site Grade A — 83/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fcardscan.site%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Dig deeper
cardscan.site 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 cardscan.site.