CanAgentUse

Saved report

https://www.elsevier.com/products/digital-commons

SCANNED

Jun 28, 2026, 5:38 AM

VISIBILITY

Public

SUITE2026.06.10

Rescan Report

Share Report

Copy Report Link

New Scan

https://www.elsevier.com/products/digital-commons

SCANNED

Jun 28, 2026, 5:38:57 AMJun 28, 2026, 5:38 AM

VISIBILITY

Public

SUITE2026.06.10

Rescan Report

Share Report

Copy Report Link

Export Report

68/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents

CAPTURED SCREENSHOT

What AI sees of your website

Digital Commons | Digital showcase for scholarly work | Elsevier

Digital Commons helps institutions save, share, showcase, publish and promote research, scholarship and collections.

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.

Detailed report scores grouped by capability area
Metric	Score	Status	Passed	Failed	Warning	Evidence
AI Discoverability	63	Needs work	34	1	0	View details
Discoverability	67	Needs work	8	0	0
Content Readiness	66	Needs work	21	0	0
Bot Access Control	58	Needs work	5	1	0	View details
Agent Ease of Use	49	Priority fix	1	0	0
Auth	48	Priority fix	1	0	0
GEO, AIO and AEO	73	Needs work	10	1	2	View details
GEO Readiness	61	Needs work	3	1	2	View details
AIO Readiness	Not Applicable	Not Applicable	4	0	0
AEO Readiness	Not Applicable	Not Applicable	3	0	0
SEO	100	Strong	10	0	0
SEO	100	Strong	10	0	0
Security & Trust	70	Needs work	14	0	0
Security & Trust	70	Needs work	14	0	0
Performance	90	Strong	21	1	0	View details
Performance	90	Strong	21	1	0	View details

Prioritized recommendations

Issues ranked by score impact

5 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

Needs attention

AI bot rules in robots.txt

Failed check

Issue

No explicit User-agent rules were found for major AI crawler tokens.

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.

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=0

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Citable passages

GEO: Citable passages scored 0/100 and needs a fix.

12 Fail

Needs attention

GEO: Citable passages

Failed check

Issue

No evidence-backed, citation-length explanatory paragraph was found.

Details

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Citable passages

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Citable passages scored 0/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Source and trust signals

GEO: Source and trust signals scored 67/100 and needs improvement.

4 Warning

Needs attention

GEO: Source and trust signals

Warning

Issue

Missing source or trust signals: freshnessDate, entityLinks.

Details

Why it matters

Check name

GEO: Source and trust signals

Score

67/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Source and trust signals scored 67/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Structured extraction

GEO: Structured extraction scored 75/100 and needs improvement.

3 Warning

Needs attention

GEO: Structured extraction

Warning

Issue

Missing or weak extraction signals: clean heading hierarchy, summary or key takeaways.

Details

Why it matters

Check name

GEO: Structured extraction

Score

75/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Structured extraction scored 75/100 and needs improvement.

PerformancePerformanceBrowser audit

Forced reflow

100 Fail

Check name

Forced reflow

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations.

References

https://web.dev/learn/performance/

Evidence

{
  "description": "A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations."
}

Sign in to see 30 other issues and the full report

Create a free account to unlock every issue, evidence details, exports, and higher free limits.

Development Note:

Please configure GOOGLE_CLIENT_ID in .env to activate live login.

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.

2 reports

Public score history report links
Scan date	Score	Readiness	Report
Jun 22, 2026	68/100	Level 3, Bot-Aware	View report
Jun 28, 2026	68/100	Level 3, Bot-Aware	Current report