Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 37 out of 100
- Agent Ease of Use 58 out of 100
- Security & Trust 68 out of 100
- GEO, AIO and AEO 55 out of 100
- SEO 100 out of 100
- Performance 63 out of 100
- Accessibility 79 out of 100
What AI sees of your website
OHSU | Healing Begins with Discovery
OHSU treats the most complex health needs in the region, makes discoveries that save lives and educates next-generation health professionals.
Next step
Turn this report into a fix workflow
3 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 | 37 | Priority fix | 14 | 5 | 3 | View details |
| Discoverability | 47 | Priority fix | 6 | 0 | 0 | |
| Content Readiness | 17 | Priority fix | 7 | 4 | 3 | View details |
| Bot Access Control | 45 | Priority fix | 1 | 1 | 0 | View details |
| Agent Ease of Use | 58 | Needs work | 3 | 0 | 0 | |
| Auth | 48 | Priority fix | 1 | 0 | 0 | |
| Google Agentic Browsing | 100 | Strong | 2 | 0 | 0 | |
| GEO, AIO and AEO | 55 | Needs work | 7 | 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 | 2 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| Security & Trust | 68 | Needs work | 14 | 0 | 0 | |
| Security & Trust | 68 | Needs work | 14 | 0 | 0 | |
| Performance | 63 | Needs work | 11 | 0 | 0 | |
| Performance | 63 | 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
Author attribution
Author attribution is partially implemented.
48 Fail
AI DiscoverabilityContent ReadinessEstablished
Author attribution
Author attribution is partially implemented.
Needs attention
Author attribution
Issue
Applicable editorial content has no usable author, creator, publisher, visible byline, or HTML attribution signal.
Details
Why it matters
Author attribution helps agents cite content responsibly, assess source credibility, and distinguish editorial pages from anonymous marketing copy.
Check name
Author attribution
Score
5/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Identify content authors or publishers for trust and attribution.
Result
Author attribution is partially implemented.
Validation steps
Schema.org attribution
Editorial content has no Schema.org author, creator, or publisher attribution.
Schema.org author attribution is missing or incomplete
Author identity quality
No named author or publisher identity could be extracted.
Author identity quality is incomplete
Visible byline parity
Structured author/publisher names were not found in visible byline text.
Author attribution does not match visible byline content
HTML attribution support
No supporting HTML author metadata, rel=author link, or visible byline was found.
HTML author attribution support is missing
Evidence log4 steps · 16 lines
Schema.org attribution [fail]! Editorial content has no Schema.org author, creator, or publisher attribution.INFOSchema.org attributionINFOChecking structured data for author, creator, and publisher contributorsFAILCheck named Schema.org author count actual=0 expected="> 0" authorCount=0 publisherCount=0 namedContributors=0 authors=[] publishers=[] formats=[]FAILNo Schema.org author, creator, or publisher attribution foundAuthor identity quality [fail]! No named author or publisher identity could be extracted.INFOAuthor identity qualityINFOChecking contributors for stable identity signalsFAILCheck identified contributor count actual=0 expected="> 0" namedContributors=0 identifiedContributors=[] unidentifiedContributors=[]FAILNo named contributor identity could be extractedVisible byline parity [fail]! Structured author/publisher names were not found in visible byline text.INFOVisible byline parityINFOComparing structured contributor names with visible byline evidenceFAILCheck visible attribution matches actual=0 expected="> 0 or visible byline present" visibleByline=false bylineCount=0FAILNo visible byline parity foundHTML attribution support [warning]! No supporting HTML author metadata, rel=author link, or visible byline was found.INFOHTML attribution supportINFOChecking meta author, rel=author, and visible byline supportWARNCheck HTML attribution support signals actual=0 expected="> 0" metaAuthor=false relAuthor=false visibleByline=falseWARNNo supporting HTML attribution signal found
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
13 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: meta Last-Modified is not a parseable date (1780694892)..
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
75/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 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
Check date validity and consistency
meta Last-Modified is not a parseable date (1780694892).
Freshness dates are invalid or inconsistent
Evidence log3 steps · 12 lines
Validate metadata freshness dates [warning]! No Open Graph, Dublin Core, or generic meta freshness date was found.INFOValidate metadata freshness datesINFOCollecting Open Graph, Dublin Core, and generic meta freshness datesWARNCheck metadata freshness date count actual=1 expected="> 0" metaDateCount=1 invalidDateCount=1 alternateDates=[{"source":"http","channel":"header","property":"Last-Modified","value":"Fri, 03 Jul 2026 18:16:12 GMT","parsed":"2026-07-03T18:16:12.000Z","location":"HTTP response header: Last-Modified"}]WARNMetadata freshness dates include invalid values invalidDateCount=1Corroborate with sitemap lastmod [warning]INFOCorroborate with sitemap lastmodINFODiscovering sitemap candidates and matching the scanned page URL candidateCount=1 attempts=5WARNCheck matching sitemap lastmod actual="no match" expected="valid match when available" robotsStatusCode=200WARNNo matching sitemap lastmod found after sitemap attempts attempts=5Check date validity and consistency [fail]! meta Last-Modified is not a parseable date (1780694892).INFOCheck date validity and consistencyINFOChecking collected freshness dates for invalid values, future dates, and inconsistent orderingFAILCheck critical freshness issue count actual=1 expected=0 warningIssueCount=0 issues=[{"severity":"fail","message":"meta Last-Modified is not a parseable date (1780694892)."}]FAILInvalid freshness date issue found issues=["meta Last-Modified is not a parseable date (1780694892)."]
Sign in to see 42 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 |
|---|---|---|---|
| 57/100 | Level 3, Bot-Aware | Current report |