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 6, 2026, 7:15 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
67/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability53%Agent Easeof Use61%Security& Trust62%GEO, AIO, AEO61%SEO100%Performance97%Accessibility88%
  • AI Discoverability 53 out of 100
  • Agent Ease of Use 61 out of 100
  • Security & Trust 62 out of 100
  • GEO, AIO and AEO 61 out of 100
  • SEO 100 out of 100
  • Performance 97 out of 100
  • Accessibility 88 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Mountain View Staffing - Silicon Valley/Bay Area Staffing favicon

Mountain View Staffing - Silicon Valley/Bay Area Staffing

Silicon Valley's most trusted recruiting and staffing agency for full-time and contract hiring for technical and business roles at funded startups- Mountain View, Palo Alto, Sunnyvale, Santa Clara, San Jose, Menlo Park, Redwood City

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
53
Needs work2541View details
Discoverability
67
Needs work800
Content Readiness
55
Needs work1600
Bot Access Control
40
Priority fix141View details
Agent Ease of Use
61
Needs work1000
API
67
Needs work100
Auth
47
Priority fix100
Agent Commerce
83
Mostly ready600
Google Agentic Browsing
67
Needs work200
GEO, AIO and AEO
61
Needs work920View details
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
74
Needs work420View details
AEO Readiness
Not Applicable
Not Applicable300
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
62
Needs work1300
Security & Trust
62
Needs work1300
Performance
97
Strong1700
Performance
97
Strong1700

Prioritized recommendations

Issues ranked by score impact

4 items need attention

AI DiscoverabilityBot Access ControlEmerging recommendation

ai.txt policy

ai.txt policy failed at "Fetch /ai.txt".

41 Fail

Needs attention

ai.txt policy

Failed check
01

Issue

/ai.txt returned HTTP 400.

Details

02

Why it matters

ai.txt is a fragmented emerging convention. It can communicate human-readable AI crawling, training, attribution, restriction, and contact guidance, but it is not a standard access-control mechanism and absence should not be penalized.

Check name

ai.txt policy

Score

18/100

Status

fail

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

Publish an advisory human-readable AI usage policy only when the site intentionally needs one.

Result

ai.txt policy failed at "Fetch /ai.txt".

Validation steps

  1. Fetch /ai.txt

    /ai.txt returned HTTP 400.

    /ai.txt could not be fetched when present
  2. Validate transport

    ai.txt appears to be an HTML page or error document rather than a plain-text policy.

    /ai.txt transport is invalid or not plain text
  3. Parse ai.txt policy

    Transport validation failed before policy parsing could be trusted.

    /ai.txt policy format is missing required sections or non-standard
  4. Validate policy content

    ai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.

    /ai.txt content is incomplete or unsafe
Evidence log4 steps · 18 lines
Fetch /ai.txt [fail]! /ai.txt returned HTTP 400.INFOFetch /ai.txtINFORequesting optional advisory policy file at /ai.txtFAILCompare /ai.txt HTTP response actual=400 expected="2xx when ai.txt is intentionally published; 404/410 means absent optional file" contentType="text/html; charset=UTF-8" length=2204FAIL/ai.txt returned HTTP 400. statusCode=400Validate transport [fail]! ai.txt appears to be an HTML page or error document rather than a plain-text policy.INFOValidate transportINFOChecking ai.txt media type, size, line count, and whether the response looks like plain text contentType="text/html; charset=UTF-8" length=2204 lineCount=53FAILCompare media type to preferred text/plain transport actual="text/html" expected="text/plain preferred; readable text required"FAILai.txt appears to be an HTML page or error document rather than a plain-text policy.Parse ai.txt policy [fail]! Transport validation failed before policy parsing could be trusted.INFOParse ai.txt policyINFODetecting ai.txt convention from bracket sections, frontmatter, headings, and ai.txt context linksINFODetected policy structure convention="unknown-text" sections=[] markdownHeadings=[]WARNCheck AI Visibility required sections actual="missing identity, permissions, restrictions" expected="identity, permissions, and restrictions" missingRecommended=["attribution","contact","content-types"]WARNTransport validation failed before policy parsing could be trusted.Validate policy content [warning]! ai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.INFOValidate policy contentINFOChecking required section content, permission/restriction language, attribution, contact details, and safety risks convention="unknown-text"INFODetected policy signals hasPermissionLanguage=false hasRestrictionLanguage=false hasTrainingLanguage=false hasAttributionLanguage=false hasContact=falseWARNCheck required and recommended section coverage actual={"missingRequired":["identity","permissions","restrictions"],"missingRecommended":["attribution","contact","content-types"]} expected={"missingRequired":[],"recommendedPresentWhenPossible":true}WARNai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.

AI DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

AI bot rules in robots.txt failed at "Classify AI crawler rules".

35 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

AIO: Structured data consistency

AIO: Structured data consistency scored 0/100 and needs a fix.

15 Fail

Needs attention

AIO: Structured data consistency

Failed check
01

Issue

1 structured-data value(s) were not found in visible page text.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Structured data consistency

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Structured data consistency scored 0/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

AIO: Source and trust signals scored 17/100 and needs a fix.

12 Fail

Needs attention

AIO: Source and trust signals

Failed check
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate, policyLinks, sourceLinks.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Source and trust signals

Score

17/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Source and trust signals scored 17/100 and needs a fix.

Sign in to see 33 other issues and the full report

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

Email code

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

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 dateScoreReadinessReport
63/100Level 3, Bot-AwareView report
67/100Level 3, Bot-AwareCurrent report