PlayHero°
Scan My Site
How it works

Detection to verified fix.
One closed loop.

AI systems decide who gets discovered. Your site decides who converts. PlayHero monitors the second half — a finding is decided, briefed, shipped, and the next scan closes the card.

1
Approve
2
Brief drafted
3
Team ships
4
Scan evaluates
5
Resolved
01The Score

One URL in. One number out.

A scan renders your page the way visitors and AI agents both see it, then scores seven pillars. The overall number is the mean of the 6 human-side pillars at 88% plus Agent Readiness at 12%.

playhero.ai · 2026-09-166 human · 88% + Agent Readiness · 12%
Load Intelligence
75
Signal Hierarchy
77
Messaging Clarity
59
Content Clarity
90
CTA Clarity
80
Conversion Friction
60
Agent Readiness
82
Overall
75
Human UX
74
Agent Readiness
82
Four passes
DOM fetchDeterministic

Full rendered DOM at 375 / 768 / 1440px — what visitors actually see.

Heuristic analysisDeterministic

CTA visibility, contrast ratios, heading nesting, form friction, per viewport.

LighthouseObjective

LCP, INP, CLS against Google's published thresholds.

LLM interpretationProbabilistic

Value-prop legibility and messaging hierarchy — catches what rules can't, labeled as interpretive.

Total scan timeabout 3 minutes
02The Agents

Four specialists. One domain each.

Every agent owns one narrow detection domain. Narrow on purpose — a UX finding and a Web Vitals finding argued by the same generalist would weaken both.

UX Sentinel
Conversion friction · human UX signals

High and critical severity, plus lower-severity findings with strong supporting evidence.

CTA visibility across viewports
Heading hierarchy breaks
Drift Detector
Score drift · scan-to-scan regression

It compares each pillar to the previous scan on the same URL and raises a regression alert when the drop holds for seven days.

Per-pillar score change scan-to-scan
7-day regression alert
Alerts are skipped across an engine-version boundary
Page Vitals Enforcer
Load intelligence · AI crawl performance

Enforces Google's published Core Web Vitals thresholds — slow pages lose crawlers too.

LCP regression detection
CLS layout-shift scoring
Lumen
AI discoverability · citation monitoring

Scores AI readiness across the platforms your buyers actually query, and flags misframing.

9-signal readiness scan
Citation Scout · 5 platforms
Framing accuracy · weekly on Brand
03The Decision

Every finding arrives as a decision.

A Rallycard is a governed decision artifact, not a notification. Every field exists so a reviewer can decide without opening another tab.

UX SentinelEXAMPLEhigh
Hero CTA invisible on mobile viewports

Primary CTA sits below the fold on mobile viewports. Visitors who never see the CTA cannot convert.

Agent + severity
Who found it, how bad, and by which detection method. Each agent owns severity for its own domain.
Decision impact
A benchmark-based dollar range when both estimates are present — labeled as the estimate it is.
How it surfaces
High, medium, or low — judged by the detecting agent. Lumen's framing-accuracy check is the exception and keeps its own measured threshold.
Code fix
A copy-ready diff when the detecting agent wrote one. The reviewer sees the fix before they weigh the finding.
Approve · Defer · Dismiss
Nothing executes without this. Every choice is logged with actor and timestamp — dismissals included.
04The Fix

Approval starts a loop, not a ticket.

Approving a card doesn't file a ticket into the void. It starts a loop the system finishes on its own — and no one has to ask "did that work?" The record answers.

1
Approve
Card locks. The original finding is frozen — no quiet edits.
2
Brief drafted
A Resolution Brief with verification criteria, frozen at draft time.
3
Team ships
The fix lands in your codebase. PlayHero never touches your site.
4
Scan evaluates
The next scan reads the frozen criteria — not vibes, not a checkbox.
5
Resolved
The card closes. A score delta attaches when the scan measured one.
EXAMPLE
ResolvedHero CTA invisible on mobile viewportsclosed by a later scan
05The Record

The Heroboard remembers by page, not by ping.

The Heroboard is not a task manager. Every decision — approved, dismissed, deferred, resolved — lives under the page it belongs to, with actor and timestamp. Over time it becomes the only complete history of why your site converts the way it does.

your-website.com/pricingEXAMPLE
ResolvedHero CTA invisible on mobile viewportsclosed by a later scan
ApprovedHeading hierarchy breakbrief drafted
DismissedStale hero messagingreason logged

See your first findings.

Free scan. No login, no credit card.