Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 70 out of 100
- Agent Ease of Use 43 out of 100
- Security & Trust 45 out of 100
- GEO, AIO and AEO 65 out of 100
- SEO 69 out of 100
- Performance 69 out of 100
- Accessibility 7 out of 100
What AI sees of your website
Lanterncrm - My blog about spying
My blog about spying
Next step
Turn this report into a fix workflow
1 failed check is 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 | 70 | Needs work | 32 | 1 | 0 | View details |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 74 | Needs work | 20 | 1 | 0 | View details |
| Bot Access Control | 69 | Needs work | 4 | 0 | 0 | |
| Agent Ease of Use | 43 | Priority fix | 0 | 1 | 0 | View details |
| Google Agentic Browsing | 12 | Priority fix | 0 | 1 | 0 | View details |
| GEO, AIO and AEO | 65 | Needs work | 10 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| SEO | 69 | Needs work | 9 | 0 | 0 | |
| SEO | 69 | Needs work | 9 | 0 | 0 | |
| Security & Trust | 45 | Priority fix | 7 | 0 | 0 | |
| Security & Trust | 45 | Priority fix | 7 | 0 | 0 | |
| Performance | 69 | Needs work | 9 | 1 | 0 | View details |
| Performance | 69 | Needs work | 9 | 1 | 0 | View details |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
0 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: dateModified (2022-01-18T16:35:31+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00).; dateModified (2022-01-18T16:28:55+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00).; dateModified (2022-01-18T16:44:01+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00).; dateModified (2022-01-18T15:09:12+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00)..
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
100/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
Check date validity and consistency
dateModified (2022-01-18T16:35:31+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00).; dateModified (2022-01-18T16:28:55+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00).; dateModified (2022-01-18T16:44:01+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00).; dateModified (2022-01-18T15:09:12+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00).
Freshness dates are invalid or inconsistent
Evidence log1 step · 4 lines
Check date validity and consistency [fail]! dateModified (2022-01-18T16:35:31+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00).; dateModified (2022-01-18T16:28:55+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00).; dateModified (2022-01-18T16:44:01+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00).; dateModified (2022-01-18T15:09:12+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00).INFOCheck date validity and consistencyINFOChecking collected freshness dates for invalid values, future dates, and inconsistent orderingFAILCheck critical freshness issue count actual=4 expected=0 warningIssueCount=0 issues=[{"severity":"fail","message":"dateModified (2022-01-18T16:35:31+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00)."},{"severity":"fail","message":"dateModified (2022-01-18T16:28:55+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00)."},{"severity":"fail","message":"dateModified (2022-01-18T16:44:01+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00)."},{"severity":"fail","message":"dateModified (2022-01-18T15:09:12+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00)."}]FAILInvalid freshness date issue found issues=["dateModified (2022-01-18T16:35:31+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00).","dateModified (2022-01-18T16:28:55+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00).","dateModified (2022-01-18T16:44:01+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00).","dateModified (2022-01-18T15:09:12+00:00) is earlier than datePublished (2022-06-11T08:32:48+00:00)."]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."
}PerformancePerformanceBrowser audit
Avoid large layout shifts
100 Fail
PerformancePerformanceBrowser audit
Avoid large layout shifts
Check name
Avoid large layout shifts
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
2 layout shifts found
Fix guidance
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls). [Learn how to improve CLS](https://web.dev/articles/optimize-cls)
References
web.dev/learn/performanceEvidence
{
"displayValue": "2 layout shifts found",
"description": "These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls). [Learn how to improve CLS](https://web.dev/articles/optimize-cls)"
}Sign in to see 46 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