Agent-readiness report: fastsocialz.com — A
Why we think this is Lovable (2 signals)
- · CSP allowlists Lovable origin
- · 'lovable' string in JS bundle
1 failed out of 14 that apply to your site.
Quick Wins
Top 1 fixes ranked by score impact
- 01Fail+6 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://fastsocialz.com/ Platform: lovable (99% confidence) AIScan score: 87/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** — FAIL - Evidence: no JSON-LD Offer found on /pricing or the homepage - 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. ### 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 (7): B1, 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
100Can agents find your pages? robots, sitemaps, llms.txt.
Content
100Can agents read your content cleanly? Markdown, structured data.
Bot Access
100Are AI crawlers explicitly allowed or blocked?
Capabilities
100Can agents do things? APIs, auth, MCP, Agent Skills.
Commerce
0Can agents transact? Catalogs, checkout, agentic commerce.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · M4
What we foundno JSON-LD Offer found on /pricing or the homepage
Measured againstHow to fix itPublish 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.
⚡ Fix automatically with AIScan
Option A — Agent Skill (any agent runtime)
Install the AIScan skill in one command:
```
npx add-skill https://aiscan.site/aiscan-skill.json
```
Or download it directly: https://aiscan.site/aiscan-skill.json
Then ask your agent: "Fix the failing AI readiness checks for <your-url>"Option B — Claude Code skill (CLAUDE.md)
- Download
CLAUDE.mdfrom https://aiscan.site/CLAUDE.md and place it in your project root. - Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.
Option C — MCP (Claude Desktop, Cursor, or any MCP client)
- Endpoint:
https://aiscan.site/api/mcp - Tools:
scan_website,get_fixes,get_grade - Call
get_fixeswith your URL for machine-readable fix instructions.
Option D — REST API
```
GET https://aiscan.site/api/public/scan?url=YOUR_URL
```
Returns the full report with all checks and fix details.Re-scan at https://aiscan.site to verify after applying fixes.
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.Add Offer JSON-LD to your pricing page
One block per plan (or one AggregateOffer covering the range) so an agent can answer "what does this cost?" without reading prose.
Example
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Product", "name": "Pro", "offers": { "@type": "Offer", "price": "12.00", "priceCurrency": "USD", "priceSpecification": { "@type": "UnitPriceSpecification", "price": "12.00", "priceCurrency": "USD", "billingDuration": 1, "billingIncrement": 1, "unitCode": "MON" }, "availability": "https://schema.org/InStock", "url": "https://example.com/pricing" } } </script>Keep it truthful
The structured price must match the price a human sees; agents will quote it.
Verify
After deploying, re-scan at https://aiscan.site. You can also test with
curl -Iorcurldirectly.- Download
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of fastsocialz.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Ffastsocialz.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade A (87/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=87&grade=A&host=fastsocialz.com" alt="AIScan.site Grade A — 87/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Ffastsocialz.com%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Dig deeper
Automate your AI-readiness
Plug AIScan into your agent stack or chat with it on the go.
Scan your own site
Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.