Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 54 out of 100
- Agent Ease of Use 54 out of 100
- Security & Trust 62 out of 100
- GEO, AIO and AEO 65 out of 100
- SEO 92 out of 100
- Performance 64 out of 100
- Accessibility 0 out of 100
What AI sees of your website
Health and Wellness Credit Card - CareCredit
The CareCredit credit card can help pay for health, wellness, and medical costs with special financing options. Learn how it works and apply today!
Next step
Turn this report into a fix workflow
2 failed checks are ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.
| Metric | Score | Status | Passed | Failed | Warning | Evidence |
|---|---|---|---|---|---|---|
| AI Discoverability | 54 | Needs work | 22 | 2 | 1 | View details |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 52 | Needs work | 13 | 1 | 1 | View details |
| Bot Access Control | 45 | Priority fix | 1 | 1 | 0 | View details |
| Agent Ease of Use | 54 | Needs work | 4 | 1 | 0 | View details |
| API | 67 | Needs work | 1 | 0 | 0 | |
| Auth | 48 | Priority fix | 1 | 0 | 0 | |
| Skill Discovery | 54 | Needs work | 1 | 0 | 0 | |
| Google Agentic Browsing | 50 | Needs work | 1 | 1 | 0 | View details |
| GEO, AIO and AEO | 65 | Needs work | 8 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| Security & Trust | 62 | Needs work | 14 | 0 | 0 | |
| Security & Trust | 62 | Needs work | 14 | 0 | 0 | |
| Performance | 64 | Needs work | 11 | 0 | 0 | |
| Performance | 64 | Needs work | 11 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
69 Fail
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
Needs attention
AI bot rules in robots.txt
Issue
No explicit User-agent rules were found for major AI crawler tokens.
Details
Why it matters
AI crawler product tokens have different meanings. Explicit robots.txt groups make training, search, and retrieval access policy auditable for compliant crawler operators.
Check name
AI bot rules in robots.txt
Score
31/100
Status
fail
Category
Bot Access Control
Maturity
Established
Goal
Declare deliberate robots.txt rules for major AI training, AI search, user-triggered, and dataset crawlers.
Result
AI bot rules in robots.txt failed at "Classify AI crawler rules".
Validation steps
Classify AI crawler rules
No explicit User-agent rules were found for major AI crawler tokens.
robots.txt lacks explicit AI crawler rules
Evidence log1 step · 6 lines
Classify AI crawler rules [fail]! No explicit User-agent rules were found for major AI crawler tokens.INFOClassify AI crawler rulesINFOParsing User-agent groups and Allow/Disallow records for known AI crawler tokens evaluatedPath="/"INFOEvaluating exact User-agent matches before wildcard fallback exactAiPolicyCount=0 totalCrawlerTokens=18FAILNo explicit AI crawler User-agent groups were found examplesExpected=["GPTBot","OAI-SearchBot","ClaudeBot","Google-Extended","CCBot"]FAILCompare explicit AI crawler coverage actual=0 expected="> 0 explicit non-search AI crawler policies" missingTokens=["GPTBot","OAI-SearchBot","ChatGPT-User","ClaudeBot","Claude-SearchBot","Claude-User","Google-Extended","Applebot-Extended","Amazonbot","Amzn-SearchBot","Amzn-User","PerplexityBot"]INFOResolved effective root-path policy for crawler tokens blocked=0 allowed=21 unspecified=0AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
33 Fail
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
Needs attention
Content freshness signals
Issue
Content freshness signals are invalid: json-ld datePublished is not a parseable date ().; json-ld dateModified is not a parseable date ()..
Details
Why it matters
Freshness signals help agents, crawlers, and search systems decide whether content is current enough to cite, summarize, cache, or compare against newer sources.
Check name
Content freshness signals
Score
67/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Expose modified and published dates for freshness-aware retrieval, citation, and ranking.
Result
Content freshness signals is missing or incomplete.
Validation steps
Validate structured freshness dates
No Schema.org freshness dates were found.
Structured freshness dates are missing or invalid
Check date validity and consistency
json-ld datePublished is not a parseable date ().; json-ld dateModified is not a parseable date ().
Freshness dates are invalid or inconsistent
Evidence log2 steps · 8 lines
Validate structured freshness dates [warning]! No Schema.org freshness dates were found.INFOValidate structured freshness datesINFOCollecting Schema.org freshness dates from JSON-LD, Microdata, and RDFaWARNCheck structured freshness date count actual=2 expected="> 0" invalidDateCount=2 formats={"json-ld":2} alternateDates=[{"source":"http","channel":"header","property":"Last-Modified","value":"Thu, 02 Jul 2026 21:08:34 GMT","parsed":"2026-07-02T21:08:34.000Z","location":"HTTP response header: Last-Modified"},{"source":"sitemap","channel":"sitemap","property":"lastmod","value":"2019-12-17T12:29:37+00:00","parsed":"2019-12-17T12:29:37.000Z","location":"matching sitemap <lastmod> entry for this page URL"}]WARNStructured freshness dates include invalid values invalidDateCount=2Check date validity and consistency [fail]! json-ld datePublished is not a parseable date ().; json-ld dateModified is not a parseable date ().INFOCheck date validity and consistencyINFOChecking collected freshness dates for invalid values, future dates, and inconsistent orderingFAILCheck critical freshness issue count actual=2 expected=0 warningIssueCount=0 issues=[{"severity":"fail","message":"json-ld datePublished is not a parseable date ()."},{"severity":"fail","message":"json-ld dateModified is not a parseable date ()."}]FAILInvalid freshness date issue found issues=["json-ld datePublished is not a parseable date ().","json-ld dateModified is not a parseable date ()."]
Agent Ease of UseGoogle Agentic BrowsingBrowser audit
Accessibility tree is not well-formed
100 Fail
Agent Ease of UseGoogle Agentic BrowsingBrowser audit
Accessibility tree is not well-formed
Check name
Accessibility tree is not well-formed
Score
0/100
Status
fail
Device
desktop
Category
Google Agentic Browsing
Fix guidance
A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page.
Evidence
{
"description": "A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page."
}Sign in to see 44 other issues and the full report
Create a free account to unlock every issue, evidence details, exports, and higher free limits.
Fix with MCP or CLI
Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.
Score history
Public scan score over time
Public reports for this website origin. Select any point or report link to open that canonical report.
| Scan date | Score | Readiness | Report |
|---|---|---|---|
| 49/100 | Level 2, Agent-Limited | Current report |