Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 63 out of 100
- Agent Ease of Use 61 out of 100
- Security & Trust 85 out of 100
- GEO, AIO and AEO 55 out of 100
- SEO 77 out of 100
- Performance 59 out of 100
- Accessibility 29 out of 100
What AI sees of your website
Center for Digital Government
No page metadata or readable excerpt was captured.
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 | 63 | Needs work | 28 | 3 | 1 | View details |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 44 | Priority fix | 15 | 3 | 1 | View details |
| Bot Access Control | 75 | Mostly ready | 5 | 0 | 0 | |
| Agent Ease of Use | 61 | Needs work | 8 | 1 | 2 | View details |
| API | 70 | Needs work | 6 | 1 | 2 | View details |
| Google Agentic Browsing | 86 | Mostly ready | 2 | 0 | 0 | |
| GEO, AIO and AEO | 55 | Needs work | 6 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| SEO | 77 | Mostly ready | 7 | 0 | 0 | |
| SEO | 77 | Mostly ready | 7 | 0 | 0 | |
| Security & Trust | 85 | Mostly ready | 22 | 0 | 0 | |
| Security & Trust | 85 | Mostly ready | 22 | 0 | 0 | |
| Performance | 59 | Needs work | 9 | 1 | 0 | View details |
| Performance | 59 | 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.
100 Fail
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
Needs attention
Content freshness signals
Issue
Content freshness signals are incomplete: missing any valid freshness date in Last-Modified, Schema.org, Open Graph, Dublin Core, generic meta, or sitemap lastmod.
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
0/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 Last-Modified header
No valid Last-Modified HTTP header was found.
Last-Modified freshness signal is missing or invalid
Validate structured freshness dates
No Schema.org freshness dates were found.
Structured freshness dates are missing or invalid
Validate metadata freshness dates
No Open Graph, Dublin Core, or generic meta freshness date was found.
Metadata freshness dates are missing or invalid
Corroborate with sitemap lastmod
Add a sitemap entry with a valid lastmod for the canonical page URL when sitemap corroboration is useful.
Sitemap lastmod corroboration is missing
Evidence log4 steps · 16 lines
Validate Last-Modified header [fail]! No valid Last-Modified HTTP header was found.INFOValidate Last-Modified headerINFOReading Last-Modified response headerFAILCheck Last-Modified header is present and parseable actual="missing" expected="valid" alternateDates=[]FAILLast-Modified header is missing or invalidValidate structured freshness dates [fail]! No Schema.org freshness dates were found.INFOValidate structured freshness datesINFOCollecting Schema.org freshness dates from JSON-LD, Microdata, and RDFaFAILCheck structured freshness date count actual=0 expected="> 0" invalidDateCount=0 formats={} alternateDates=[]FAILNo structured freshness dates foundValidate metadata freshness dates [fail]! No Open Graph, Dublin Core, or generic meta freshness date was found.INFOValidate metadata freshness datesINFOCollecting Open Graph, Dublin Core, and generic meta freshness datesFAILCheck metadata freshness date count actual=0 expected="> 0" metaDateCount=0 invalidDateCount=0 alternateDates=[]FAILNo metadata freshness dates foundCorroborate with sitemap lastmod [warning]INFOCorroborate with sitemap lastmodINFODiscovering sitemap candidates and matching the scanned page URL candidateCount=1 attempts=6WARNCheck matching sitemap lastmod actual="no match" expected="valid match when available" robotsStatusCode=200WARNNo matching sitemap lastmod found after sitemap attempts attempts=6
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog targets".
27 Fail
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog targets".
Needs attention
API Catalog
Issue
API catalog target https://www.govtech.com/sitemap.xml (item) advertised application/xml but returned text/xml;charset=UTF-8.
Details
Why it matters
API catalogs help agents find API endpoints, service descriptions, documentation, status resources, auth metadata, and related machine-readable contracts without guessing entry points.
Check name
API Catalog
Score
73/100
Status
fail
Category
API
Maturity
Established
Goal
Publish an API catalog for automated public API discovery using RFC 9727 when this origin exposes public APIs.
Result
API Catalog failed at "Validate API catalog targets".
Validation steps
Check API catalog HEAD Link header
HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".
API catalog HEAD Link discovery is incomplete
Validate API catalog media type
The API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter.
API catalog media type is not application/linkset+json
Validate API catalog targets
API catalog target https://www.govtech.com/sitemap.xml (item) advertised application/xml but returned text/xml;charset=UTF-8.
API catalog targets are unreachable or media types mismatch
Evidence log3 steps · 16 lines
Check API catalog HEAD Link header [warning]! HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".INFOCheck API catalog HEAD Link headerINFOSend HEAD request to API catalog path attempted=true statusCode=200 contentType="application/linkset+json;charset=UTF-8"WARNCompare HEAD Link rel=api-catalog count actual=0 expected="> 0"WARNHEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog". status="warning"Validate API catalog media type [warning]! The API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter.INFOValidate API catalog media typeWARNCompare API catalog media type actual="application/linkset+json;charset=UTF-8" expected="application/linkset+json"WARNCompare RFC 9727 profile parameter actual=false expected=trueWARNThe API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter. status="warning"Validate API catalog targets [fail]! API catalog target https://www.govtech.com/sitemap.xml (item) advertised application/xml but returned text/xml;charset=UTF-8.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsPASSAPI catalog target is reachable rel="service-desc" href="https://www.govtech.com/.well-known/openapi.json" statusCode=200 contentType="application/openapi+json;charset=UTF-8" advertisedType="application/openapi+json"PASSAPI catalog target is reachable rel="service-doc" href="https://www.govtech.com/robots.txt" statusCode=200 contentType="text/plain" advertisedType="text/plain"FAILAPI catalog target failed validation rel="item" href="https://www.govtech.com/sitemap.xml" statusCode=200 contentType="text/xml;charset=UTF-8" advertisedType="application/xml" typeMatches=falsePASSAPI catalog target is reachable rel="item" href="https://www.govtech.com/llms.txt" statusCode=200 contentType="text/markdown;charset=utf-8" advertisedType="text/markdown"FAILCompare API catalog target failure count actual=1 expected=0FAILAPI catalog target https://www.govtech.com/sitemap.xml (item) advertised application/xml but returned text/xml;charset=UTF-8.
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
15 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": "15 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 45 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