We audit your store. We do not score individual AI brands.
13.3
Agentic Browsing is in Lighthouse's default config
Experimental
Default config May 2026
PSI rollout (gradual)
The gap
Most sites fail on first run
Fail audits Pass
Directional figure. Almost nobody in VTEX owns this yet.
What we sell
AI agent readiness for VTEX commerce
"This shift transcends traditional SEO, which stands to become less relevant in an agentic world."
McKinsey, Oct 2025
— we sell readiness for the agents doing the buying, not faster SEO
Read
Structured data and llms.txt agents can parse
Understand
Named controls on search, cart, and filters
Transact
Optional WebMCP tools when the spec is ready
What we fix
Five technical fronts
llms.txt
Machine-readable summary at your domain root
Low riskQuick win
Structured data
JSON-LD on Home, PLP, and PDP
Low riskSEO aligned
Accessibility tree
Named search, cart, and filters
Medium effortHelps users too
WebMCP
Tools agents call directly
OptionalHigh value
Layout stability
CLS on key templates
Low riskCore Web Vitals
The stack
How agent discovery maps to your store
Layer 1 feeds and Layer 3 payments are optional paths. Core package: llms.txt, JSON-LD,
a11y tree, CLS. ACP, AP2, and MCP are backed by OpenAI, Stripe, Google, Visa, Mastercard,
and PayPal —
McKinsey, Oct 2025.
Core package
What we implement first on most projects
✓
llms.txt
Agents learn your catalog from one file
✓
Structured data
Products and nav in JSON-LD
✓
Accessibility tree
Named controls on key interactions
✓
Layout stability
CLS hygiene we already know well
WebMCP is not part of the starting package. Covered on the next slide if relevant.
Optional later
WebMCP when you are ready — never required to start
WebMCP
Search, cart, and order lookup as callable tools for agents.
OptionalSpec still moving
We do not bundle WebMCP into the initial audit or core implementation.
If the audit shows you need it and the spec has settled, we scope it separately.
No pressure to buy it on day one. This is not a hidden upsell.
Delivery
How we work
1
Audit
Agentic Browsing on Home, PLP, PDP, cart, search
2
Scope
Map failures to fronts; quote by platform
3
Implement
FastStore kit or VTEX IO app
4
Verify
Re-run audit; show what changed
5
Monitor
Scheduled re-runs as the spec moves
Your store today
2 / 5 pass
→
After implementation
5 / 5 pass
Example audit delta — actual numbers come from your store
Platforms
FastStore vs VTEX IO
FastStore
VTEX IO
Stack
Next.js, open
Store Framework, closed
Delivery speed
Fast
Slower
Repeatability
High (drop-in kit)
Medium (custom app)
Typical ticket
Lower
Higher
Best for
Rollout across stores
Premium, defensible work
Same outcome. Different delivery model.
Engagement
Three tiers
Tier 1
Audit
Report and roadmap. Low cost, easy yes.
Tier 2
Implementation
Fix the fronts you need, scoped by platform.
Tier 3
Retainer
Keep passing as Lighthouse checks change.
Our promise
We will not oversell this
Standards still moving
WebMCP and llms.txt are proposals. We build in modules so pieces can swap when the spec changes.
Pass or fail, per check
No vanity score to chase. Each item is something we can show you fixed.
Why we sell a retainer
The checks will change. A one-off project gets you passing today. The retainer keeps you passing after the next release.
Volve Technology
