CanAgentUse

Saved report

https://www.facebook.com/watch/

SCANNED

Jun 24, 2026, 11:24 AM

VISIBILITY

Public

SUITE2026.06.10

Rescan Report

Share Report

Copy Report Link

New Scan

https://www.facebook.com/watch/

SCANNED

Jun 24, 2026, 11:24:10 AMJun 24, 2026, 11:24 AM

VISIBILITY

Public

SUITE2026.06.10

Rescan Report

Share Report

Copy Report Link

Export Report

43/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents

CAPTURED SCREENSHOT

What AI sees of your website

Discover popular videos | Facebook

Video is the place to enjoy videos and shows together. Watch the latest reels, discover original shows and catch up with your favourite creators.

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.

Detailed report scores grouped by capability area
Metric	Score	Status	Passed	Failed	Warning	Evidence
AI Discoverability	40	Priority fix	17	0	0
Discoverability	48	Priority fix	5	0	0
Content Readiness	13	Priority fix	8	0	0
Bot Access Control	54	Needs work	4	0	0
Agent Ease of Use	42	Priority fix	13	2	3	View details
API	50	Needs work	4	0	0
Auth	40	Priority fix	4	0	0
MCP	37	Priority fix	3	0	0
Skill Discovery	41	Priority fix	2	2	3	View details
GEO, AIO and AEO	31	Priority fix	2	3	3	View details
AIO Readiness	Not Applicable	Not Applicable	2	0	0
AEO Readiness	25	Priority fix	0	3	3	View details
SEO	100	Strong	10	0	0
SEO	100	Strong	10	0	0
Security & Trust	74	Needs work	18	0	0
Security & Trust	74	Needs work	18	0	0
Performance	58	Needs work	13	0	0
Performance	58	Needs work	13	0	0
Accessibility	0	Priority fix	0	1	0	View details
Accessibility	0	Priority fix	0	1	0	View details

Prioritized recommendations

Issues ranked by score impact

8 items need attention

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

A2A Agent Card failed at "Detect A2A card version".

61 Fail

Needs attention

A2A Agent Card

Failed check

Issue

The discovered JSON document does not match a supported A2A Agent Card version family.

Why it matters

A2A Agent Cards provide protocol-specific discovery for agent identity, skills, input and output modes, transport bindings, capabilities, and security requirements. Legacy A2A also used /.well-known/agent.json, so scanners must classify the card shape before reporting readiness.

Check name

A2A Agent Card

Score

39/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish a version-appropriate A2A Agent Card so A2A-compatible clients can discover agent skills and invoke the declared endpoint safely.

Result

A2A Agent Card failed at "Detect A2A card version".

Validation steps

Discover A2A Agent Card
The A2A Agent Card was found at a legacy or fallback path.
Detect A2A card version
The discovered JSON document does not match a supported A2A Agent Card version family.
Validate version-specific card shape
A2A Agent Card response is not valid JSON.
Validate HTTP delivery
The card was parseable JSON but was not served with a JSON-compatible content type.
Probe same-origin A2A endpoint
A2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.

Evidence log5 steps · 26 lines

Discover A2A Agent Card [warning]! The A2A Agent Card was found at a legacy or fallback path.INFODiscover A2A Agent CardINFOTry A2A discovery paths in priority order paths=["/.well-known/agent-card.json","/.well-known/agent.json","/agent-card.json","/.well-known/a2a/agent-card.json"]WARNA2A candidate path did not return a usable card path="/.well-known/agent-card.json" statusCode=404 contentType="text/html; charset=\"utf-8\""WARNA2A candidate path did not return a usable card path="/.well-known/agent.json" statusCode=404 contentType="text/html; charset=\"utf-8\""PASSFound an A2A candidate path="/agent-card.json" statusCode=200 contentType="text/html; charset=\"utf-8\"" bytes=430915WARNA2A candidate path did not return a usable card path="/.well-known/a2a/agent-card.json" statusCode=404 contentType="text/html; charset=\"utf-8\""WARNSelected non-canonical A2A Agent Card path="/agent-card.json" pathClass="fallback" requestedUrl="https://www.facebook.com/agent-card.json"WARNThe A2A Agent Card was found at a legacy or fallback path.Detect A2A card version [fail]! The discovered JSON document does not match a supported A2A Agent Card version family.INFODetect A2A card versionINFORead version indicators from the card detectionEvidence=[]FAILCompare detected A2A version family actual="unknown" expected="v0.1, v0.2, v0.3, or v1"FAILThe discovered JSON document does not match a supported A2A Agent Card version family.Validate version-specific card shape [fail]! A2A Agent Card response is not valid JSON.INFOValidate version-specific card shapeFAILCompare missing required card fields actual="none" expected="none"FAILCheck every declared A2A skill has required name, description, and endpoint fields actual=0 expected=0 invalidSkills=[]INFOReview declared endpoint interfaces interfaces=[]FAILA2A Agent Card response is not valid JSON.Validate HTTP delivery [warning]! The card was parseable JSON but was not served with a JSON-compatible content type.INFOValidate HTTP deliveryWARNCompare card Content-Type with JSON expectation actual="text/html; charset=\"utf-8\"" expected="application/json or +json"INFOReview selected discovery path path="/agent-card.json" pathClass="fallback"WARNHTTP delivery/path warning warning="card was found only at a non-standard fallback path"WARNThe card was parseable JSON but was not served with a JSON-compatible content type.Probe same-origin A2A endpoint [warning]! A2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.INFOProbe same-origin A2A endpointINFOProbe same-origin A2A endpoint when scanner policy allows itSKIPSkipped endpoint probe reason="No valid A2A card was available to probe."WARNA2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Evidence and trust

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

6 Fail

Needs attention

AEO: Evidence and trust

Failed check

Issue

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

Details

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

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: Evidence and trust scored 0/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question and answer structure

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

3 Fail

Needs attention

AEO: Question and answer structure

Failed check

Issue

No natural question headings were detected. No visible FAQ or Q&A pattern was detected. Heading structure issues were detected. No list or table answer format was detected.

Details

Why it matters

Check name

AEO: Question and answer structure

Score

40/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 40/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.

3 Fail

Needs attention

AEO: Extractable visible copy

Failed check

Issue

Only 6 visible words were detected for answer extraction. Visible text has few answer-oriented terms or explanatory markers.

Details

Why it matters

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: Answer-first passages

AEO: Answer-first passages scored 55/100 and needs improvement.

3 Warning

Needs attention

AEO: Answer-first passages

Warning

Issue

No h2/h3 answer sections were detected. No direct definition pattern was detected.

Details

Why it matters

Check name

AEO: Answer-first passages

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: Answer-first passages scored 55/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

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

2 Warning

Needs attention

AEO: Entity and definition clarity

Warning

Issue

Expected exactly one h1, found 0. No direct definition sentence was detected.

Details

Why it matters

Check name

AEO: Entity and definition clarity

Score

62/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 62/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-surface controls

AEO: Answer-surface controls scored 65/100 and needs improvement.

2 Warning

Needs attention

AEO: Answer-surface controls

Warning

Issue

6 answer retrieval crawler(s) are blocked for the scanned path.

Details

Why it matters

Check name

AEO: Answer-surface controls

Score

65/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: Answer-surface controls scored 65/100 and needs improvement.

AccessibilityAccessibilityBrowser audit

Accessibility audit

100 Fail

Check name

Accessibility audit

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Make sure the page can load in Chrome and run Accessibility checks.

References

https://www.deque.com/accessibility/core-documentation/

Evidence

{
  "error": "Execution context was destroyed, most likely because of a navigation."
}

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

5 reports

Public score history report links
Scan date	Score	Readiness	Report
Jun 22, 2026	50/100	Level 3, Bot-Aware	View report
Jun 22, 2026	49/100	Level 2, Agent-Limited	View report
Jun 22, 2026	49/100	Level 2, Agent-Limited	View report
Jun 22, 2026	49/100	Level 2, Agent-Limited	View report
Jun 24, 2026	43/100	Level 2, Agent-Limited	Current report