CanAgentUse

Make your website ready for AI agents.

CanAgentUse tools

UCP Suite

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

UCP Validator UCP 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

https://talener.com/

SCANNED

Jul 6, 2026, 12:41 AM

VISIBILITY

Public

SUITE2026.06.10

Rescan Report

Share Report

Copy Report Link

New Scan

https://talener.com/

SCANNED

Jul 6, 2026, 12:41 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

CAPTURED SCREENSHOT

What AI sees of your website

Talener | Home | Technology Staffing

Technology staffing and recruitment services that help your growing business stay competitive in the fast-paced, ever-evolving tech space.

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
Metric	Score	Status	Passed	Failed	Evidence
AI Discoverability	63	Needs work	32	2	View details
Discoverability	67	Needs work	8	0
Content Readiness	81	Mostly ready	23	1	View details
Bot Access Control	45	Priority fix	1	1	View details
Agent Ease of Use	50	Needs work	1	1	View details
Google Agentic Browsing	50	Needs work	1	1	View details
GEO, AIO and AEO	56	Needs work	6	0
GEO Readiness	Not Applicable	Not Applicable	2	0
AIO Readiness	Not Applicable	Not Applicable	2	0
AEO Readiness	Not Applicable	Not Applicable	2	0
SEO	85	Mostly ready	8	0
SEO	85	Mostly ready	8	0
Security & Trust	45	Priority fix	7	0
Security & Trust	45	Priority fix	7	0
Performance	89	Mostly ready	14	0
Performance	89	Mostly ready	14	0

Prioritized recommendations

Issues ranked by score impact

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

Details

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

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

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

0 Fail

Needs attention

Content freshness signals

Failed check

Issue

Content freshness signals are invalid: dateModified (2026-01-05) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-04-21).; dateModified (2025-04-25) is earlier than datePublished (2026-04-21).; dateModified (2026-01-05) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-04-21).; dateModified (2025-04-25) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2026-01-05).; dateModified (2025-10-21) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2025-10-13).; dateModified (2025-04-25) is earlier than datePublished (2025-10-13).; dateModified (2026-01-05) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-04-21).; dateModified (2025-04-25) is earlier than datePublished (2026-04-21).; dateModified (2026-01-05) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-04-21).; dateModified (2025-04-25) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2026-01-05).; dateModified (2025-10-21) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2025-10-13).; dateModified (2025-04-25) is earlier than datePublished (2025-10-13)..

Details

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

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

Check date validity and consistency
dateModified (2026-01-05) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-04-21).; dateModified (2025-04-25) is earlier than datePublished (2026-04-21).; dateModified (2026-01-05) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-04-21).; dateModified (2025-04-25) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2026-01-05).; dateModified (2025-10-21) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2025-10-13).; dateModified (2025-04-25) is earlier than datePublished (2025-10-13).; dateModified (2026-01-05) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-04-21).; dateModified (2025-04-25) is earlier than datePublished (2026-04-21).; dateModified (2026-01-05) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-04-21).; dateModified (2025-04-25) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2026-01-05).; dateModified (2025-10-21) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2025-10-13).; dateModified (2025-04-25) is earlier than datePublished (2025-10-13).
Freshness dates are invalid or inconsistent

Evidence log1 step · 4 lines

Check date validity and consistency [fail]! dateModified (2026-01-05) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-04-21).; dateModified (2025-04-25) is earlier than datePublished (2026-04-21).; dateModified (2026-01-05) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-04-21).; dateModified (2025-04-25) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2026-01-05).; dateModified (2025-10-21) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2025-10-13).; dateModified (2025-04-25) is earlier than datePublished (2025-10-13).; dateModified (2026-01-05) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-04-21).; dateModified (2025-04-25) is earlier than datePublished (2026-04-21).; dateModified (2026-01-05) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-04-21).; dateModified (2025-04-25) is earlier than datePublished (2026-04-21).; dateModified (2025-10-21) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2026-01-05).; dateModified (2025-10-21) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2026-01-05).; dateModified (2025-04-25) is earlier than datePublished (2025-10-13).; dateModified (2025-04-25) is earlier than datePublished (2025-10-13).INFOCheck date validity and consistencyINFOChecking collected freshness dates for invalid values, future dates, and inconsistent orderingFAILCheck critical freshness issue count actual=24 expected=0 warningIssueCount=0 issues=[{"severity":"fail","message":"dateModified (2026-01-05) is earlier than datePublished (2026-04-21)."},{"severity":"fail","message":"dateModified (2025-10-21) is earlier than datePublished (2026-04-21)."},{"severity":"fail","message":"dateModified (2025-04-25) is earlier than datePublished (2026-04-21)."},{"severity":"fail","message":"dateModified (2026-01-05) is earlier than datePublished (2026-04-21)."},{"severity":"fail","message":"dateModified (2025-10-21) is earlier than datePublished (2026-04-21)."},{"severity":"fail","message":"dateModified (2025-04-25) is earlier than datePublished (2026-04-21)."},{"severity":"fail","message":"dateModified (2025-10-21) is earlier than datePublished (2026-01-05)."},{"severity":"fail","message":"dateModified (2025-04-25) is earlier than datePublished (2026-01-05)."},{"severity":"fail","message":"dateModified (2025-10-21) is earlier than datePublished (2026-01-05)."},{"severity":"fail","message":"dateModified (2025-04-25) is earlier than datePublished (2026-01-05)."}]FAILInvalid freshness date issue found issues=["dateModified (2026-01-05) is earlier than datePublished (2026-04-21).","dateModified (2025-10-21) is earlier than datePublished (2026-04-21).","dateModified (2025-04-25) is earlier than datePublished (2026-04-21).","dateModified (2026-01-05) is earlier than datePublished (2026-04-21).","dateModified (2025-10-21) is earlier than datePublished (2026-04-21)."]

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

Fix guidance

A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page.

References

goo.gle/lighthouse-agentic-web Browser agent UX guide for forms and modals

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

1 reports

Public score history report links
Scan date	Score	Readiness	Report
Jul 6, 2026	51/100	Level 3, Bot-Aware	Current report

Want help fixing this?

Level 3, Bot-Aware

CAPTURED SCREENSHOT

What AI sees of your website

Talener | Home | Technology Staffing

Turn this report into a fix workflow

Issues ranked by score impact

AI bot rules in robots.txt

AI bot rules in robots.txt

Issue

Details

Why it matters

Check name

Score

Status

Category

Maturity

Goal

Result

Validation steps

robots.txt lacks explicit AI crawler rules

Content freshness signals

Content freshness signals

Issue

Details

Why it matters

Check name

Score

Status

Category

Maturity

Goal

Result

Validation steps

Freshness dates are invalid or inconsistent

Accessibility tree is not well-formed

Check name

Score

Status

Device

Category

Fix guidance

References

Sign in to see 42 other issues and the full report

Fix with MCP or CLI

Public scan score over time