CanAgentUse

CanAgentUse products

Agentic Browsing AuditCheck dialogs, menus, drawers, popovers, form errors, checkout steps, and other UI states that a standard Lighthouse scan may not capture.View product MCP ServerInstall CanAgentUse in your coding agent so scan findings become repo-ready fixes.View product WooCommerce PluginPublish UCP discovery and agent-ready commerce signals from WooCommerce without rebuilding checkout.View product Shopify PluginAdd UCP discovery, storefront metadata checks, and controlled cart-to-checkout flows for shopping agents.View product AgentReady CIScan commits and PRs, publish reports, and choose which agent-readiness failures should block merges.View product

CanAgentUse tools

UCP Suite

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

UCP ValidatorUCP Playground

MCP Playground

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

MCP Playground

A2A Playground

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

A2A Playground

Agent Website Viewer

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

Agent Website Viewer
New Scan
https://rewaa.com/
SCANNED
Jul 12, 2026, 10:15 AM
VISIBILITY
Public
SUITE2026.06.10
Rescan Report
Share Report
Copy Report Link
Export Report
51/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability69%Agent Easeof Use56%Security& Trust45%GEO, AIO, AEO35%SEO100%Performance94%Accessibility0%
  • AI Discoverability 69 out of 100
  • Agent Ease of Use 56 out of 100
  • Security & Trust 45 out of 100
  • GEO, AIO and AEO 35 out of 100
  • SEO 100 out of 100
  • Performance 94 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

رواء | كاشير ومحاسبة وإدارة مخزون وفوترة وأكثر favicon

رواء | كاشير ومحاسبة وإدارة مخزون وفوترة وأكثر

تعرّف على أفضل برنامج محاسبة وكاشير لإدارة نشاطك تجاري - حلول متكاملة تجمع الكاشير، والمحاسبة، والمخزون، و الفوترة الإلكترونية في نظام واحد

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
69
Needs work3300
Discoverability
67
Needs work800
Content Readiness
65
Needs work2000
Bot Access Control
75
Mostly ready500
Agent Ease of Use
56
Needs work731View details
API
60
Needs work521View details
Google Agentic Browsing
67
Needs work210View details
GEO, AIO and AEO
35
Priority fix341View details
GEO Readiness
Not Applicable
Not Applicable100
AIO Readiness
Not Applicable
Not Applicable100
AEO Readiness
19
Priority fix141View details
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
45
Priority fix700
Security & Trust
45
Priority fix700
Performance
94
Strong1500
Performance
94
Strong1500

Prioritized recommendations

Issues ranked by score impact

7 items need attention

Agent Ease of UseAPIEstablished

API Catalog

API Catalog failed at "Validate Linkset shape".

40 Fail

Needs attention

API Catalog

Failed check
01

Issue

Relation "title" must be an array of target objects.

Details

02

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

60/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 Linkset shape".

Validation steps

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

  2. Validate Linkset shape

    Relation "title" must be an array of target objects.

    API catalog Linkset shape is invalid

    title: Relation "title" must be an array of target objects.

  3. Validate API catalog targets

    API catalog target https://rewaa.com/llms.txt (describedby) advertised text/markdown but returned text/plain; charset=UTF-8.

    API catalog targets are unreachable or media types mismatch
Evidence log3 steps · 16 lines
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" 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 Linkset shape [fail]! Relation "title" must be an array of target objects.INFOValidate Linkset shapeFAILCompare Linkset JSON parse result actual=true expected=trueFAILCompare top-level linkset item count actual=2 expected="> 0"FAILCompare extracted href target count actual=3 expected="> 0"FAILLinkset href issue rel="title" issue="Relation \"title\" must be an array of target objects."FAILRelation "title" must be an array of target objects.Validate API catalog targets [fail]! API catalog target https://rewaa.com/llms.txt (describedby) advertised text/markdown but returned text/plain; charset=UTF-8.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsFAILAPI catalog target failed validation rel="describedby" href="https://rewaa.com/llms.txt" statusCode=200 contentType="text/plain; charset=UTF-8" advertisedType="text/markdown" typeMatches=falsePASSAPI catalog target is reachable rel="service-doc" href="https://rewaa.com/" statusCode=200 contentType="text/html; charset=UTF-8" advertisedType="text/html"FAILCompare API catalog target failure count actual=1 expected=0FAILAPI catalog target https://rewaa.com/llms.txt (describedby) advertised text/markdown but returned text/plain; charset=UTF-8.

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

10 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: Entity and definition clarity

AEO: Entity and definition clarity scored 44/100 and needs a fix.

4 Fail

Needs attention

AEO: Entity and definition clarity

Failed check
01

Issue

Expected exactly one h1, found 2. Title, h1, description, and opening copy are weakly aligned. 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

44/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: Entity and definition clarity scored 44/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Extractable visible copy

AEO: Extractable visible copy scored 46/100 and needs a fix.

4 Fail

Needs attention

AEO: Extractable visible copy

Failed check
01

Issue

Only 23 visible words were detected for answer extraction. 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

46/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: Extractable visible copy scored 46/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question and answer structure

AEO: Question and answer structure scored 47/100 and needs a fix.

4 Fail

Needs attention

AEO: Question and answer structure

Failed check
01

Issue

No natural question headings were detected. No visible FAQ or Q&A pattern was detected. Heading structure issues were 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

47/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: Question and answer structure scored 47/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Evidence and trust

AEO: Evidence and trust scored 57/100 and needs improvement.

3 Warning

Needs attention

AEO: Evidence and trust

Warning
01

Issue

Missing answer evidence or trust signals: author, publisher, sameAs.

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

57/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: Evidence and trust scored 57/100 and needs improvement.

Agent Ease of UseGoogle Agentic BrowsingBrowser audit

Accessibility tree is not well-formed

100 Fail

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."
}

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