Qualify
Identify the client journey, business risk, environments and owners before testing.
Digital agencies
Evidence-backed AI-agent audits.
Today: repeatable site checks with evidence and fixes your engineering teams can verify. Coming later: AI agent task tests for client journeys.
For digital agencies, consultancies, technical SEO teams and web delivery partners.
Turn a broad AI question into a controlled client engagement.
Each engagement starts with owned journeys, declared boundaries and evidence that both client and delivery teams can review.
Baseline
Run the same versioned checks across public pages, and later the same key tasks with named AI agents.
Compare
Coming later: separate website defects from agent, policy and platform failures.
Explain
Connect every priority fix to the evidence we saw and the customer impact.
Handoff
Give the implementation team the failed check and how we will check it again.
Retest
Repeat the same task contract after fixes and compare outcome, speed and friction.
Keep scope, evidence and remediation connected.
One evidence contract prevents audit observations from becoming subjective presentation claims.
Client contract
Persona, goal, test data, permissions, stop gate and expected result are agreed before the run.
Reviewable evidence
Step logs, step screenshots, timing and final-state checks explain each outcome.
Verified retest
The same scenario confirms whether remediation changed the result without adding new risk.
Agency risk starts when a result cannot be defended.
Generic checklist
Technical presence is reported without proving impact on a real client task.
Unclear attribution
A model or runner failure is incorrectly presented as a website defect.
Unsafe scope
The run reaches a production write action without a declared stop gate.
Unverifiable fix
A recommendation has no reproduction path, owner-ready criteria or comparable retest.
Measure delivery quality as well as agent completion.
The result must support client communication, engineering action and a defensible follow-up test.
Task completion
Coming later: track checked outcomes by key task, agent and attempt.
Time and friction
Coming later: record step timings and repeated attempts.
Evidence coverage
Confirm that priority fixes have report-safe evidence and an independent check.
Baseline to retest
Compare results against the same fixtures, environment and versioned task contract.
Client authorization defines the testing boundary.
Our checker and AI agents stop before login, cart, checkout, payment and any form that sends data. Authenticated and staging tests are coming later.
Record technology state without turning emerging standards into sales theater.
Reports separate established web foundations, optional agent-native interfaces and technologies that were not available or not tested.
- Page titles, headings, language and structured data syntax
- Structured data, canonical sources and machine-readable content
- Coming later: rendering, network behavior and layout shifts during task runs
- robots.txt rules for AI crawlers, sitemaps and llms.txt
- Declared WebMCP forms when present: detected, not run
- Evidence redaction, retention and responsible disclosure
Package the work for client and implementation teams.
- Executive summary with explicit confidence and limitations
- Coming later: results per key task for each agent that ran, with step screenshots
- Critical and High fixes with the evidence behind them
- Prioritized remediation backlog with acceptance criteria
- Baseline-to-retest comparison for approved fixes
Agency partnership questions
Can reports be white-labeled?
White-label and export capabilities are not a public product promise. Pilot deliverables and presentation boundaries are agreed individually.
Can one method cover different client stacks?
Yes. The task and evidence contracts stay consistent while fixtures, technologies and assertions remain domain-specific.
Does a failed agent mean the client site is broken?
No. Platform failures are ours and never count against the client site. Separating website, agent and policy causes is coming later.
Practical delivery guide
Keep one client audit defensible.
Scope authorization, version scenarios, preserve report-safe evidence, assign the right cause and run a comparable retest.
Read the agency audit guideRelated
- GuideRun defensible client audits end to end.Run defensible AI-agent website audits for clients with authorization, versioned scenarios, session evidence, failure attribution and comparable retests.
- Partner programFor agencies that want to run tests for client stores.
- PricingThree plans with test credits; site checks are free.
- Use caseE-commerceAvailable today: AI agent task tests for product discovery, price, stock, delivery and returns, plus the automatic site check. Cart and checkout journeys are coming later.
- Use caseBooking and travelComing later: AI agent task tests for search, availability, prices, policies and timezones. Today every website gets the automatic site check.
- Use caseSaaSComing later: AI agent task tests for SaaS product discovery, documentation and the path to signup. Today every website gets the automatic site check.
- Use caseMarketplacesComing later: AI agent task tests for seller discovery, offer comparison, trust signals, fees and availability. Today every website gets the automatic site check.
Bring one client journey that needs a defensible answer.
Apply with an owned website workflow, a technical reviewer and a clear baseline-to-retest goal.