CanAgentUse tools

UCP Suite

Validate Universal Commerce Protocol discovery, then test product search, carts, checkout links, and merchant handoff flows.

MCP Playground

Connect to remote MCP servers, inspect tools and resources, test prompts, auth, headers, notifications, and JSON-RPC responses.

A2A Playground

Inspect Agent Cards, validate advertised endpoints, and prepare safe requests for agent-to-agent workflows.

Agent Website Viewer

Enter a public URL and see the roles, names, landmarks, controls, and blockers that shape how AI agents understand the page.

SCANNED
Jul 13, 2026, 4:49 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
66/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability54%Agent Easeof Use59%Security& Trust53%GEO, AIO, AEO56%SEO100%Performance99%Accessibility86%
  • AI Discoverability 54 out of 100
  • Agent Ease of Use 59 out of 100
  • Security & Trust 53 out of 100
  • GEO, AIO and AEO 56 out of 100
  • SEO 100 out of 100
  • Performance 99 out of 100
  • Accessibility 86 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Portal-Ilmu.com | Read More Learn More favicon

Portal-Ilmu.com | Read More Learn More

Portal edukasi berbasis online di Indonesia. Menyajikan informasi: referensi pelajaran sekolah, soal, inspirasi, sastra dan biografi tokoh.

Open Agent View

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.

Fix with MCP / CLI
Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
54
Needs work2521View details
Discoverability
67
Needs work800
Content Readiness
53
Needs work1611View details
Bot Access Control
45
Priority fix110View details
Agent Ease of Use
59
Needs work200
Google Agentic Browsing
100
Strong200
GEO, AIO and AEO
56
Needs work723View details
GEO Readiness
Not Applicable
Not Applicable300
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
34
Priority fix123View details
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
53
Needs work1000
Security & Trust
53
Needs work1000
Performance
99
Strong1900
Performance
99
Strong1900

Prioritized recommendations

Issues ranked by score impact

7 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
01

Issue

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

Details

02

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

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first passages

AEO: Answer-first passages scored 0/100 and needs a fix.

7 Fail

Needs attention

AEO: Answer-first passages

Failed check
01

Issue

7 section(s) bury or omit a concise opening answer. No direct definition pattern was detected.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Answer-first passages

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

AEO: Answer-first passages scored 0/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Evidence and trust

AEO: Evidence and trust scored 43/100 and needs a fix.

4 Fail

Needs attention

AEO: Evidence and trust

Failed check
01

Issue

Missing answer evidence or trust signals: sources, sameAs, aboutOrContact, policyLinks.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Evidence and trust

Score

43/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

AEO: Evidence and trust scored 43/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question and answer structure

AEO: Question and answer structure scored 55/100 and needs improvement.

3 Warning

Needs attention

AEO: Question and answer structure

Warning
01

Issue

No natural question headings were detected. No visible FAQ or Q&A pattern was detected.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Question and answer structure

Score

55/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

AEO: Question and answer structure scored 55/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

AEO: Entity and definition clarity scored 71/100 and needs improvement.

2 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

No direct definition sentence was detected.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Entity and definition clarity

Score

71/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

AEO: Entity and definition clarity scored 71/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Extractable visible copy

AEO: Extractable visible copy scored 81/100 and needs improvement.

1 Warning

Needs attention

AEO: Extractable visible copy

Warning
01

Issue

Visible text has few answer-oriented terms or explanatory markers.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Extractable visible copy

Score

81/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

AEO: Extractable visible copy scored 81/100 and needs improvement.

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

0 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

Content freshness signals are invalid: dateModified (2025-11-16T19:04:36+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).; dateModified (2025-10-05T22:05:26+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).; dateModified (2025-09-14T17:49:07+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).; dateModified (2025-03-03T22:09:06+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).; dateModified (2025-03-03T22:09:20+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).; dateModified (2025-10-05T22:05:26+07:00) is earlier than datePublished (2025-11-16T19:04:00+07:00).; dateModified (2025-09-14T17:49:07+07:00) is earlier than datePublished (2025-11-16T19:04:00+07:00).; dateModified (2025-03-03T22:09:06+07:00) is earlier than datePublished (2025-11-16T19:04:00+07:00).; dateModified (2025-03-03T22:09:20+07:00) is earlier than datePublished (2025-11-16T19:04:00+07:00).; dateModified (2025-09-14T17:49:07+07:00) is earlier than datePublished (2025-10-05T22:05:00+07:00).; dateModified (2025-03-03T22:09:06+07:00) is earlier than datePublished (2025-10-05T22:05:00+07:00).; dateModified (2025-03-03T22:09:20+07:00) is earlier than datePublished (2025-10-05T22:05:00+07:00).; dateModified (2025-03-03T22:09:06+07:00) is earlier than datePublished (2025-09-14T17:49:00+07:00).; dateModified (2025-03-03T22:09:20+07:00) is earlier than datePublished (2025-09-14T17:49:00+07:00)..

Details

02

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

  1. 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
  2. Check date validity and consistency

    dateModified (2025-11-16T19:04:36+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).; dateModified (2025-10-05T22:05:26+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).; dateModified (2025-09-14T17:49:07+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).; dateModified (2025-03-03T22:09:06+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).; dateModified (2025-03-03T22:09:20+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).; dateModified (2025-10-05T22:05:26+07:00) is earlier than datePublished (2025-11-16T19:04:00+07:00).; dateModified (2025-09-14T17:49:07+07:00) is earlier than datePublished (2025-11-16T19:04:00+07:00).; dateModified (2025-03-03T22:09:06+07:00) is earlier than datePublished (2025-11-16T19:04:00+07:00).; dateModified (2025-03-03T22:09:20+07:00) is earlier than datePublished (2025-11-16T19:04:00+07:00).; dateModified (2025-09-14T17:49:07+07:00) is earlier than datePublished (2025-10-05T22:05:00+07:00).; dateModified (2025-03-03T22:09:06+07:00) is earlier than datePublished (2025-10-05T22:05:00+07:00).; dateModified (2025-03-03T22:09:20+07:00) is earlier than datePublished (2025-10-05T22:05:00+07:00).; dateModified (2025-03-03T22:09:06+07:00) is earlier than datePublished (2025-09-14T17:49:00+07:00).; dateModified (2025-03-03T22:09:20+07:00) is earlier than datePublished (2025-09-14T17:49:00+07:00).

    Freshness dates are invalid or inconsistent
Evidence log2 steps · 8 lines
Corroborate with sitemap lastmod [warning]INFOCorroborate with sitemap lastmodINFODiscovering sitemap candidates and matching the scanned page URL candidateCount=2 attempts=4WARNCheck matching sitemap lastmod actual="no match" expected="valid match when available" robotsStatusCode=200WARNNo matching sitemap lastmod found after sitemap attempts attempts=4Check date validity and consistency [fail]! dateModified (2025-11-16T19:04:36+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).; dateModified (2025-10-05T22:05:26+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).; dateModified (2025-09-14T17:49:07+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).; dateModified (2025-03-03T22:09:06+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).; dateModified (2025-03-03T22:09:20+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).; dateModified (2025-10-05T22:05:26+07:00) is earlier than datePublished (2025-11-16T19:04:00+07:00).; dateModified (2025-09-14T17:49:07+07:00) is earlier than datePublished (2025-11-16T19:04:00+07:00).; dateModified (2025-03-03T22:09:06+07:00) is earlier than datePublished (2025-11-16T19:04:00+07:00).; dateModified (2025-03-03T22:09:20+07:00) is earlier than datePublished (2025-11-16T19:04:00+07:00).; dateModified (2025-09-14T17:49:07+07:00) is earlier than datePublished (2025-10-05T22:05:00+07:00).; dateModified (2025-03-03T22:09:06+07:00) is earlier than datePublished (2025-10-05T22:05:00+07:00).; dateModified (2025-03-03T22:09:20+07:00) is earlier than datePublished (2025-10-05T22:05:00+07:00).; dateModified (2025-03-03T22:09:06+07:00) is earlier than datePublished (2025-09-14T17:49:00+07:00).; dateModified (2025-03-03T22:09:20+07:00) is earlier than datePublished (2025-09-14T17:49:00+07:00).INFOCheck date validity and consistencyINFOChecking collected freshness dates for invalid values, future dates, and inconsistent orderingFAILCheck critical freshness issue count actual=14 expected=0 warningIssueCount=0 issues=[{"severity":"fail","message":"dateModified (2025-11-16T19:04:36+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00)."},{"severity":"fail","message":"dateModified (2025-10-05T22:05:26+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00)."},{"severity":"fail","message":"dateModified (2025-09-14T17:49:07+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00)."},{"severity":"fail","message":"dateModified (2025-03-03T22:09:06+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00)."},{"severity":"fail","message":"dateModified (2025-03-03T22:09:20+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00)."},{"severity":"fail","message":"dateModified (2025-10-05T22:05:26+07:00) is earlier than datePublished (2025-11-16T19:04:00+07:00)."},{"severity":"fail","message":"dateModified (2025-09-14T17:49:07+07:00) is earlier than datePublished (2025-11-16T19:04:00+07:00)."},{"severity":"fail","message":"dateModified (2025-03-03T22:09:06+07:00) is earlier than datePublished (2025-11-16T19:04:00+07:00)."},{"severity":"fail","message":"dateModified (2025-03-03T22:09:20+07:00) is earlier than datePublished (2025-11-16T19:04:00+07:00)."},{"severity":"fail","message":"dateModified (2025-09-14T17:49:07+07:00) is earlier than datePublished (2025-10-05T22:05:00+07:00)."}]FAILInvalid freshness date issue found issues=["dateModified (2025-11-16T19:04:36+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).","dateModified (2025-10-05T22:05:26+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).","dateModified (2025-09-14T17:49:07+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).","dateModified (2025-03-03T22:09:06+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00).","dateModified (2025-03-03T22:09:20+07:00) is earlier than datePublished (2026-05-04T08:58:00+07:00)."]

Sign in to see 28 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.

Fix with MCP / CLI

Score history